Batch queue processing configurations and extension points

There are two configurations associated with the functionality of processing pending transactions.

Enable processing pending transactions

This setting is used for enabling or disabling dispute processing for pending transactions.

Pending clearing threshold days

The setting is used to specify the number of threshold days to wait for the clearing transaction to be available before the case is resolved automatically.

Pega Smart Dispute Agentic Automation marks the below data transforms, activities, decision tables and when rules for enabling customer customization.

Data Transform: LoadVisaBatchQueueConfig, LoadVisaBatchQueueConfig_Ext

This rule is used for loading values for Visa batch queue processing. This is utilized in the LoadVisaServiceConfig data transform.

Data Transform: SetBatchQReadPageNumberSequence_Ext

By default, batch queue items are read per page, starting from page number 1 to the last page number present for the given queue. To modify this reading sequence, this rule can be extended at the implementation layer.

Decision Table: ValidateQueueItemForSDProcessing

This rule is used to validate the queue type and case status, determining whether the case can be processed in Service Desk (SD) or not. If the queue item is valid, the ExecutionStatus property value is set accordingly. Based on the return value, records will be stored in the specific queue type tables. This rule is utilized in the SaveQueueItems activity and can be extended by clients to support additional case statuses.

Decision Table: ValidateQueueItemForMultipleQueueAvailability

This rule is used to validate the queue type and case status, returning a parameter that indicates whether the given batch queue item is present in multiple queues. If the record is found in multiple queues, the ExecutionStatus property value is set to Resolved-DuplicateItem. Based on this return value, records will be stored in the specific queue type tables. The MarkBatchQueueItemAsRead API will be called for this record; however, this duplicate item record will not be queued to the Queue Processor for processing. This rule is utilized in the SaveQueueItems activity.

When: IsValidSavableBatchQueueItem

This condition is used to check if a given batch queue record is valid for saving in the database. It serves as an extension point for clients, allowing them to add any specific implementation layer conditions as needed.

Activity: SaveQueueItems

This rule is used to save individual Visa Queue items to the database and is utilized in the SaveVisaQueueItems activity.

Activity: SaveOtherQueueItems

This rule is used to save items in the OTHER queue. It serves as an extension for saving OTHER type records and is utilized in the SaveQueueItems activity.

Decision table - FlowNameLookUpForDQueue

A decision table is configured with the batch queue names and their corresponding case statuses received in the Visa queue, along with the respective flow names and flow action names of the Visa case type in the system. These flow names and flow action names enable the system to appropriately resume the work object to the next available assignment in the process.