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
The Config tab is used for defining switch conditions when creating or editing workflows within the platform.
After clicking on + button, following screen for creating switch cases opens up.
Switch Case Modal Field | Description |
|---|---|
Label | A user-friendly name for the switch case, used for easy identification within the application. |
Name | The unique identifier for the switch case, typically used in code or within merge text. |
Filters | 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. |
Add Condition & Group Condition | It enables to add conditions for filtering. Reference: Add Condition & Group Condition |
Add Condition & Group Condition
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. Reference: Destination Type |
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. Reference: Source Type |
Value | The available options will change depending on the selected source type. For example, if you choose "Static" as the source, you can provide a fixed static value. |
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.
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
Attribute Name | Description |
|---|---|
Label | A user-friendly name for the action, used for easy identification within the application. |
Name | The unique identifier for the action, typically used in code or within merge text. |
Is Async? | Decides whether the action will be performed in async context or within sync context. |
Description | A user-friendly description for the action, used for easy apprehend within the application. |
Is Async : Brief Explaination
Is Async checkbox provides flexibility in managing how actions within workflows are executed in relation to system transactions. Here's how it works:
Single Transaction Execution: When multiple actions within a workflow have Is Async set to
false, they are executed within a single transaction. This ensures that all actions complete successfully, or if one fails, the entire transaction is rolled back, maintaining data integrity.Breaking Transactions: When an action within the workflow has Is Async set to
true, a new transaction is initiated at that point. This allows for separation between the actions, enabling different parts of the workflow to be processed independently.Handling Large Data: The Is Async feature is especially useful when working with large amounts of data that may risk hitting system governor limits. By setting certain actions as asynchronous, you can ensure that the workflow avoids limits by breaking the execution into multiple transactions.
This feature empowers users to control how workflows behave during execution, optimizing performance and avoiding potential issues with system resources.
Input
Overview
In noKodr, an Input Variable is used to temporarily store a value and pass it to a desired action or component within the application. It facilitates the dynamic transfer of data between different elements of the application.
Temporary Storage: Stores values temporarily during the application's operation, allowing for flexible data handling.
Data Passing: Enables the transfer of values to other workflow actions or components, such as layouts, Components etc. based on user interactions or other triggers.
For example, Suppose you have a button that, when clicked, opens a layout or modal (screen) displaying a user's personal information. To achieve this, you can use an Input Variable to pass the user's ID from the button click event to the layout or modal. This allows the layout to retrieve and display the relevant personal information associated with that user ID.
Variable Config | Description |
|---|---|
Label | A user-friendly name for the variable, used for easy identification within the application. |
Name | The unique identifier for the variable, typically used in code or within merge text. |
Field Type | Specifies the type of data the variable will hold (e.g., text, number, date, etc). Reference: Field Types |
Default Value | The initial value assigned to the variable, applied if no other value is provided. Note: It depends on the field type we choose. |
Required | If checked true, the variable becomes required. |
Is Array ? | Checkbox that indicates whether the variable can store multiple values (an array) instead of just one. |
Field Types
Data Type | Description |
|---|---|
Text | Stores a string of characters, such as names or descriptions. |
Checkbox | Represents a boolean value (true/false) typically used for on/off or yes/no selections. |
Integer | Holds whole numbers without decimals, used for counting or numerical calculations. |
Double | Stores numbers with decimals, allowing for more precise calculations. |
Record | Represents a single Salesforce record, such as an account or contact. |
Object | Stores complex data structures or objects, often containing multiple fields or properties. |
Currency | Used to represent monetary values, ensuring proper formatting and calculations. |
Date | Stores a calendar date (year, month, day) without time information. |
DateTime | Stores both date and time information together. |
Picklist | A dropdown menu that allows users to select a single value from a predefined list. |
Tags | Stores a list of keywords or labels used for categorization or filtering. |
Specifically formatted to store email addresses. | |
Phone | Holds phone numbers, often with specific formatting. |
URL | Stores web addresses (Uniform Resource Locators) for linking to external resources. |
Radio | Represents a group of mutually exclusive options where only one can be selected. |
Time | Stores time information without an associated date. |
Percentage | Stores numerical values represented as percentages, often used in calculations or metrics. |
Text Area | Allows for the input of larger amounts of text, often used for comments or detailed descriptions. |
Duration | Stores a length of time, typically used for measuring intervals or time spans. |
Multi Picklist | Allows users to select multiple values from a predefined list. |
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 Dan and Aron. Assign lead to Dan, when lead source as Phone and assign lead to Aron when lead source is Web using workflows like below:
0 Comments