Skip to main content

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

Known issues in version 8.7

Updated on August 22, 2022

This section describes the known issues in this version.

Pega Customer Decision Hub Release Notes

The following ID reference is used:

  • Reference numbers beginning with “ISSUE ” or “BUG” refer to bugs logged in the Pega issue-tracking system.
  • Reference numbers beginning with “INC-” or “SR-” refer to corresponding Support Requests logged in My Support Portal.

Known issues in Pega 1:1 Operations Manager

IDDescriptionSuggested Resolution
BUG-671823Whenever an action is created from a Standard Change Request, a message with the word Good is displayed at the bottom of the Action in the Pega Customer Decision Hub portal.Avoid creating actions using the Standard Change Request. Actions should be created and updated using Operations Change Request in the Pega 1:1 Operations Manager application.
BUG-604785Change Requests are unable to complete the Build stage due to a build failure in the child cases OpsCA and OpsUA. This occurs due to parallel processing where multiple operators are completing the Build stage at the exact same time.Avoid completing the last Build stage task at the exact same time as other users. If this occurs, log into the system as CDH Administrator and remove duplicate rules from the 1:1 Operations Manager branch. Post this rework on the Failed OpsCR by moving the OpsCR into Plan stage.
ISSUE 578834No warning appears if you enter Engagement Policy conditions in the Plan stage and then click Next without confirming the selection.See "Issue:Engagement policy details were not saved" in Troubleshooting for more information about confirming the selection. This issue will be fixed in an upcoming release.
BUG-675828Change Requests show a dependency to a When condition that is in fact not a dependency.This happens when you create When rule from standard CR, then create new action from standard CR and update same action from OpsCR to add or use When rule (which got created as part of first standard CR) in configure engagement policy. When we will see the dependency for When rule then it's showing the 2nd standard CR as well, but When rule was not used as part of 2nd standard CR.
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 (INCs) in My Support Portal. Ensure that you refer to the issue ID in all communications.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us