Overview
The Prompt action displays a dialog box that requests input or confirmation from the user. This could be used for various purposes, such as asking for consent, confirming a decision, or collecting information that is necessary to proceed with the workflow.
The Prompt action ensures that the user is actively engaged in key decisions or inputs, making it ideal for cases where a response is needed before continuing with the next step of the process.
Let’s explore the screens that follow, after drag-n-drop of Prompt action on workflow canvas.
Config
Config Field | Description |
|---|---|
Header | It enables to input text which will be displayed on the header of the prompt. |
Prompt Message | It enables to input confirmation message body which will be displayed on the prompt. |
Confirmation Option Label | It enables to input label for button which will be used for confirmation of the prompt operation. |
Cancel Option Label | It enables to input label for button which will be used for cancellation of the prompt operation. |
Prompt Theme |
|
Hide Texture Theme | If checked, it will disable the texture theme of the prompt. |
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