Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Implementation class structure update

Updated on June 22, 2022

The following rules are responsible for setting the name of the class for corresponding pyWorkPage for disputes.

Pega Smart Dispute for Acquirers Implementation Guide

These rules need to be overridden with corresponding implementation work class if implementation application is built on SD OOTB application. If new application 'Pay' is built on SD out-of-the-box application for organization 'ABC', then class structure would be as following:

SD Claim class: PegaCard-Sd-Claim

New Implementation class: ABC-Pay-Work-Claim

Rule NameRule TypeApplies toRuleset
LoadVCRConfigurationData TransformPegaCard-Interface-Admin-Visa-VCRConfigurationPegaCardSdVisa
ATMDisputeDTDecision TreePegaCard-Sd-DisputePegaCardSd
GenericDisputeDTDecision TreePegaCard-Sd-DisputePegaCardSd
InterlinkDisputeDTDecision TreePegaCard-Sd-DisputePegaCardSd
MaestroDisputeDTDecision TreePegaCard-Sd-DisputePegaCardSd
MasterCardDisputeDTDecision TreePegaCard-Sd-DisputeAcqPegaCardSdAcquirerMC
NachaDisputeDTDecision TreePegaCard-Sd-DisputePegaCardSd
PulseDisputeDTDecision TreePegaCard-Sd-DisputePegaCardSd
VisaDisputeDTDecision TreePegaCard-Sd-DisputeAcqPegaCardSdAcquirerVisa
DynamicReferenceForWorkClassData TransformPegaCard-Interface-Admin-AppExtensionPegaCardSdAcquirer

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us