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.2K All Categories
- 64 General
- 11 Training
- 201 Installation / Setup
- 1.1K Flows
- 106 Rules
- 261 Administration
- 212 Portal
- 490 General Q & A
- 693 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 51 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 178 Pages
- 5 Process Mining
- New Features
- 178 Datastructures
- 69 Repository
- 219 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 76 Lunch And Learn Questions