Assignment

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 `Model` as the Destination Type, the Model field allows you to specify the exact model (such as a Salesforce Object) where the value will be assigned. This ensures precise targeting for your data assignment, allowing you to control where and how the data is applied within your application. 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 after assignment. 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: The following fields, namely Operator, Source Type, and Value, are disabled until you fill in the above 3 condition fields.
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. 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.

Operators

Operator	Supported Destination types	Description
Set	Single Record Models Multi-record Models Non-Array Variable	This operator allows you to set or assign all data from the source to the selected destination.
Merge	Single Record Models	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.

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

For example, Suppose you need to retrieve a contact's first name to populate a form field. In this case, the Source Type would be the "First Name" field from the contact record. This means that the value for the contact’s first name is pulled from this field, and then it can be used or displayed in the target location within the application.

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. 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.
Email	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 user wants to automatically update the "Status" field of a Case object to "Closed" when the "Resolution" field is populated with a resolution note, indicating the issue has been resolved and not manual intervention in between, basically automate the process through workflow. For this the user must assign the Closed value to Status field. For this we can use Assignment Action like this: