Sequence of action execution
The WEBCON BPS Designer Studio tool provides three modes of action execution:
- Standard behavior – an action is executed precisely where the automation flow was triggered,
- Pending in transaction – execution of an action is postponed until at the end of transaction, after all actions in the automation are executed. If any operation within the transaction fails, the action is not executed either. This rule also applies the other way round: failure of an action executed in this mode prevents execution of the whole transaction,
- Pending after transaction – execution of an action is postponed. The action is executed after the end of transaction, i.e. after correct execution of all automations. What is important is that a failure to execute an action operating in this mode does not affect the execution of an already completed transaction.
Most actions available in WEBCON BPS operate in a standard manner, i.e. an action is triggered exactly where it has been embedded in automation. Actions that operate differently are presented in the below table along with information about their mode or modes of operation.
| Action name | Execution mode |
|---|---|
| Read a barcode | Standard behavior, Pending after transaction |
| Add a barcode | Pending after transaction |
| Send a custom email | Pending after transaction |
| Send a standard email | Pending after transaction |
| Remove privileges | Pending after transaction |
| Add privileges | Pending after transaction |
| Start editing a file using OneDrive | Pending after transaction |
| Run an SDK action | Standard behavior, Pending in transaction, Pending after transaction |
info
To learn more about sequence of executing actions, read the ARTICLE available in the WEBCON Community website.