Designer > Define scenarios

Define scenarios

Communication plan developers, scenario administrators, scenario supervisors and other users with the correct permissions can create default value sets for forms called scenarios.

If you're familiar with Advanced Messaging scenarios (now sometimes called "legacy scenarios"), you will probably find the features of communication plan scenarios to be familiar. However, we think that once you start working with communication plan scenarios, you'll quickly find them more flexible, intuitive, and powerful than legacy scenarios. Additionally, legacy scenarios may not be available in your xMatters On-Demand deployment.

While communication plan forms essentially define a set of values equivalent to scenarios, scenarios allow you to specify and save form values for form senders to use. For example, if the form includes a Handling section, the form will still control settings such as the order and visibility of items, but the related scenario will define the default values for the handling options.

Understand scenario values

Scenario-level default values replace form-level values, so it's important to understand the following behavior:

  • When a scenario value has been defined for a given setting, this is the value that will appear on the form. For example, if a text property has a default value of "Evacuate the building", and its scenario-level value is "Evacuate Building 5", the latter default text will appear on the form.
  • In contrast, if you do not specify a scenario-level value for a setting that has a form-level default specified, the form-level value appears on the form. For example, if a text property has a form-level default value of "Evacuate the building", and its scenario-level value is not defined, the form-level default value of "Evacuate the building" will appear on the form.
  • When you delete a scenario, the values of settings on the form will revert to their original form-level default values (if any).

Of course, if you later decide to change or delete a scenario-level value, you can edit the scenario and those changes will immediately be reflected in the form once you re-save the scenario. You can also add or remove settings (e.g., properties, sections) from the form layout, and these changes will also be reflected in the scenario.

Some form sections (e.g., Devices, Handling) allow you to control whether a given configuration option is visible to form initiators, and these visibility settings are reflected in form scenarios. For example, if a form's Devices section hides "Work Email", this Device option will not appear in any scenarios related to the form.