The Scenario transfer node (STN) handles the joining of two scenarios and conceptually, comprises of two components (as shown in Figure 1). The node links two scenarios and runs them together.
Figure 1. Scenario Transfer node
For a pitcher STN, if it is not linked to the catcher scenario, this node acts like a minimum flow requirement node. For a catcher STN, if it is not linked to the pitcher scenario, it acts like an inflow node.
There would be a new running configuration "Run Multiple Scenario Together" (needs a catchier name). That would be able to handle what to do (in each phase) both when scenarios are connected and when they are run separately.
Expressions from one scenario would need to point to the transfer node when expressions need to point to items in a different scenario. The transfer node would have to produce a result in both connected execution and disconnected execution.The STN operates in either a connected or disconnected mode. When processing a connected execution, the pitcher passes all components of the pitcher scenario to the catcher, hence linking the two scenarios together. For a disconnected execution (ie. scenarios are run independent of each other), the pitcher acts like a minimum flow requirement node and the catcher models an inflow node.
Figure 1. Scenario Transfer node
Constituents
If constituents are defined in both the pitcher and catcher scenarios, you can choose which constituent in pitcher will match to which constituent in the catcher in the STN feature editor. Choose Connected > Constituent Mapping from the tree and click Add (as shown in Figure.
Figure STN, Constituent mapping