MES transaction control activities

MES XML Command activities and child workflows that call MES XML Command activities can be grouped as part of a single MES database transaction. As each activity is executed, its results are stored in the MES database but not committed until the Commit MES activity is completed.

If any participating activities result in an error or if the transaction has not been completed within the MES middleware transaction timeout period, the results of all activities bound to the transaction are rolled back (that is, the results are removed from the MES database).

The following figure shows a sample workflow that executes an MES transaction.