The Run Chain Command is a type of trigger that provides the ability to invoke an existing Chain and pass variables between existing Chains. A parent-child relationship is another way to think about Chain within a Chain execution. The Chain being called is the child, and the chain issuing the call to the child is the parent.
This feature allows for reusable (modular) Chain operations across multiple use cases. Outputs from the child Chain can be used as input in the next Command within the parent Chain.
To use the Run Chain Command, Navigate to the Chain Events group, and add the Run Chain event as a command to the chain. Once the Run Chain command is on the Studio pallet, simply connect and edit the Command as you would any other Command. The Run Chain command requires that you specify the Chain to Run and, if applicable, Chain Runtime Inputs.
Outputs can be added to any Chain. When a child Chain is invoked through a Run Chain event, the output will be available to any command in the parent Chain. This allows for a flexible and modular architecture where individual Chains can be reused and operate as independent functions with their own outputs.
Outputs are managed in the Chain edit form.
If a variable needs to be passed from one Chain to the next, then be sure the first Command in the target Chain has a Runtime Input. The example below corresponds to the example above whereby two variables can be set on the receiving Chain.
At this point, continue to build the Chain and leverage the variables that were passed from the prior Chain.
If OneCloud Life Cycle Management is used whereby Chains are promoted from one Environment to another Environment, special care should be taken to promote the subordinate sub-level Chain(s) before the primary top-level Chain is promoted. In other words, it is important that the child Chain(s) exists in the Environment in advance of promoting the parent chain.
Learn how to use Runtime Inputs.