[[File:Api_multi_scenario.png|thumb|right|400px|[[Stakeholder]]s and [[Scenario]]s]]
By default, a project in the {{software}} always consists of at least one scenario.
By default, a project in the {{software}} always consists of at least one scenario.
==How-to's==
* [[How to add or remove a Scenario]]
* [[How to change properties of a Scenario]]
* [[How to change Events of a Scenario]]
When you have multiple Scenarios, for example with two different designs for you project, you can switch between them from the ribbon bar in the editor. Currently, only one scenario can be active at the same time. Actions taken in a different scenario are reverted.
==Limit Map==
Scenario's can be limited to a specific part of the map by selecting 'Measure Neighborhoods' in the Editor. This way only [[Neighborhoods]] that are covered by measures are active in the Scenario and the map is [[Limit Map|limited]] to these [[Neighborhoods]]. Using the margin attribute a margin can be added around the Neighborhoods.
===Event Bundles===
==Attributes==
[[File:ScenariosEventBundles-Q3-2015.jpg|frame|right|Add events to a scenario ([[Right Panel|right panel]])]]
The attributes and description of an active Scenario are persistent (not reset) when stopping the testrun. This allows users to store attributes for later comparison between Scenario's.
An event is something that occurs, on which the application can react. By selecting the Event Bundles option of a scenario, (a bundle of) Server events can be added to a scenario, that will trigger as soon as the scenario is activated.
====Server Events fired when chosen====
: This section manages Server Events that are fired when the scenario is activated. Events can be assigned on the right panel to the selected scenario, after being added with the 'Add Event' button on the bottom of the [[Right Panel|right panel]]. Then the desired event can be selected from a list on the [[Bottom Panel|bottom panel]]. The selection can be confirmed with the 'Commit' button, or cancelled with the 'Cancel' button.
{{Editor steps|title=add events to a scenario|Select Multi-Scenario → Scenarios|Select scenario to have events added to|Select Event Bundles from the selected scenario|Select 'Add event' on the bottom of the right panel|Select the newly added event on the right panel|Select the desired server event from the bottom panel|Confirm the selection with the 'Commit' button, or use the 'Cancel' button to clear the selection}}
[[File:LevelsEventsBottomPanel-Q3-2015.jpg|frame|center|Event bundle [[Bottom Panel|bottom panel]] with 'Commit' and 'Cancel' buttons]]
* Scenarios are intended to become parallel planned situations
Besides events it is also possible to trigger measures (= predefined [[actions]]) when a scenario is activated. For example; in one scenario the stakeholders looked into different spatial alignments of possible solutions, in another scenario, a particular measure is applied, decreasing the space of possible solutions, which in turn can accommodate further discussions. Prerequisite for this is to have the measure(s) already available, then select the Measures entry on the left panel. The available measures will then show up on the right panel, which can then be assigned to the selected scenario.
|howtos=
{{Editor steps|title=add measures to a scenario|Ensure predefined measures are available in the project|Select Multi-Scenario → Scenarios|Select the scenario to have measures added to|Select on the left panel the Measures property from the selected scenario|Mark the check box of the desired measure from the available entries on the right panel}}
* [[How to change Measures activated by a Scenario]]
: ''Main article: [[Stakeholders]]''
* [[How to configure the available actions of a stakeholder per scenario]]
Selecting the arrow next to 'Stakeholders' on the left panel opens up the stakeholder section, containing the names of all active stakeholders in the project. Here the stakeholder properties can be set up per scenario. The following properties can be adjusted:
* [[How to configure an intro Cinematic for a Stakeholder and a Scenario]]
====Start with Cinematic====
* [[How to use a limit map in a Scenario]]
: ''Main article: [[Cinematics]]''
}}
: To introduce a scenario with a cinematic, each stakeholder can have a tailor made cinematic triggered at the start of the scenario to inform about the intricacies of this particular scenario. These cinematics must be created first, before they are available for selection from the drop down menu on the right panel.
{{Editor steps|title=change the scenario stating cinematic a stakeholder|Ensure a proper cinematic is available|Select Multi-Scenario → Scenarios|Select the Scenario to have the stakeholder cinematic changed from|Select on the left panel the affected Stakeholder from the Stakeholder list of the selected scenario|Select on the right panel the desired cinematic from the drop down menu|Mark the check box 'Start with Cinematic' to activate the cinematic at the start of the scenario}}
====Active Action Menus====
: ''Main article: [[Actions]]''
: It is possible to assign more (or even different) action menus for each scenario, for each stakeholder. This is very useful when scenarios are implemented to build up complexity or restrict actions for that scenario. Available action menus are present in a list with check boxes. Checking a box adds the action menu to the selected stakeholder for that scenario.
{{Editor steps|title=change the available actions for a stakeholder in the selected scenario|Select Multi-Scenario → Scenarios|Select the scenario to have the stakeholder actions changed from|Select on the left panel the affected Stakeholder from the Stakeholder list of the selected scenario|Mark on the right panel the check boxes of the desired action menus}}
By default, a project in the Tygron Platform always consists of at least one scenario.
When you have multiple Scenarios, for example with two different designs for you project, you can switch between them from the ribbon bar in the editor. Currently, only one scenario can be active at the same time. Actions taken in a different scenario are reverted.
Scenario's can be limited to a specific part of the map by selecting 'Measure Neighborhoods' in the Editor. This way only Neighborhoods that are covered by measures are active in the Scenario and the map is limited to these Neighborhoods. Using the margin attribute a margin can be added around the Neighborhoods.
Attributes
The attributes and description of an active Scenario are persistent (not reset) when stopping the testrun. This allows users to store attributes for later comparison between Scenario's.
Notes
Scenarios are intended to become parallel planned situations
Multi Scenario