Config
Config Field | Description |
|---|---|
Layout | It allows to choose layout from which one wants to pop the modal to create, update or view record. |
Hide Header | If checked, the modal header will be hidden. |
Modal Header | A user-friendly name for the modal header, used for easy identification within the workflow. |
Modal Size | It is used to define the modal size ranging from extra small to full-screen. |
Event Mapping | It is used to map the event and workflows according to need of record creation. You can explore more about event mapping here. |
Padding Location | It is used to apply padding to modal. One can apply padding at various locations which contains:
|
Padding Size | It is used to apply padding size to modal. One can apply padding at various locations, ranging from xxx-small to xx-large. |
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