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.2K All Categories
- 68 General
- 11 Training
- 203 Installation / Setup
- 1.1K Flows
- 108 Rules
- 264 Administration
- 212 Portal
- 494 General Q & A
- 702 Forms
- 334 Reports
- 3 Designer Extensions
- 47 Example Flows
- 53 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 180 Pages
- 5 Process Mining
- New Features
- 181 Datastructures
- 69 Repository
- 222 Integrations
- 28 Multi-Tenant
- 27 SDK
- 81 Modules
- 57 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 106 Lunch And Learn Questions