Skip to main content


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

Importing the application bundle

Updated on June 22, 2022

Use the Import wizard to import the system data and rulesets for Pega Smart Dispute for Issuers to Pega Platform.

Pega Smart Dispute for Issuers Installation Guide
  1. Log in to Pega Platform at https://hostname:port/prweb with the administrative ID and password that you set up during the installation of Pega Platform.
    For example: [email protected]
  2. In the header of Dev Studio, click ApplicationDistributionImport and perform the following actions:
    1. Depending on your web browser, click Browse or Choose File, select the \Rules\SmartDispute_Base_Schema_87.jar file from your SmartDispute Base distribution image, and then click Next.
    2. Ensure that you import all components by leaving the Enable advanced mode to provide granular control over the import process check box cleared, and then click Next.
      Result: The wizard identifies differences between the database schema of your current system and the schema of Pega Smart Dispute for Issuers 8.7.
    3. If the file that you are importing requires changes to the database schema, select Automatic and then click Next.
    4. Follow the instructions on the screen, and when the import is completed, click Done.
    5. If there are column length issues encountered during the installation process, increase the length of the following table columns to the length given below in parentheses:
      • PR_INDEX_REFERENCE MODIFY PXREFERENCINGDESCRIPTION VARCHAR(128)
      • PR_INDEX_REFERENCE MODIFY PXRULEFAMILYNAME VARCHAR(192)
      • PR_INDEX_REFERENCE MODIFY PYRULENAME VARCHAR(192)
      • PR4_RULE_PROPERTY MODIFY PYLABEL VARCHAR(128)
      • PR4_FIELDVALUE MODIFY PYLABEL VARCHAR(128)
      • PR4_RULE_VW MODIFY PYLABELVARCHAR(128)
      • PR4_RULE_SECTION PYLABEL VARCHAR(128)

      Query changing the column length: ALTER TABLE <RULESSCHEMA>.PR_INDEX_REFERENCE MODIFY PXREFERENCINGDESCRIPTION VARCHAR(128);

  3. The SmartDispute_Base_Schema_87.jar file contains the following third-party files that require an application restart, follow the instructions on the screen to restart the app server.
    • jai imageio-1.1.jar
    • pdfbox-app-2.0.6.jar
    • sdk-api-core-1.4.19.jar
    • signpost-core-1.2.1.2.jar
  4. Repeat steps 2.a to 2.e for the following files from your distribution image:
    Smart Dispute Base
    • Rules\SmartDispute_INT_87.jar (shared layer)
    • Rules\SmartDispute_Base_87.jar (shared layer)
    • Rules\SmartDispute_Debit_87.jar (shared layer)
    • Rules\SmartDispute_Base_Config_Data_87.jar (tenant layer)
    Smart Dispute Visa
    • Rules\SmartDispute_Visa_Schema_87.jar (shared layer)
    • Rules\SmartDispute_Visa_87.jar (shared layer)
    • Rules\Canada\SmartDispute_Visa_Canada_87.jar (shared layer)
    • Rules\AP\SmartDispute_Visa_AP_87.jar (shared layer)
    • Rules\LAC\SmartDispute_Visa_LAC_87.jar (shared layer)
    • Rules\CEMEA\SmartDispute_Visa_CEMEA_87.jar (shared layer)
    • Rules\Europe\SmartDispute_Visa_Europe_87.jar (shared layer)
    • Rules\US\SmartDispute_Visa_US_87.jar (shared layer)
    • Rules\Interlink\SmartDispute_Visa_Interlink_87.jar (shared layer)
    • Rules\SmartDispute_Visa_Config_Data_87.jar (tenant layer)
    Smart Dispute Mastercard
    • Rules\SmartDispute_MasterCard_Schema_87.jar (shared layer)
    • Rules\SmartDispute_MasterCard_87.jar (shared layer)
    • Rules\SmartDispute_MasterCard_Config_Data_87.jar (tenant layer)
    • Rules\Maestro\SmartDispute_Maestro_87.jar (shared layer)
    Smart Dispute AMEX
    • Rules\SmartDispute_AMEX_87.jar (shared layer)
  5. Conditional: If integration with Ethoca and/or Verifi is required, install the relevant following files available in Smart Dispute Base package in the shared layer:
    • SmartDispute_Base\ResourceKit\Rules\SmartDispute_Base_Ethoca_87.jar
    • SmartDispute_Base\ResourceKit\Rules\ SmartDispute_Base_Verifi_87.jar
  6. Conditional: If Customer Service for Financial Services (CSFS) implementation is required install the following files available in Smart Dispute Base package in the shared layer:
    • SmartDispute_Base\ResourceKit\Rules\SmartDispute_CSFS_87.jar
  7. Conditional: If Pega Smart Dispute for Unified implementation is required install the following file available in Smart Dispute Base package in the shared layer:
    • SmartDispute_Base\ResourceKit\Rules\SmartDispute_Unified_87.jar
  8. Conditional: If Pega Smart Dispute for Unified implementation along with Payment Exception Recovery is required, install the following file available in Smart Dispute Base package in the shared layer:
    • SmartDispute_Base\ResourceKit\Rules\PaymentExceptionRecovery_Schema_87.jar
    • SmartDispute_Base\ResourceKit\Rules\PaymentExceptionRecovery_Base_87.jar
    • SmartDispute_Base\ResourceKit\Rules\PaymentExceptionRecovery_Config_Data_87.jar
    • SmartDispute_Base\ResourceKit\Rules\PaymentExceptionRecovery_Zelle_87.jar
    • SmartDispute_Base\ResourceKit\Rules\PaymentExceptionRecovery_Unified_87.jar
  9. Patch release changes

    To import the patch release changes or incremental code changes post GA, please proceed to the designated \Patch folder available in the package and then import the .jar files according to your implementation.

    For example, SmartDispute Base package patch release changes are available under:

    • ..\Patch\SmartDispute_Base_Patch.jar
    • ..\ResourceKit\Patch\PaymentExceptionRecovery_Base_Patch.jar
    Note: After importing the jars, clients are recommended to manually review all the non-versioned rules, such as Data-Admin-System-Settings (DSS) and Data-Admin-Workbasket, and update the values according to the business requirements.
    Visa data patch jars contain a complete set of data instances for dispute validations and supporting documents to reset the Smart Dispute for Issuers application. Installing the package replaces your current set of dispute validations and supporting documents data records.

    If any custom extensions were made to the dispute validations or supporting documents by a customer, these get overwritten. Therefore, make a record of these extensions before installing this package to avoid losing any custom content.

    Execute the scripts below before importing the hot fix. This action deletes all dispute validations and supporting documents instances in your current setup

    Backup options
    Use the option of Export to Excel from the data types:
    • Dispute Validations of class PegaCard-Interface-AdminDisputeValidations
    • Supporting Documents of class PegaCard-Interface-Admin-VisaDocuments
    Have a backup/clone of the existing tables:
    • pr_PegaCard_Interface_Admin_Di
    • pr_PegaCard_Interface_Ad_67b6a
    SQL scripts
    DELETE FROM PR_PEGACARD_INTERFACE_ADMIN_DI
    DELETE FROM PR_PEGACARD_INTERFACE_AD_67B6A; COMMIT
    Note: If necessary, modify the script accordingly based on the database.
  10. Optional: For the best performance and user experience, pre-assemble the rules in the application by running the Static Assembler utility.
  11. Ensure the Pega Platform for Financial Services (PFFS 8.7) HFix-83482 is installed and any other hot fixes released on Pega Platform for Financial Services (PFFS 8.7) are installed.
  12. Verify that the new application rule appears by performing the following actions:
    1. In the Explorer panel, click Records Application Definition Application
    2. Verify that following rules appear in the list of built on applications:
      ApplicationPlatform 8.x
      SmartDisputeIssuerAll8
      SmartDisputeBaseSchemes8
      SmartDisputeBase8
  13. To configure Ethoca and Verifi components in Pega Smart Dispute for Issuers, in Designer Studio, open the SmartDisputeBase application rule and add the required components.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us