Exception handler flows
Whenever an unexpected event of an Action occurs and it is redirected to a handler, it can be customized and have its own logic in order to give us flexibility in handling errors and allow a reduction of impact on the end user.
In Exception handlers, we can choose between aborting the transaction or not (rollback of all inserts, updates, or deletes made to the database during the flow that has not been committed) and whether we want to log the error or not, as shown in Figure 7.2:
Figure 7.5 – Parameterization of an abort transaction and log error of an Exception handler
Sometimes, in scenarios where we want to scale the error to module or consumer Actions, we define an output variable for this purpose, being of the type of a structure with two attributes:
HasSucess: A Boolean that returnsTrueif everything goes as expected orFalseif unexpected behavior occurs.Message: A text field used to return a specific...