Undo cancel batch (ICL)

When the Transaction Server receives an undo cancel batch (ICL) request, it ensures the request is valid and uses a return code value to indicate any problems. If problems exist, error messages are logged and the undo cancel operation is not started. The request does not start if:
  • The requested batch (ICL) was not found in the database
  • An undo cancel operation for the specified batch (ICL) is already in progress

Once the request is determined to be valid, the undo cancel batch (ICL) operation is performed for all of the inbound and processing batches (ICLs) selected by the user. For processing batches (ICLs), the undo cancel operation is performed on only the processing batch (ICL) that was selected by the user. However, if the processing batch (ICL) needs Risk Management, additional batches (ICLs) may be updated. Refer to Additional undo cancel batch (ICL) processing for processing batches (ICLs) that need Risk Management for more information.

The undo cancel batch (ICL) operation performs the following for each batch (ICL) it processes:
  • The processing states of the batch (ICL) are cleared by setting them to null. For an inbound batch (ICL), the processing states of its child processing batches (ICLs) are also cleared. The undo cancel operation clears the states to prepare each batch (ICL) to be re-processed by the application associated with the state. If a state is not cleared, it prevents the application from reprocessing the batch (ICL). The following batch (ICL) states are never cleared by the undo cancel operation:
    • CREATED
    • CAPTURED
    • LOADED
    • IQA
    In some cases, a user may want to prevent additional states from being cleared by the undo cancel operation. Specify the additional states that should not be cleared in the undo cancel preserve batch states property. For more information about this property, see General Properties Page.
  • For FTM Check, the processing states of any segments associated with the batch (ICL) are also cleared by setting them to null. The undo cancel operation clears the states to prepare each batch (ICL) to be re-processed by the application associated with the state. If a state is not cleared, it prevents the application from reprocessing the batch (ICL). The following segment states are never cleared by the undo cancel operation:
    • LOADED
    • IQA
    In some cases, a user may want to prevent additional states from being cleared by the undo cancel operation. Specify the additional states that should not be cleared in the undo cancel preserve segment states property. For more information about this property, see General Properties Page.
  • The condition flag for the inbound batch (ICL) and its child processing batches (ICLs) is set to the condition that was assigned to the inbound batch (ICL) at ingestion. Usually, this condition is accepted.
  • Transaction Server uses an event to notify the other applications that the condition flag changed.

Additional undo cancel batch (ICL) processing for processing batches (ICLs) that need Risk Management

When the undo cancel operation is performed on a processing batch (ICL) that needs to be re-processed by Risk Management (Risk), the operation clears additional states. In addition, an event handler for Risk needs to be added to the Scheduler.xml file.

To prepare a processing batch (ICL) to be reprocessed by Risk Management, the states associated with Risk must be cleared for both the processing batch (ICL) and its associated inbound batch (ICL). Risk Management will not re-process a batch (ICL) if the states are not cleared. The processing states associated with Risk are:
  • RISK_REVIEWED
  • ACTIVITY MONITORED
  • AUTH_CHECKED
  • AUTH_REVIEWED
For Risk Management to re-process a batch (ICL), make sure that these states are not specified in the undo cancel preserve batch states property.