View Source

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

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 Model as the Destination Type, the Model field allows you to specify the exact model (such as a Salesforce Object) where the decision condition will be mapped. This ensures precise targeting for your decision action, allowing you to control where and how the decision is applied within your application.

note

Note:

It is specifically dependent on the destination type one chooses.
If you choose another Destination Type, you will get that field label here.

Note:

It is specifically dependent on the destination type one chooses.
If you choose another Destination Type, you will get that field label here.

Field

It defines the exact field or variable where values will be stored for mapping.

note

Note:

After choosing the second condition field, you will get this field visible in modal.
If you chose Model as second condition field, this will be field, and if you chose variable as second field, there will be variable.

Note:

After choosing the second condition field, you will get this field visible in modal.
If you chose Model as second condition field, this will be field, and if you chose variable as second field, there will be variable.

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 decision with destination field chosen earlier.

note

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: Mobile Desktop Tablet

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 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. 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.

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	The Add Condition feature allows users to define multiple criteria that must be met for a validation rule to trigger. This feature is used to create complex logic by combining different conditions that Salesforce evaluates before allowing a record to be saved.
Add Group Condition	The Add Group Condition feature allows users to group multiple conditions together, creating complex logic that involves different sets of criteria. This feature is particularly useful when combining conditions that should be evaluated as a unit (logical OR within a group) or when nesting conditions for more advanced logic.

Action Details

Input

For example, if a sales organization wants to prioritize accounts that have special relationships with key stakeholders whose names start with "Ryan." To automate this, they need a workflow that triggers certain actions when the Account Name starts with "Ryan" in Salesforce.