Skip to main content


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

Known issues in Pega Customer Decision Hub for Financial Services 8.5

Updated on August 28, 2020

This table describes the known issue that might occur in this release.

IDDescriptionSuggested Resolution
BUG-537181Seed lists fail after upgrading from Pega Customer Decision Hub 8.x.Run the activity PegaMKT-Data-SeedList.UpdateSeedListClass.
BUG-420445When creating an action, if the decision data rule tied to that action is checked out, an incorrect validation message displays.Determine if the decision data rule related to the action is checked out or is in a locked ruleset version. If it is, check it in or copy it to an unlocked ruleset version.
BUG-420163Email treatment is not sent in actions for Pega Collections when used with the Collections Interaction smart shape.Create an email template rule with the same name as the email treatment rule.
BUG-288167When opening an action from an email, propensity in the interaction history is captured as zero.

The action being opened from an email is captured in the interaction history as an impression event with the channel set as Email. However, the propensity value is blank.

Propensity should be used to determine the likelihood of a customer clicking the email ad after receiving it.

This is expected to be a future enhancement feature from Pega Customer Decision Hub.

ISSUE-31318The Collections Interaction smart shape does not update the Pega Collections case in Pega Customer Service for Financial Services.This occurs because of locking issues in the Pega Collections case. Add a delay of a few seconds on the Flow tab of the action by using one of the following resources:
  • In the Properties dialog box of a Send Email or a Send SMS shape, use the Offset option.
  • Insert a Wait shape before the Collections Interaction smart shape.
ISSUE-31319In Pega Collections, you cannot initiate an action from the ProcessWSRequest SOAP service on the InitiateOffer request type, unless Customer set as the primary context in the Pega Customer Decision Hub context dictionary.Ensure that Customer is set as the primary context of the Pega Customer Decision Hub context dictionary.
BUG-522031After generating a new implementation layer, the CustomerID property appears in the context dictionary.In the relevant records of your implementation customer class, set the CustomerID property as irrelevant.
Note: To submit new issues or find out more about known issues, or to request a hotfix, go to the Pega Product Support Community. Look up or subscribe to your Support Requests (SRs) in My Support Portal. Ensure that you refer to the issue ID (SR, BUG, or FDBK) in all communications.Tip: You can look up Pega Platform bug fixes in the Pega Platform Release Notes. If you know a BUG#, that number becomes the Issue#.
  • Previous topic Prediction Studio enhancements
  • Next topic Upgrading from prior versions of Pega Customer Decision Hub for Financial Services

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