Overview
The Switch action is an advanced decision-making mechanism that efficiently handles multiple possible outcomes or conditions.
Unlike simple if-else conditions, the Switch action tests a single variable or expression against a predefined set of values. Based on which value matches the variable, the corresponding action is executed.
This method is especially useful when there are numerous possible outcomes, as it avoids repetitive and nested conditions, simplifying the workflow.
It is often used in situations where a workflow must take distinct actions based on user choices, status updates, or other distinct categories of input data.
Let’s explore the screens that follow, after drag-n-drop of Switch action on workflow canvas.
Config
...
After clicking on '+' button, following screen for creating switch cases opens up.
...
Condition | Description |
|---|---|
Add Condition |
|
Add Group Condition |
|
Add Condition Explained
After clicking on + button, following screen for adding condition for switch case opens up.
...
Condition | Description | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Destination Type | It defines the target location, where the switch condition will be mapped with. Note: By default, the Destination Type is model. Other options include variable, cookie key, and local storage key.
| |||||||||||
Model | When you select Note:
| |||||||||||
Field | It defines the exact field or variable where values will be stored for mapping. Note:
| |||||||||||
Note: The following fields, namely Operator, Source Type, and Value, are disabled until you fill in the above 3 condition fields. | ||||||||||||
Operator | It is specifically operator value such as Equals, Not Equals, In, Starts With, Ends With, Contains. | |||||||||||
Source Type | It defines the data which will be mapped for switch with destination field chosen earlier. Note: By default, the Source Type is Static. Other options include Model, Variable, Cookie Key, Local Storage Key, User, Null, and Blank.
| |||||||||||
Value | The available options will change depending on the selected source type.
| |||||||||||
Destination Type
In noKodr, the term Destination refers to the location where you want to assign or add a value. It allows you to choose from multiple options for where the value should be applied or stored.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
For example, If you are assigning a value to the "First Name" field for a contact, then the "First Name" field would be the Destination. This means that the value you provide for the first name will be stored or displayed in that specific field, ensuring that the contact's information is correctly recorded. |
Multiple Options: You can select from various destinations based on your needs, ensuring flexibility in how and where data is assigned.
Value Assignment: Determines the target location for assigning values, which could include fields from models or other data storage points within the application.
Destination Type | Description |
|---|---|
Model | From this source, users can select a Model (Salesforce Object) field to be displayed as the destination type. |
Variable | Here, users can select the destination type from variables such as Record ID, Is Disabled, Is Read only, or Is Visible. |
Input Variable | Here, user can select the destination type from input variables created in the layout by him earlier. |
User | Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID. |
Device | It enables user to decide whether the action will be visible on the specific device type or not. Devices supported:
|
Source Type
Source Type | Description |
|---|---|
Static | Use this option to provide a fixed static value. |
Model | Choose the field from other models whose value you want to include. |
Variable | Select from the variables created in the layout whose value you want to use. |
Input Variable | Select from the variables created in the layout whose value you want to use. |
User | You can also select fields from the current logged-in user in your organization to include in the merge. Note: The User source refers to the currently logged-in user in your organization. This means that if you include the First Name field from the user, each time a different user logs in, they will see their own First Name displayed. |
Null | It enables us to assign null value to the Destination Type field we chose. |
Blank | It enables us to assign blank value to the Destination Type field we chose. |
Action Details
...
| Include Page | ||||
|---|---|---|---|---|
|
Input
...
...
| Include Page | ||||
|---|---|---|---|---|
|
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
For example, if a sales organization wants to assign leads to different sales representatives based on the lead source, they can use workflow here, suppose there are two sales reps namely    |