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

Overview

  • The Unsubscribe Event action stops the workflow from listening to a specific event.

image-20240910-063247.png

  • Once invoked, it prevents any further responses or actions that would have been triggered by the previously subscribed event.

  • This action is useful for workflows that no longer need to track certain events or that need to stop responding to external triggers after a particular phase is completed.

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

Config

image-20240819-083032.png

Config Field

Description

Layout

It allows to choose layout from which one wants to un-subscribe event.

Event

It allows to choose specific event to be un-subscribed from the layout.

Note: By default, this will show blank, if the layout is not chosen.

Action Details

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