PresentmentStateChange

The PresentmentStateChange event occurs when the state of an inbound batch (ICL) changes. For example, when a batch (ICL) finishes loading into the Transaction Server, the state of the batch (ICL) changes to loaded and a PresentmentStateChange event occurs. The event is scheduled in the scheduler XML file. When the event occurs, the following class is called:

com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentStatesEventHandler

The PresentmentStatesEventHandler class is responsible for creating a performAdjustment message to be sent to the AutoAdjust engine. When the AutoAdjust engine receives the performAdjustment message, it performs the specified adjustment actions on the specified batch (ICL). The msgType parameter defines the type of performAdjustment message to send. The parmFileName parameter defines the properties necessary for sending a message to the AutoAdjust engine. For more details, see AutoAdjust Parameter File. Each presStates parameter defines the batch (ICL) states that must be met for the message to be sent.

The condition and productCode parameters are columns in the PRESENTMENT table that are checked against the specified values. If the value from the corresponding column in the database does not match one of the specified values in the event definition, a message is not posted to the AutoAdjust engine. Use any of the columns in the PRESENTMENT table which are of type SMALLINT, CHAR or VARCHAR.

The actions parameter defines the adjustment actions that are to be performed. The following is a sample definition of a PresentmentStateChange event:

<EVENT>
  <NAME>Auto Adjust - Batch</NAME>
  <TYPE>PresentmentStateChange</TYPE>
  <TYPE>PresentmentColumnChange</TYPE>
  <TYPE>PresentmentGroupColumnChange</TYPE>
  <EXEC>
    com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentStatesEventHandler
  </EXEC>
  <PARAMETER name="msgType">performAdjustment</PARAMETER>
  <PARAMETER name="presStates1">REVIEWED,REPAIRED</PARAMETER>
  <PARAMETER name="group.condition">ACCEPTED</PARAMETER>
  <PARAMETER name="condition">ACCEPTED</PARAMETER>
  <PARAMETER name="productCode">ABC1,XYZ2</PARAMETER>
  <PARAMETER name="actions">RBDL,DBDL,NCI,IAD</PARAMETER>
  <PARAMETER name="parmFileName">AdjustmentProfile.properties</PARAMETER>
</EVENT>

The use of parameters like condition and productCode enable the specification of different adjustment actions for different types of batches (ICLs). For example, when assigning product codes at ingestion time, batches (ICLs) assigned to a particular product code perform no adjustments while those assigned to a different product code perform all adjustment types. The valid actions are listed in Adjustment Actions. Use the short name (DBDL, RBDL, ICLD, NCI, TXOB, IAD, BALANCE, or COMPLETE) when specifying actions in the Scheduler.xml file.