Map

Overview

The Map action allows a workflow to apply a specific transformation to each element in a collection, such as a list or array.
The action works by applying a function to each item and generating a new collection with the modified values.

This action is particularly useful for converting or transforming data structures, formatting outputs, or altering values based on a set of rules.

For example, if a workflow has list of account objects and want to map new values with the account records, then they can prefer using Map action.

Let’s explore the screens that follow, after drag-n-drop of Map action on workflow canvas.

Config

Config Field	Description
Map Source	It enables to choose the source type to where the mapping will be performed on records.
Model / Input / Variable	It enables to choose the exact value of source type to where the filtering will be performed on records. Note: By default, label of this field will be populated depending upon the Map source chosen earlier.
Key Property	It enables to specify the key property which will be unique value to trace records in collection. Note: By default, this field will be invisible. It will only be populated if the Map Source is chosen as Model.
Output Properties	It enables to specify output properties of records after filtering data, which means which field values are to be taken under consideration in filtering from the selected key property. Note: By default, this field will be invisible. It will only be populated if the Map Source is selected.
Filters	It enables to perform filtering on map records. Reference: Filters

Filters

Filter Field

Description

Field Name

It enables to specify the field name as left operand in filtering.

Operator

It enables to specify the operator to compare in filtering such as

Equals: The equal operator is used to compare two values or expressions. It is used to compare numbers, strings, Boolean values, variables, objects, etc. The result is TRUE if the expressions are equal otherwise it’s FALSE.
Starts with: It returns TRUE if a string or number starts with the specified character otherwise it returns FALSE.
Ends with: It returns TRUE if a string or number ends with the specified character otherwise it returns FALSE
Contains: The contains operator returns TRUE if the value on the left contains the value on the right, and otherwise FALSE
In: IN operator allows you to easily test if the expression matches any value in the list of values. Determines whether the value of an expression is equal to any of several values in a specified list.

Source Type

In this option, you can select various sources from which you want to display values.

Reference: Source Type

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

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.