From Bright Pattern Documentation
imported>Elizabeth |
(Updated via BpDeleteTranslateTags script) |
||
| Line 1: | Line 1: | ||
| − | + | = Start Another Scenario= | |
The Start Another Scenario block starts the specified scenario from within the given (parent) scenario. Variables defined in the parent scenario carry over to the sub scenario. After the sub scenario finishes executing, control returns to the parent scenario (except when terminated by error or disconnect). The parent scenario will resume by executing the next block in the flowchart. | The Start Another Scenario block starts the specified scenario from within the given (parent) scenario. Variables defined in the parent scenario carry over to the sub scenario. After the sub scenario finishes executing, control returns to the parent scenario (except when terminated by error or disconnect). The parent scenario will resume by executing the next block in the flowchart. | ||
| Line 10: | Line 10: | ||
[[File:Start-Another-Scenario-Settings.png|800px|thumbnail|center|Scenario Builder Start Another Scenario block settings]] | [[File:Start-Another-Scenario-Settings.png|800px|thumbnail|center|Scenario Builder Start Another Scenario block settings]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 04:10, 29 May 2024
Start Another Scenario
The Start Another Scenario block starts the specified scenario from within the given (parent) scenario. Variables defined in the parent scenario carry over to the sub scenario. After the sub scenario finishes executing, control returns to the parent scenario (except when terminated by error or disconnect). The parent scenario will resume by executing the next block in the flowchart.
To configure the block, select the desired sub scenario in the drop-down list. The label of the block in the flowchart will display Start Another Scenario “[scenario name]”. In the scenario shown, you can see that the Start Another Scenario block is used if the call is disconnected.
