Scenario: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 31: Line 31:
* [[Api session event editor scenario]]
* [[Api session event editor scenario]]
* [[Api session event editor activate testrun]]
* [[Api session event editor activate testrun]]
*[[Web scenarios]]
}}
}}


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

Latest revision as of 14:09, 22 September 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.