Decision
- Content Writers
Overview
The Decision action introduces logic into the workflow by making choices based on predefined conditions.
It’s essentially a control mechanism that dictates the flow of the process by evaluating certain conditions. If a condition is met, one branch of the workflow is followed; if it is not, a different path is taken.
This action is crucial for workflows that need to react differently under various scenarios.
For example, the workflow might check if a account is active or not and then perform different tasks accordingly.
The Decision action enables workflows to behave dynamically and intelligently, ensuring appropriate responses to different inputs or situations.
Let’s explore the screens that follow, after drag-n-drop of Decision action on workflow canvas.
Config
After clicking on + button, following screen for specifying decision condition opens up.
Condition | Description |
|---|---|
Destination Type | It defines the target location, where the decision condition will be mapped with. Note: By default, the Destination Type is model. Other options include variable, cookie key, and local storage key. Reference: Destination Type |
Model | When you select |
Field | It defines the exact field or variable where values will be stored for mapping. |
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 decision with destination field chosen earlier. |
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.
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. |
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. |
Criteria Conditions
It enables to see toggle switches of AND & OR and add multiple conditions as much as you want and create a logic you desire to create a decision condition.
Condition | Description |
|---|---|
Add Condition |
|
Add Group Condition |
|