Scenarios

scenarios is a built in app for managing scenarios with the scenarios app in , you can start or call a scenario, return scenario outputs, and customize the run name modules with the scenarios app, you can use the following modules to build your all scenarios modules are free to use, as they do not consume docid\ hh nrtakeqakbmg63uuin triggers start scenario starts the scenario when called by another source, and lets you receive scenario inputs you should use the start scenario module in a called scenario true 182,100left unhandled content type left unhandled content type left unhandled content type left unhandled content type actions call a scenario calls another scenario from the scenario flow, and lets you pass scenario inputs and outputs between the two all scenarios called by the call a scenario module must be active and scheduled on demand updates to scenario inputs and outputs in subscenarios are not automatically reflected in parent scenarios to sync changes, return to the parent scenario, open the call a scenario module, and update the scenario inputs scenario outputs should be updated in the subsequent modules of the parent scenario true 176,100 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type return output sends the scenario's output back to the source that called it you add this module to the end of a called scenario true 162,100left unhandled content type left unhandled content type left unhandled content type left unhandled content type customize run name defines a custom run name so you can easily identify and search for records add this module anywhere in your scenario to name runs conditionally based on data mapped from a preceding module you can add it multiple times in a scenario, such as at the end of each route, to name runs based on where data is processed you can find custom run names in the run name column of the docid 9z2xnh lyy62cfahjfhj5 the customize run name module furthest in the scenario route defines the name that appears in this table true 313,313left unhandled content type left unhandled content type left unhandled content type left unhandled content type scenarios resources help center https //help make com/subscenarios help center docid 7odicud0ke9 tr4xwuiqn