Automatic Lock Events

Units of work may also be locked automatically by Transaction Correction and Reconciliation. This process is called the automatic workflow. Transaction Correction and Reconciliation supports automatic workflow for the following unit of work types:

• Batch / ICL
• Outbound transmission

The automatic workflow is defined by events configured in the Transaction Server scheduler. When creating the Scheduler.xml for the automatic workflow, the user needs to consider the following:

• The automatic locking of a unit of work by TCR occurs when the unit of work has been adjusted and is not balanced. Ensure that the proper state changes are configured in the Scheduler.xml before installing Transaction Correction and Reconciliation.
• Automatic lock requests are processed in the order they are received by Transaction Correction and Reconciliation. To avoid problems with automatic locking, determine at which level to perform balancing and then define only that one event in the Scheduler.xml file. For example, after considering individual business needs, one user may need to perform balancing at a transmission level while another needs to perform balancing at a batch (ICL) level.

A sample Scheduler.xml batch (ICL) level balancing configuration for automatic locking is shown:

<EVENT>
   <NAME>TCR - Batch (ICL)</NAME>
   <TYPE>PresentmentStateChange</TYPE>
   <EXEC>
      com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentStatesEventHandler
   </EXEC>
   <PARAMETER name="msgType">setPresentmentState</PARAMETER>
   <PARAMETER name="workType">Edit</PARAMETER>
   <PARAMETER name="actions">Lock</PARAMETER>
   <PARAMETER name="presStates1">!BALANCED,ADJUSTED</PARAMETER>
   <PARAMETER name="group.condition">ACCEPTED</PARAMETER>
   <PARAMETER name="condition">ACCEPTED</PARAMETER>
   <PARAMETER name="presLevel">INB</PARAMETER>
   <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF>
   <PARAMETERREF>sendToTCR</PARAMETERREF>
</EVENT>