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.1K All Categories
- 61 General
- 11 Training
- 201 Installation / Setup
- 1.1K Flows
- 106 Rules
- 260 Administration
- 212 Portal
- 489 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
- 76 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 66 Lunch And Learn Questions