Queue processor processing
The Pega Smart Dispute™ Agentic Automation uses a queue processor to process the queue records retrieved from the Visa queue. Processing the queue involves resuming the current assignment and waiting for the opposite party's response to the corresponding dispute.
For example, in the case of a dispute response from the acquirer, the current dispute work object is at the stage of awaiting the acquirer response to the consumer dispute submitted. When the acquirer declines the dispute, the queue processor moves the dispute work object to process the acquirer response based on the input from the queue record supplied by the job scheduler.
The queue processors are dedicated messaging queues that receive input from the job scheduler. After initiating the queue processor, the next task is to initiate the default parameters and properties required for processing.
The queue processor in Pega Smart Dispute can currently run on a single thread per node and at a maximum of one retry in case of any failures. Customers can update these values in their layer based on the requirement.
Queue processor processing steps
Consider the following scenario: The system expects a dispute response from the Acquirer for a Consumer Dispute – Cancelled in the Recurring transaction category.
The queue processor uses the following process:
- The pre-processing activity PreProcessQueueItems takes care of setting up the preliminary values on the batch queue record before proceeding with the main task.
- The primary processing activity ProcessQueueItems fetches the appropriate work object based on the visacasenumber associated with the queue record.
- After fetching the prerequisite, the system begins processing the queue record. The system browses for the visacasenumber of the queue record in the local database for processing.
- If the corresponding work object that is mentioned in step 2
- exists, the processing activity resumes the current assignment of the work object which is performed in the activity VisaBatchQProcessWorkItem.
- The activity VisaBatchQProcessWorkItem handles copying the queue record information to work object and resuming the work object from the current assignment.
- The activity CopyBatchQItemToWork copies the relevant queue record information to work object by creating data transforms for each queue type (D Queue and S Queue).
- The activity VisaBatchQResumeWorkItem resumes the Visa work object. The resume action requires the flow name and flow action name of the assignment the work object is currently in. System gets these details from a decision table that is configured with all the possible scenarios that the system supports. The decision tables are marked as extension. So, the implementation team can change the flow names and flow action names based on their flow details.
- Based on the success or failure status of the resume action of the batch queue record, the activity UpdateQueueRecord updates the corresponding status parameters of the queue record. Along with updating the status of queue record the activity also takes care of checking if the batch queue needs a requeue of the current record based on the retry counter configured.
- Before exiting the control, the queue processor checks if the queue record is eligible for requeue.
- If the queue record is eligible for requeuing, the queue processor QueueVisaIssuerRecords again and clears the current error.
- Else, the control exits the queue processor.
- Execution status column hold below valid status values:
Execution Status
Description
New
Read from the Visa system and save in the Pega Smart Dispute database
In-progress
Queue processor selects a record for processing
Completed
Queue processor successfully processes the record
Error
Record fails because of exception during the processing the work object
Error - Retry limit exceeded
Record is retried due to an exception and exceeded the threshold retry limit
This Topic is available in the following Module:
Want to help us improve this content?