Overview
The Component Action allows for triggering specific behaviors or functions within individual UI components, such as buttons, forms, or custom widgets.
This action facilitates dynamic interaction between the user and the interface, enabling workflows to respond to user inputs or other triggers.
By interacting with specific UI elements, the Component Action enhances the interactivity and responsiveness of the application, ensuring a smooth, engaging user experience.
Config
Config Field | Description |
|---|---|
Layout Item | It enables to choose from the layout item you created in the specific layout, you are aiming to trigger component action on. |
Action Name | It enables to choose the action available on Layout item one chose earlier. Note: On the basis of action one chooses, more fields will be populated in this modal. |
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.
0 Comments