Scenario - Revision history

Frank@tygron.nl at 13:43, 8 July 2026

2026-07-08T13:43:20Z

← Older revision		Revision as of 13:43, 8 July 2026
Line 11:		Line 11:

	==Limit Map==		==Limit Map==
	~~Scenario's~~ can be limited to a specific part of the map by ~~selecting~~ 'Measure Neighborhoods' in the Editor. This limits ~~the map~~ to only those [[Neighborhoods]] covered by measures. 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==

Frank@tygron.nl at 12:25, 7 July 2026

2026-07-07T12:25:18Z

← Older revision		Revision as of 12:25, 7 July 2026
Line 11:		Line 11:

	==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.		Scenario's can be limited to a specific part of the map by selecting 'Measure Neighborhoods' in the Editor. This limits the map to only those [[Neighborhoods]] covered by measures. Using the margin attribute a margin can be added around the Neighborhoods.

	==Attributes==		==Attributes==

Maxim@tygron.com at 15:11, 2 July 2026

2026-07-02T15:11:03Z

← Older revision		Revision as of 15:11, 2 July 2026
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==
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]]

Frank@tygron.nl at 07:28, 8 June 2026

2026-06-08T07:28:31Z

← Older revision		Revision as of 07:28, 8 June 2026
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 ~~events~~.		*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.

Frank@tygron.nl at 07:28, 8 June 2026

2026-06-08T07:28:20Z

← Older revision		Revision as of 07:28, 8 June 2026
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 ~~measures~~;		*Activate one or more [[measure]]s;
	*Activate ~~areas~~ or ~~neighborhoods~~;		*Activate [[area]]s or [[neighborhood]]s;
	*Adjust attribute values and ~~globals~~;		*Adjust [[attribute]] values and [[global]]s;
	*Activate events.		*Activate events.

Frank@tygron.nl at 07:27, 8 June 2026

2026-06-08T07:27:57Z

← Older revision		Revision as of 07:27, 8 June 2026
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:
			*Activate one or more measures;
			*Activate areas or neighborhoods;
			*Adjust attribute values and globals;
			*Activate events.

	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.

Frank@tygron.nl at 13:07, 13 May 2026

2026-05-13T13:07:56Z

← Older revision		Revision as of 13:07, 13 May 2026
Line 22:		Line 22:
	* [[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]]		* [[How to use a limit map in a Scenario]]
			\|api=*[[Api session items scenarios]]
			*[[Api session event editor scenario]]
	}}		}}

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

Maxim@tygron.com at 10:16, 13 November 2025

2025-11-13T10:16:12Z

← Older revision		Revision as of 10:16, 13 November 2025
Line 22:		Line 22:
	* [[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]]		* [[How to use a limit map in a Scenario]]
	~~\|videos=~~
	~~{{video\|link=https://www.youtube.com/watch?v=2eAsisgZNuo&list=PLqkv7u9AhhfwrmXQSwDkEvBbzfK900yg3&index=10\|language=dutch\|description=Webinar {{software}} LTS release 2023: working with scenario's.}}~~
	}}		}}

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

Maxim@tygron.com at 10:15, 13 November 2025

2025-11-13T10:15:58Z

← Older revision		Revision as of 10:15, 13 November 2025
Line 13:		Line 13:
	\|notes=		\|notes=
	* Scenarios are intended to become parallel planned situations		* Scenarios are intended to become parallel planned situations
	* Scenarios replaced the incremental ''Level'' system.
	\|howtos=		\|howtos=
	* [[How to add or remove a Scenario]]		* [[How to add or remove a Scenario]]
Line 22:		Line 21:
	* [[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]]
	\|videos=		\|videos=
	{{video\|link=https://www.youtube.com/watch?v=2eAsisgZNuo&list=PLqkv7u9AhhfwrmXQSwDkEvBbzfK900yg3&index=10\|language=dutch\|description=Webinar {{software}} LTS release 2023: working with scenario's.}}		{{video\|link=https://www.youtube.com/watch?v=2eAsisgZNuo&list=PLqkv7u9AhhfwrmXQSwDkEvBbzfK900yg3&index=10\|language=dutch\|description=Webinar {{software}} LTS release 2023: working with scenario's.}}

Maxim@tygron.com at 12:08, 3 October 2025

2025-10-03T12:08:14Z

← Older revision		Revision as of 12:08, 3 October 2025
Line 17:		Line 17:
	* [[How to add or remove a Scenario]]		* [[How to add or remove a Scenario]]
	* [[How to change properties of a Scenario]]		* [[How to change properties of a Scenario]]
			* [[How to use a limit map in a Scenario]]
	* [[How to change Events fired by a Scenario]]		* [[How to change Events fired by a Scenario]]
	* [[How to change Measures activated by a Scenario]]		* [[How to change Measures activated by a Scenario]]