![]() ![]() To create or modify a scenario on this page, configure the form as required then save it as a scenario. This makes it easier for users who don't have access to the workflow to create and modify the scenario. Create and manage scenarios on the Messaging tabĭepending on your scenario permissions, you can create, modify, rename, and specify permissions for scenarios from the messaging page used to send the form. After sorting, edited scenarios remain in the same position, new scenarios are added to the bottom of the list. This only sorts the list as it currently appears. (You can't reverse this action, but can manually change the order once sorted.) ![]() To sort the list of scenarios in alphabetical order (A-Z), click Sort Scenarios.To sort the list in a customized order, click and drag the scenario to change its position.To change how the list is sorted, do one of the following: You can sort the scenarios in your workflow to make it easier for users to manage the list or quickly find specific scenarios. You can edit the scenario and its permissions in the form's Edit menu. If you have manage or editor permissions for the scenarios and sender permissions for the form, you can access scenarios through the form's messaging page.Ĭreate and manage scenarios in the workflow.If you have access to the workflow and have manage scenario permissions, you can access scenarios from the form's Edit menu.There are two ways to create and edit scenarios, depending on your scenario permissions: Scenario editors can still modify the default scenario settings for hidden form sections using the guidelines explained above. 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. Some form sections (for example, Recipients, Devices, Handling) allow you to control whether a given configuration option is visible to form initiators. ![]() You can also add or remove settings (for example, properties or entire sections) from the form layout, and these changes are reflected in the scenario. If you edit the scenario to change its values, the changes are reflected in the scenario form as soon as you save the scenario. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |