This transaction is used to edit the workflow of a selected transaction. This can for example be necessary, if a service reports an error in the specified transaction. Since it is possible to edit the complete workflow of a transaction and thereby to skip compulsory technical actions, it is strongly recommended to limit the access to this transaction to only specially authorized administrators.

In any case, after changes in the workflow the user is responsible for evaluating the banking and technical consequences and has to take the required actions outside of the system, where necessary.

Many services can safely be skipped (Print, outgoing email,  swift , etc, except COM.
Do not skip COM!
COM is the Commit service and all down stream actions depend on it being done successfully. If it is skipped you will potentially corrupt the whole Contract and any dependant sub contracts.  

If, for example, the SWIFT service or the booking transfer is set to 'Skip', the user has to make sure that all messages will still be received by the recipients and/or that all required bookings will be executed or otherwise manually booked.

This transaction can work across entities. The “All visible entities” checkbox is visible when the transaction table has been defined for a specific entity and when the current user has system administrator rights. In all other cases, only those transactions for the current entity are displayed. When a transaction for another entity is selected, the application automatically changes to this entity, assuming that the user's profile permits him to edit the data for the relevant entity.

This panel offers the user to sort transactions or workflow entries by transaction status or by workflow status.

Independent of the type of selection only one single transaction can be displayed in the panel “Transaction Header” by marking it and clicking theicon.. From this panel also the further workflow processing of the transaction is possible.

If selecting via workflow entries, these workflow entries are displayed with their respective status in the list field. The user is able to to mark the transactions and process them via the buttons under “Set Service” (e.g. to set back all SWIFT entries from 'E'rror to 'R'etry, after a malfunction of the connection to the SWIFT terminal).