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.

Troubleshooting integration between Pega Customer Decision Hub for Financial Services and Pega Collections

Updated on September 10, 2021
Note: Starting in version 8.5, Pega Customer Decision Hub™ is Pega's main solution for 1:1 customer engagement, combining the features available in previous versions of Pega Marketing™ and Pega Customer Decision Hub with many new features. Pega Marketing is no longer available as a separate product.

If the integration between Pega Customer Decision Hub for Financial Services and Collections is not working, please ensure the following:

  1. In Pega Customer Decision Hub for Financial Services, configure the ConnectCRMURL dynamic system setting to have the endpoint URL of the Pega Customer Service for Financial Services instance to which you are connecting.
  2. In Pega Customer Service for Financial Services, configure the endpoint URL of the Pega Customer Decision Hub for Financial Services instance.
  3. Update the Customer Decision Hub configuration landing page. Click Designer Studio > Customer Service > Customer Experience > Customer Decision Hub configuration.
    This maps to a dynamic system setting called ConnectMKTURL.
  4. On the Customer Decision Hub configuration landing page, ensure that NBA Enabled is set to true and that the Advisor Server is set to the Pega Customer Decision Hub for Financial Services endpoint URL.
    To change these fields, click the blue label for each field.
  5. In Pega Customer Decision Hub for Financial Services, ensure that your decisioning topology has a node associated to it and that the agent status on that node is set to enabled.
  6. If your Agent status is not available, ensure that your marketing agents are enabled on the nodes required.
    For more information, see the Pega Customer Decision Hub Installation Guide.
  7. In Pega Customer Decision Hub for Financial Services, verify that at least one node is configured for each of your decisioning services and that the status of each node is normal.
    There should be a node configured for Decision Data Store, Adaptive Decision Manager, and Data Flow. Set one for Visual Business Director if you plan on using it. It is not used for the Collections functionality.
  8. If you are not getting offers in the NextBestAction REST service, it may be because your customer is in collections.
    The logic for this is defined in the eligibility criteria IsInCollections.
  9. If you are tracing the functionality, you may see errors in the SimpleProcessOffer activity. This activity is designed to error out on obj-open if the offer flow is new or has been previously resolved and there does not exist an instance of it in your DB table. Ignore this error in your tracer.
  10. You can test the service through SOAP UI or similar software. You can also run and trace the service method activity ProcessWSRequest.
    Note: The following values for the service and service method activity are required: RequestType, Account Number, CustomerID, and AccountType.
  11. If Pega Customer Decision Hub for Financial Services is not returning offers, ensure that the agent schedules in the application have been enabled. This includes: PegaMKT-Engine, PegaMKT-PushNotification, PegaMKT-FieldMarketing, and PegaNBAM-Artifacts.
    Note: If you have created the agent ProcessBatchJob as an agent schedule in your implementation layer, you should enable that one rather than the one in PegaNBAM-Artifacts.
  12. If your service returns successfully when initiating an offer, but your offer is not run or does not contain customer data, confirm that the context dictionary defined does not have a secondary context defined as a top level page or “parent” to your customer context. The customer context needs to be your top level context.
  13. If your right to cure offer is running, but you do not see the collections case updated with the right to cure mail or email, add a Wait shape prior to the collections interaction smart shape or update your Send email or Send sms shape to include a wait of a few seconds.

Tags

Pega Collections 8.3 - 8.4 Pega Marketing for Financial Services 8.3 - 8.4 Pega Customer Service for Financial Services 8.3 - 8.6 Pega Customer Decision Hub for Financial Services 8.5

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