Bulk Notify

Config

Config Field	Description
Bulk Notify Source	It enables to choose from various sources to bulk notify. Sources include: Variable Model Input
Input Source	It enables to choose the exact input source depending upon earlier chosen field. Note: By default, this field is invisible. Once you input in bulk notify source, this field will get populated.
Business Event	It enables to choose the event or update for which the bulk notifications are to be sent.
Mapping	It enables to map the fields for input conditions to notify. //Crosscheck Reference: Mapping

Mapping

Config Fields	Description
Fields	It enables to enter fields for which notifications to be triggered.
Operator	It is specifically operator value such as Equals, Not Equals, In. Note: It is disabled until you fill above first condition field.
Source Type	In this option, you can select various sources from which you want to display values. Note: By default, the Source Type is Static. Note: It is disabled until you fill above first condition field. 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. Note: It is disabled until you fill above first condition field.

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.