Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Overview

  • The Pop Modal action is used to close a modal window that was previously opened with a Push Modal action.

  • It signifies the completion of an operation, such as form submission or cancelation, and returns the user to the previous layout.

image-20240910-062547.png

  • This action allows the workflow to continue from where it left off, resuming normal operations after the modal interaction is finished.

  • Let’s explore the screens that follow, after drag-n-drop of Pop Modal action on workflow canvas.

Action Details

image-20240819-082231.png

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

image-20240911-043804.png

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.

  • No labels