Scenario: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[File:Api_multi_scenario.png|thumb|right|400px|[[Stakeholder]]s and [[Scenario]]s]]
[[File:Api_multi_scenario.png|thumb|right|400px|[[Stakeholder]]s and [[Scenario]]s]]
A scenario is an [[Item]] that stores a series of settings, actions and events that can be activated automatically. For example, a scenario can:
A scenario is an [[Item]] that stores a series of settings, actions and events that can be activated automatically. For example, a scenario can:
*Activate one or more [[measure]]s;
*Activate one or more [[measure]]s.
*Activate [[area]]s or [[neighborhood]]s;
*Activate [[area]]s or [[neighborhood]]s.
*Adjust [[attribute]] values and [[global]]s;
*Adjust [[attribute]] values and [[global]]s.
*Activate [[event]]s.
*Activate [[event]]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.


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.
When you have multiple Scenarios, for example with two different designs for your [[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==
==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.
Scenarios can be limited to a specific part of the map by setting the 'Limit Calculation Scope' to 'Measure Neighborhoods' in the Editor. This limits calculations to only those [[Neighborhoods]] covered by measures. Using the margin attribute a margin can be added around the Neighborhoods.


==Attributes==
==Attributes==
Line 27: Line 27:
* [[How to configure the available actions of a stakeholder per scenario]]
* [[How to configure the available actions of a stakeholder per scenario]]
* [[How to configure an intro Cinematic for a Stakeholder and a Scenario]]
* [[How to configure an intro Cinematic for a Stakeholder and a Scenario]]
* [[How to use a limit map in a Scenario]]
|api=
|api=*[[Api session items scenarios]]
* [[Api session items scenarios]]
*[[Api session event editor scenario]]
* [[Api session event editor scenario]]
* [[Api session event editor activate testrun]]
}}
}}


{{Editor multi scenario nav}}
{{Editor multi scenario nav}}
[[Category:Items]]
[[Category:Items]]

Latest revision as of 13:43, 8 July 2026

Stakeholders and Scenarios

A scenario is an Item that stores a series of settings, actions and events that can be activated automatically. For example, a scenario can:

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 your 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

Scenarios can be limited to a specific part of the map by setting the 'Limit Calculation Scope' to 'Measure Neighborhoods' in the Editor. This limits calculations to only those Neighborhoods covered by measures. 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.