Implementation class structure update
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 Name | Rule Type | Applies to | Ruleset |
| LoadVCRConfiguration | Data Transform | PegaCard-Interface-Admin-Visa-VCRConfiguration | PegaCardSdVisa |
| ATMDisputeDT | Decision Tree | PegaCard-Sd-Dispute | PegaCardSd |
| GenericDisputeDT | Decision Tree | PegaCard-Sd-Dispute | PegaCardSd |
| InterlinkDisputeDT | Decision Tree | PegaCard-Sd-Dispute | PegaCardSd |
| MaestroDisputeDT | Decision Tree | PegaCard-Sd-Dispute | PegaCardSd |
| MasterCardDisputeDT | Decision Tree | PegaCard-Sd-DisputeAcq | PegaCardSdAcquirerMC |
| NachaDisputeDT | Decision Tree | PegaCard-Sd-Dispute | PegaCardSd |
| PulseDisputeDT | Decision Tree | PegaCard-Sd-Dispute | PegaCardSd |
| VisaDisputeDT | Decision Tree | PegaCard-Sd-DisputeAcq | PegaCardSdAcquirerVisa |
| DynamicReferenceForWorkClass | Data Transform | PegaCard-Interface-Admin-AppExtension | PegaCardSdAcquirer |
Previous topic Creating your application Next topic Updating the dispute decision tree matrix