4.3 Custom Queue Processing

Custom Queues support is provided for Outbound Cross border/RTGS/Book Transfer transactions as part of initial processing stage.

The Custom queue rules are evaluated on completion of future value check for processing on Booking Date. If Booking dated validations are set as not required, Custom Queue validations are done for current dated transactions only.

If any rule is satisfied, system marks the transaction as exception with custom queue code linked. The transaction is stored in a separate table for the custom queue processing. Custom Queue / Queue actions / Queue action log are to be handled in the extension layer.

Once the custom queue processing is over, transaction can be sent back to the product processor for proceeding with the processing. A rest service is provided for the same.

If resultant status can be TRUE (Approved) or FALSE (Rejected). If the processing is approved, then transaction status is updated as 'In Progress', Queue code gets removed. Transaction will proceed with Document verification and Non STP queue validations.

If resultant status is rejected, transaction is marked as Cancelled.

On completion of Custom Queue check, Document Verification/Non STP Queue Check and other Process Exception /Business Override /Repair validations are done, as existing.

Note:

• Queue Browsers are to be created in the custom layer with required actions.
• Custom Queues can be placed only before system queues and inserting custom queues in between system queues not supported.
• Modification of field values is not allowed.