Config
Config Field | Description |
|---|---|
Source Type | In this dropdown, you can select a source among various sources for which you want to create records. Note: By default, the Source Type is Object. Other options include Model and Variable. |
Note: Fields below this will be populated based on the Source Type one chooses. If Variable and Model are chosen, only one field of choosing specific model and variable will be populated. | |
Object | In this option, you can select the object from which you want to query records. The chosen object will define the source of data for your query. Note: Label of this field is dependent on Source Type chosen earlier. If chosen variable or model, label will be the same either variable or model as per selection. |
How many records to store? | In this option, you can specify the number of records to create from the selected object. You can choose to retrieve either a single record or multiple records based on your operational needs.
|
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.
For example, if a sales team wants to create contacts for opportunities that are having amount more than $50,000, then they can do that by using Decision action as well as Loop action and finally Create Records action.
0 Comments