In the OutSystems Platform, when an end-user makes a request to the application, a transaction is started, and when the server sends the response, the transaction is committed. This ensures only consistent data is persisted on the database. However, you need to consider what happens when an exception is raised.
When using exceptions, you can define in the error handler properties, what happens to the transaction when it catches an exception. For the Abort Transaction property in the error handler you can specify:
Abort Transaction: All the transactions that weren't committed are aborted and these changes are rolled back in the database.
In this situation, you have to set the Abort Transaction property to Yes.
Continue Transaction: the database transaction continues to be processed, as if no exception had occurred. This transaction will be committed by the next Commit Transaction action or implicitly by the platform, typically at the end of request execution.
In this situation, you have to set the Abort Transaction property to No.
What You Should Know
When there is integration with external systems, transaction handling might need some extra care. Learn more about Handling Transactions in Integration Scenarios.
Handling Transactions | Handling Transactions with External Systems