Workflow developers, scenario administrators, scenario supervisors and other users with the correct permissions can create default value sets for forms called scenarios.
While 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
When a message sender selects a scenario, any values configured for the scenario replace the default values on the form:
- When values is defined for a setting in the scenario, this is the value that appears on the form when someone selects the scenario to send a message. For example, if a text property has a default form value of "Service degradation" but the scenario value is "Web app service degradation", the latter text — Web app service degradation — appears on the form for the scenario.
- If you don't specify a value for the setting in the scenario, but there is a default value for the form, the form value appears when someone selects the scenario to send a message. For example, if a text property has a default form value of "Antares application", and there is no value defined in the scenario, the form value of "Antares application" appears on the form for the scenario.
- When you delete a scenario, the values of settings on the form will revert to their original form-level default values (if any).
If you edit the scenario to change its values, the changes are reflected in the scenario form as soon as you save the scenario. You can also add or remove settings (e.g., properties, sections) from the form layout, and these changes are reflected in the scenario.
Hidden form sections and scenarios
Some form sections (for example, Recipients, Devices, Handling) allow you to control whether a given configuration option is visible to form initiators. Form scenarios respect these visibility settings; for example, if a form's Recipients section is hidden, then message senders cannot modify the recipients when initiating the scenario. Scenario editors can still modify the default scenario settings for hidden form sections using the guidelines explained above.