A specific type of decision step is called a sub-flow. It permits calling multiple decision flows inside of a single decision flow.
You must choose the decision flow to execute, the input object, and the output object when defining a decision step subflow.
The engine will use the portion of the data object specified in the input attribute for execution. The output attribute defined in the resultant data object will be set back to the core data object.
In our example, the engine will use information from the attribute $.application_data to evaluate the “Creditworthiness Subflow” decision flow, and then set the outcome to $.creditworthiness_result. The core data object will receive updates to the object in this manner.