Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Disputes FW queuing correspondence to Pega-Procom:Sendcorr

SA-13079

Summary



While generating the expedited billing forms for RC ( such as, 4855, 4841, 4837, 4860 and 4831), Disputes FW creates correspondence request and queues it to Pega-Procom:SendCorr agent.
This creates unnecessary records in the PR_SYS_Queue table which impacts the performance. 


Error Messages



Not Applicable


Steps to Reproduce



1. Create any MC case in Disputes Issuer or Acquirer.
2. Process the chargeback using any of the RCs (4855,4841,4837,4860,4831).
3. Wait for Expedited billing form to be generated.
4. Check the PR_SYS_QUEUE table for the correspondence request.


Root Cause



This behaviour is working as per design.

Resolution



This issue is resolved through the following local-change:

The change to remove the OOTB Queue needs to be performed from several places, based on the flow processing in the system. 

One of the general reference point to change is in the activity PegaCard-Sd-Dispute- • CallVerifySendCorr. The code flow for this is as below:

ACTIVITY     PegaCard-Sd-Dispute- • CallVerifySendCorr    calls the below Flow.
FLOW     Work- • VerifySendCorr    Pega-ProCom : 06-01-01  

This in turn calls the utility that calls the below activity.

ACTIVITY     Work- • CorrSend    Pega-IntegrationArchitect : 06-01-01  

Published August 27, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us