This action commits the current database transaction (i.e. saves in the database all updates made by the transaction).
Usually you don't need an explicit Commit, since the transaction is automatically committed by Tersus upon a successful execution of the service in which it is included. Yet, sometimes you may want to catch (through an Error exit) an exception issued upon a failure, inspect its details, and based on these details decide whether to perform a Commit or a Rollback.
After either Commit or Rollback, a new database transaction is started, so you can continue to work with the database normally (the new transaction will be committed or rolled back independently).
For more details, see Database Transaction Support in Tersus.