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 20, 2022

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

Pega Smart Dispute for Acquirers Update Guide
Before you begin:
Note: If you are upgrading Smart Dispute for Acquirers in a Multi-Tenant environment, for the application to function correctly, you must install each component into the layer listed.
  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 Acquirer 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 Acquirers 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 update 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 SmartDisputeBase_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 Acquirer Base
    • Rules\SmartDispute_Base_87.jar(shared layer)
    • Rules\SmartDispute_INT_87.jar (shared layer)
    • Rules\SmartDisputeAcquirer_Base_87.jar (shared layer)
    • Rules\SmartDispute_Base_Config_Data_87.jar (tenant layer)
    Smart Dispute Acquirer Visa
    • Rules\SmartDispute_Visa_Schema_87.jar (shared layer)
    • Rules\SmartDisputeAcquirer_Visa_87.jar (shared layer)
    • Rules\AP\SmartDisputeAcquirer_Visa_AP_87.jar (shared layer)
    • Rules\Canada\SmartDisputeAcquirer_Visa_Canada_87.jar (shared layer)
    • Rules\CEMEA\SmartDisputeAcquirer_Visa_CEMEA_87.jar (shared layer)
    • Rules\Europe\SmartDisputeAcquirer_Visa_Europe_87.jar (shared layer)
    • Rules\LAC\SmartDisputeAcquirer_Visa_LAC_87.jar (shared layer)
    • Rules\US\SmartDisputeAcquirer_Visa_US_87.jar (shared layer)
    • Rules\SmartDispute_Visa_Config_Data_87.jar (tenant layer)
    Smart Dispute Acquirer Mastercard
    • Rules\SmartDispute_MasterCard_Schema_87.jar (shared layer)
    • Rules\SmartDisputeAcquirer_MasterCard_87.jar (shared layer)
    • Rules\SmartDispute_MasterCard_Config_Data_87.jar (tenant layer)
  5. 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 Acquirer base package patch release changes are available under:
    • ..\Patch\SmartDispute_Base_Patch.jar
  6. Optional: For the best performance and user experience, pre-assemble the rules in the application by running the Static Assembler utility.
  7. 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.
  8. 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
      SmartDisputeAcquirerAll 8
      SmartDisputeBaseSchemes8
      SmartDisputeBase 8
      Note: The Dynamic System Settings (DSS) shipped are as part of the application are set to default values. Ensure the values are updated as per business requirement before the initial testing is started.

Tags

Smart Dispute for Acquirers 8.7

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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