Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



 enables SCENARIO$ enables the definition of a specific process of input and calculations


Syntax


SCENARIO$(InputPar, GoalPar)

Arguments


  • InputPar can be more than one parameter seperated by comma's and are parameters defining input. The parameters should have an @INPUTSOLUTION and @SCENARIOCHOICE attribute; 
  • GoalPar can be more than one goal parameter seperated by comma's and the word "SUBGOAL" (see example). GoalPar are all parameters defining calculations. The parameters should have a @SCENARIOCHOICE attribute.
    Furthermore, GoalPar parameters should be either string or Telitab parameters initiating additional calculations. Because in addition to the identifiers of the calculation steps, GoalPars are (or can be used as) result containers;

...

  1. Give input you know that is always required (so no reasoning requried)
  2. Perform a calculation;
  3. Create a report; 


TotalCostsScenario$ = SCENARIO$(RequiredInput#, TotalCostsCalculation#, "SUBGOAL", ReportGeneration#)In this relation TotalCostsScenario$

 is relation  is the scenario parameter, this parameter will communicate about the progress of the scenario in words like "In progress" or "Completed".

...

An example for the above input solution:

RequiredInput# = "Required input finished..." + LEFT$(CarName$ + FuelInstallation$ + + Weight$ + STR$(BuildinCosts + FuelEconomy + AmountKm + Years), 0)

By using the LEFT$ function, you force Quaestor to request the parameters inside this function for the INPUTSOLUTION.

An example for the subgoals:

TotalCostsCalculation# = TELITAB#(0, CarName$, FuelInstallation$, Weight$, BuildinCosts, FuelEconomy, AmountKm, Years, TotalCosts)

and

ReportGeneration# = TELITAB#(0, Report$)

CarName$, FuelInstallation$, Weight$, BuildinCosts, FuelEconomy, AmountKm, Years, TotalCosts and Report$ can be any input or calculation.

You see that we still use the Quaestor reasoning for each separate solution. We only pre-discribe the order in which these (3) relations have to be analysed and make a difference between relations to ask input (an you want to save in the data set) and relations that calculate/create things. 


 

Quick links: Functions overview | Attribute overview | Constants overview | Dimensions overview