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 field description receive data from another source click add scenario inputs to open scenario inputs and outputs in the scenario toolbar in https //help make com/scenario inputs and outputs , define the inputs that you want to pass into this subscenario from the calling name the name of the input description the description of the input type the data type default value the pre set value when an explicit value is not specified required whether the input is required multi line whether the input is displayed in a single line (no) or multiple lines (yes) 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 field description scenario select an existing scenario within your team or create a scenario existing scenario select a scenario in the dropdown it must be active and scheduled to on demand create a scenario click the create scenario button in the dropdown to open a configuration dialog name name of the scenario (max 120 characters) description description of the scenario's purpose (max 240 characters) input structure input name(s) and parameters (see start a scenario ) output structure output name(s) and parameters scenario inputs map the value of the input to pass into the scenario you're calling for example, from a preceding module's output bundle or a hard coded value (e g , a function) these fields are autogenerated after you define the input names in the called scenario wait for the scenario to finish select yes if the calling scenario needs to receive outputs from the called scenario to continue its run with yes selected, the module waits for the called scenario to finish its run and return output select no if the calling scenario doesn't need outputs from the called scenario to continue its run with no selected, the module calls the scenario and continues its run 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 field description \[output name] click add scenario outputs to open scenario inputs and outputs in the scenario toolbar in scenario outputs tab, define the outputs that you want to pass from the called to the calling scenario name the name of the output description the description of the output type the data type default value the pre set value when an explicit value is not specified required whether the output is required multi line whether the output is displayed in a single line (no) or multiple lines (yes) map the value of the output to send back to the calling scenario this value can be from a preceding module's output bundle or a hard coded value (e g , function) these fields are autogenerated after you define scenario outputs in this module's scenario, in scenario inputs and outputs 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 field description run name enter a custom run name you can map data from preceding modules to generate a unique value for each run for example new contact recipientname scenarios resources help center https //help make com/subscenarios help center docid 7odicud0ke9 tr4xwuiqn