Case Step
Comments
-
In the below example, I use rule to check one by one, but this method will be eating up a lot of time if I have many customer.
What steps can I use to allow multiple outcome path?
Example:
Input – Customer Name
Case 1 – Customer A – go to flow A
Case 2 – Customer B – go to flow B
Case 3 – Customer C – go to Flow C
Case 4 – Customer D – go to flow D
Exception – go to flow E -
[font=Roboto, Arial, Helvetica, sans-serif]If you are using a string value or any value that can be mapped into a string value, you may find the string match step to be helpful. In its properties, you would type in a list of strings to match, and each of them would appear as an outcome for the step along with a No Matches outcome. This step works much like a case statement in traditional software development.[/font]
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