Skip to main content


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

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.

Integrating Pega Customer Service for Financial Services and Smart Dispute

Updated on October 24, 2022

Integrating Pega Customer Service for Financial Services (CSFS) 7.21 with Smart Dispute (SD) 7.21 allows front-line customer service representatives (CSRs) to capture all of the customer information that is required to resolve a dispute at the first point of customer contact.

Prerequisites

Before integrating Pega Customer Service for Financial Services with Smart Dispute, ensure that the following applications are installed in the following order:

  1. Pega 7.21
  2. Pega Customer Service 7.21
  3. Financial Services Industry Foundation 7.21
  4. Service Case Manager for Financial Services
  5. Pega Customer Service for Financial Services 7.21

Importing the JAR files

Import the CSFS-SD JAR files that are included with the Pega Customer Service for Financial Services 7.21 and Smart Dispute 7.21 resource kits.

  1. Log in to Designer Studio.
  2. Click Designer Studio > Application > Distribution > Import.
  3. Click Choose File. From the Pega Customer Service for Financial Services 7.21 resource kit, browse to and select \ResourceKit\PegaCSFS_SmartDispute_721.jar.
  4. Click Choose File. From the Smart Disputes 7.21 resource kit, browse to and select \ResourceKit\Rules\SmartDisputeCSFS_07.21.jar.
  5. When the import is complete, click Done.
You must apply any required hotfixes to Pega Customer Service for Financial Services and Smart Dispute. For more information, see the Hotfixes supporting CSFS-SD integrations section on the Pega Customer Service for Financial Services Hotfixes page.

Deleting the USER4 rule

In Pega Customer Service for Financial Services 7.21, you must delete the PegaRULES: USER4 user role that comes out-of-the-box with the Pega 7 Platform.

To delete the PegaRULES: USER4 rule, complete the following steps.

  1. Log in to the database using the Database administrator credentials. For more information about the database, contact your Database administrator or System administrator.
  2. In pr4_rule, run the following query:
    pxinsid =''PEGARULES:USER4!ASSIGN-WORKBASKET' and pyruleset='PegaFSSCM'
  3. Delete the rule and save the changes.

Clearing the cache

The System Management Application (SMA) maintains a memory cache of recently used rules, especially during rule resolution searches. Once the USER4 rule is deleted, you must log in to the System Management Application to clear its caches.

Clearing the rule cache

To clear the rule cache, complete the following steps.

  1. Log in to your application.
  2. Click Designer Studio > System > Operations > System Management App. You might be prompted for authentication credentials.
  3. On the System Management form, select a node.
  4. Click Advanced > Rule Cache Management.
  5. Click Clear.

Clearing the static files

To clear the static files, complete the following steps.

  1. Log in to your application.
  2. Click Designer Studio > System > Operations > System Management App. You might be prompted for authentication credentials.
  3. On the System Management form, select a node.
  4. Click Advanced > ETier Static Content Management .
  5. Click Delete Rule-File and Service Export.

Clearing the Declarative Page cache

To clear the Declarative Page cache, complete the following steps.

  1. Log in to your application.
  2. Click Designer Studio > System > Operations > System Management App. You might be prompted for authentication credentials.
  3. On the System Management form, select a node.
  4. Click Advanced > Declarative Page.
  5. Click Clear.

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