You can use this function to trigger a release workflow whenever certain objects within Payment Engine are changed. To avoid error situations caused by manual object changes, you can define a workflow that allows dual, triple, or quadruple control over changed data. By cross-checking, you can authorize certain changes before the objects are activated.
You can set up a release workflow for the following objects.
Payment orders
For more information, see Release Object ORDER (Payment Order).
Payment items
For more information, see Release Object POITEM (Payment Item).
Recalls
For more information, see Release Object RECALL (Recall).
Service level agreements
For more information, see Release Object SLA (Service Level Agreement).
Value date agreements and corresponding rules
For more information, see Release Object VA (Value Date Agreement).
Routes and corresponding rules
For more information, see Release Object ROUTE (Route).
Clearing agreements and corresponding rules
For more information, see Release Object CA (Clearing Agreement).
Customer agreements and corresponding rules
For more information, see Release Object CUSTAGR (Customer Agreement).
Exception control rules
For more information, see Release Object EH (Exception Control Rule Set).