Flow - Sub / multi flows

Supplied to the Dev team by Costas

Sub / multi flows:

A single flow is difficult to manage when trying to develop a real world process. Components like multi-choice and when-if do make a difference but the ability to have more than one flow and a flow to call another flow is essential. These subflows are autonomous components that can be packaged (and possibly sold), a subflow is a skill. This type of skill does not require a developer, it will contain standard flow components.

A subflow will have a variable number of inputs and a single output. Input Variables can have default values and optionally made mandatory. When it is added to a flow, flow variables can be used as inputs.

A subflow can be tested independently, the user will be automatically presented with fields to enter the necessary input values.

Skill subflows will not be editable (e.g. flows published in the Tenjin Flow Store are read-only). We can encourage customers to publish their own flows and possibly sell them (we need to be careful with this as will need to vet them and make sure they work properly, as well as make sure our terms say we could do this).

Possibly the word subflow is not right. There are several flows and the bot builder decides which flow is the primary one (the other option is to copy Microsoft and create trigger phrases).