What are 'legacy' sub dialog flows?

[Deleted User]

When I add a Sub Dialog button to my form I notice there's an option to 'Use Legacy' in its properties, what are these and how are they different from normal sub dialog flows?

[Deleted User]

There are few important differences between Non-Legacy 'Sub Dialog Flows' (also sometimes referred to as 'Subdialog Rule Flows' or 'Sub Dialog Data Flows') and Legacy Sub Dialog Flows.

One difference being that Legacy allows you to 'Pick or Create Flow ID', meaning these flows are separate from the form and are displayed in your project folder structure. Non-Legacy flows are linked to the form itself.

(If you already have a flow you'd like to use for your Sub Dialog Button, you can still use it within Non-Legacy Sub Dialog Flows by adding it as a sub flow.)

Non-Legacy Sub Dialog Flows are very similar to Active Form Flows, in that they can access all data from the form and its components with 'Select From Flow', while Legacy Sub Dialog Flows require data to be passed into them using 'Setup Input Data'.

It's recommended to use Non-Legacy Sub Dialog Flows and Active Form Flows instead of Legacy Sub Dialog Flows going forward in Decisions version 8 and above.

For more information on these form components please see the below documentation:

(Legacy) https://documentation.decisions.com/docs/using-data-flow-form

(Non-Legacy) https://documentation.decisions.com/docs/sub-dialog-data-flow

(Active Form Flows) https://documentation.decisions.com/docs/active-form-flows-overview