Creating subflows

To create a subflow, use its Flow ID in a message action using the ManyWho Runtime service in the original flow. The  subflow is started when the message action is executed in the flow.

Creating a subflow from Flow A to Flow B creates a parent>child relationship between the two flows. Outside the context of this relationship, the flow is like any other flow, and can be executed independently as well.

You can create one flow, and link it as a subflow to multiple flows.

You can pass information from the flow to the subflow.

  1. Both the flows need to be published.
  2. The ManyWho Runtime service needs to be installed in the tenant, and imported in the flows.

There are several advantages of jumping from one flow to another. Say, you want to build an app for employee onboarding. Once a new employee joins, there are several things that need to happen simultaneously. She needs to be given an email/password and entered into the company email system, she needs to be assigned a desk, she needs to be requisitioned a telephone/new computer, payroll needs to add her, her benefit details need to be confirmed, and so on. If you create a subflow for each of these processes, it becomes easier to manage dependencies; HR can complete their part without waiting for IT, for example.

Subflows also give you the ability to have a different parallel UI for your users.

Subflow implementations promote a modular approach, and are easier to maintain or update. When a sub-process changes, the parent flow does not need to be redesigned.

