Differences between Template Sub-Flow & Regular Sub-Flow
The Flow/Rule are reusable, such why there is a Template function when building Flow ? What are the differences between the Template Sub-Flow and the Regular Sub-Flow ? For example: Main Flow #A including Sub-Flow X Main Flow #B including Sub-Flow X If Main Flow #A and Main Flow #B happened running concurrently, there would be no issue, no confusion, no cross data for Sub-Flow X right ?
Comments
-
The "Template" feature allows a user to save a set of steps in a flow to be reused in other flows if the logic is applicable.
A Template Flow, however, is entirely different. Within Decisions, you have the ability to create Runtime Selection flows (see documentation below). A Template Subflow is part of the necessary logic for implementing runtime selection flows, and are in no way related to the "Save as Template" functionality in the flow designer.
https://documentation.decisions.com/docs/using-runtime-selection
And no, running two separate flows concurrently that utilize the same subflow does not "cross data" between the two separate instances of the subflow running.
Howdy, Stranger!
Categories
- 4.4K All Categories
- 86 General
- 13 Training
- 212 Installation / Setup
- 1.2K Flows
- 112 Rules
- 282 Administration
- 216 Portal
- 501 General Q & A
- 719 Forms
- 353 Reports
- 3 Designer Extensions
- 48 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 8 Javascript Controls
- 189 Pages
- 5 Process Mining
- New Features
- 187 Datastructures
- 71 Repository
- 233 Integrations
- 30 Multi-Tenant
- 27 SDK
- 81 Modules
- 60 Settings
- 27 Active Directory
- 12 Version 7
- 36 Version 8
- 143 Lunch And Learn Questions