enables SCENARIO$ enables the definition of a specific process of input and calculations
SCENARIO$(InputPar, GoalPar)
Arguments
...
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