Sometimes, you will need automations to be executed in a lifecycle state that are decisive for the state change to occur. That is, if the automations do not yield the expected result, the lifecycle should not advance.
Imagine, for example, that you have a “Sent” state in the lifecycle where a document is expected to be sent via email.
In the example case, the “Send approval email” operation or automation is executed.
Naturally, if the sending of the document does not occur, it does not make sense to advance to the Sent state.
By default, Athento does not perform this control. If the user changes the state, the lifecycle state will be updated without performing any verification of the operation execution. This behavior is fine when the automations to be executed are not critical for the state change.
In the example case, the successful execution of the automation is key: if the sending is not performed, the document cannot be moved to the “Sent” state.
In these cases, you must activate the Transactional parameter of the operation, so that in case of failure in the automation, the state change does not occur. This can be done from the advanced administration of the operation or automation.