Page History

...

• A scenario should only be used in combination with an object in the Dataset containing the @DBENTRY and @DBOBJECT attribute;
• A scenario is best used in combination with the Process Manager window;
• For the definition of scanario's in addition to the SCENARIO$ function attributes in the accompanying parameters are required. 
  All required attributes are:

1. 1. @SCENARIO, in the dataslot of the top goal parameter of the scenario (TotalCostsScenario$ in the example below), indicating that this parameter should present the scenario progress;
   2. @SCENARIOCHOICES, in the dataslot of the all parameters (input and calculation steps) that are part of the scenario (exept the top goal parameter initiating the scenario), indicating you should have a "Now" or "Later" choice and "Modify" or "Done" choice during the process;
   3. @INPUTSOLUTION, in the dataslot of the parameters defining the required input steps, indicating it is an input step;

All optional functional attributes are:

1. 1. @NEWNOSHOW, in the dataslot of the top goal parameter of the scenario, indicating the scenario overview will not be shown when you restart the solution;
   2. @AUTOK, in the dataslot of the parameters defining the required calculation steps, indicating that calculation should restart automatically when a solution is restarted;
   3. @TELITAB, in the dataslot of the all parameters (input or calculation steps), indicating the result is in a Telitab format;

Additional the the optional attribute the all usual attributes can be used to manipulate layout (see Documentation of knowledge ). Usefull additions are:

1. 1. Add color to scenario steps, otherwise all steps will appear in the color defined as input). Simply select the relevant parameter and choose a "Cell color" in the Slots & Properties window;
   2. Use the @ORDER:[number] attribute to give an order to the presentation of the scenario when finished, otherwise an alphabetical order is applied;

• All parameters used in the scenario function should be of the string type (string or TeLiTab) and should have the Determined by property USL (see Slots & Properties);
• Parameters used in the scenario function should be in or under the "Top Goals/Undifined" node of the knowledge base;
• By placing "SUBGOAL" between the SUBGOALS (see the example below) you indicated that the next goal will use the input and results of the previous SUBGOAL. You place it behind the goal you want to reuse the solution as part your following goal. Usually you want this so it is adviced to add "SUBGOAL" between the SUBGOALS at all times.

...