Overview
The Show Spinner action displays a visual indicator, usually in the form of a spinning circle, to let users know that a process is underway.
This is particularly useful for operations that may take time, such as data retrieval, file uploads, or API calls.
By displaying a spinner, the application signals to users that they should wait for the process to complete, preventing them from interacting with the UI prematurely or wondering if an action is taking too long.
Let’s explore the screens that follow, after drag-n-drop of Show Spinner action on workflow canvas.
Config
Config Field | Description |
|---|---|
Layout Item | It enables to choose from the layout item you created in the specific layout, you are aiming to show spinner on. |
Variant | It enables to decide the color variant for the spinner. It contains of following variants:
Note: By default, selected variant is Brand. |
Size | It enables to choose the size of the spinner, ranging from xx-small to 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.
Add Comment