Filter

Overview

The Filter action is used to refine data by selecting only the items that meet specific criteria.
When a workflow deals with large datasets, the Filter action helps streamline the process by narrowing the data down to a manageable subset.

This action operates based on conditions or rules that dictate which items are included in the filtered result. This makes the workflow more efficient and focused, processing only relevant data.

For example, a Filter might be used to select only certain types of records from a database or to limit a list of items to those that meet a threshold or requirement.

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

Config

Config Field	Description
Filter Source	It enables to choose the source type to where the filtering will be performed on records.
Input / Variable / Model	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 Filter source chosen earlier.
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. Note: By default, this field will be invisible. It will only be populated if the Filter Source is chosen as Model.
Is Unique ?	If checked, the records will be filtered uniquely. Note: By default, this field will be invisible. It will only be populated if the Filter Source is chosen as Model.
Modify Existing ?	If checked, the existing data in records will be modified. If kept unchecked, it will create a new model with the updated data, which will be treated as a new version of model.

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.