Assignment
- Content Writers
Overview
The Assignment action serves the essential purpose of storing information in a workflow. It works by assigning a specific value to a variable, which can then be referenced or manipulated throughout the entire workflow.
Variables are placeholders for data, and the assignment process allows you to control and utilize this data in various operations.
For example, if you need to store a value that will be used in calculations or conditions the Assignment action is the first step.
This action is fundamental in most automation processes, as it allows for dynamic data handling.
Let’s explore the screens that follow, after drag-n-drop of Assignment action on workflow canvas.
Config
After clicking on the + button, the following screen for specifying assignment conditions opens up.
Condition | Description |
|---|---|
Destination Type | It defines the target location where values will be stored or displayed. 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 after assignment. |
Operator | It is specifically an operator value, such as Set and Merge. |
Source Type | It defines the origin of the data to be used for assignment. |
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. |
Operators
Operator | Supported Destination types | Description |
|---|---|---|
Set |
| This operator allows you to set or assign all data from the source to the selected destination. |
Merge |
| This operator merges data from the source into the selected destination. |
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 label name. |
Variable | Here, users can select the label name from variables such as Record ID, Is Disabled, Is Read only, or Is Visible. |
cookie key | By using the Cookie Key, the result is fetched by the value that has been added under the Cookie Key. But we have to make sure that the value that we are adding is from the Cookie Key value. |
Local Storage Key | By using the Local Storage Key, the result is fetched by the value that has been added under the Local Storage Key. But we have to make sure that the value that we are adding is from the Local storage value. |
Source Type
In noKodr, Source Type refers to the origin or location from which a value is retrieved or obtained. It defines where the data comes from before being used or assigned to field.
Source Type | Description |
|---|---|
Static | Use this option to provide a fixed static value. |
Field | Select the field from the chosen object in the model whose value you want to include. |
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. |
Cookie Key | Choose the available cookie key whose value you want to include from your browser. |
Local Storage Key | Select the available Local Storage Key whose value you want to include from your browser. |
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. |