Overview
The Toaster action is used to display brief notifications or messages to the user. These messages typically appear in a corner of the screen and are designed to provide feedback about the success, failure, or completion of an action.
The messages disappear automatically after a few seconds, ensuring minimal disruption to the user’s experience.
Toasters are commonly used for system alerts, confirmations, or updates, such as when a form is successfully submitted or when an error occurs during a process.
Let’s explore the screens that follow, after drag-n-drop of Toaster action on workflow canvas.
Config
Config Field | Description |
|---|---|
Type | It enables to choose the type of toaster to be used. It consists of various options:
Note: By default, selected type is Info. |
Message | It can be displayed using Merge Text. You can explore more about Merge Text here. |
Details | A user-friendly description for the toaster, used for easy identification within the application. |
Override Result | If checked, toaster shows result based on provided result in input. |
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.
Add Comment