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 8 Current »

Overview

  • The Emit Event action enables communication between different layouts or workflows by sending out events from a source layout.

  • This action is triggered by user interactions such as button clicks or other input actions.

image-20240909-140751.png

  • The Emit Event allows the workflow to pass output parameters or data to other layouts or workflows that are configured to listen for the event.

  • It provides a way to trigger actions or transitions in other parts of the application, fostering dynamic interactivity between different components.

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

Config

image-20240819-061309.png

  • As Emit Event is used for communication between two layouts or two workflows by Emitting Events from the source Layout. Here you can choose the event which you want to emit.

Note: By default, prebuilt events are available in the dropdown. User can also create events as per his business need.

Action Details

image-20240819-061555.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