Skip to main content

 –

Known issues in Pega Customer Decision Hub 8.5

Suggest edit Updated on June 22, 2021

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

Known issues in Pega Customer Decision Hub

IDDescriptionSuggested Resolution
BUG-595845Actions initiated by an additional outbound schedule configured for a context that is a child of the primary context will fail.In order to avoid these failures, additional outbound schedules should be configured for the primary context and parent contexts only. It is recommended that in place of an outbound schedule for a child context, a primary context schedule is created. The segment selected as the starting population can be created using criteria of the child context. Action engagement policies can also be used to limit the actions' availability.

Known issues in Pega 1:1 Operations Manager

IDDescriptionSuggested Resolution
BUG-564372User is unable to select an action to be updated if that action was created in the same revision.Complete the revision, and then update the action in a new revision. This issue will be fixed in an upcoming release.
BUG-578834In the Plan stage, on Define engagement policy, if the user does not hit enter to change the entered text into a pill, the condition does not get persisted.Make sure that all conditions have become encapsulated in a grey pill by clicking Use this or hitting enter before you continue past this screen.
BUG-582495Multiple NBA Specialists are not able to work concurrently on different tasks in the Build stage.Delivery teams should enable opportunistic locking as part of implementation application on the revision case. Once you do this, multiple NBA Specialists will be able to work on different tasks at the same time. This issue will be fixed in an upcoming release.
BUG-589839Incorrect error displayed to NBA Specialist working on a case that has been change staged by a team lead.Before changing the stage of a case, the team lead should ask all team members to exit out of their assignments to prevent this issue. This issue will be fixed in an upcoming release.
BUG-590248User is unable to submit the Configure engagement policy task. There are errors on the Configure engagement policy task that occur only when you use the Save to library option. You must fix the errors before you can continue. Review the screen for missing conditions. If all conditions are defined, rename the conditions used, as the error can occur if you give a condition a name that already exists in the system.
BUG-584447On browser refresh of the test stage, empty tasks are created in the To do list.Ignore the empty tasks. The stage should still proceed when you complete the actual tasks in the Test stage.
BUG-592369Preview does not load the details if you click Preview after refreshing the browser.Close the Preview window, and then click Preview again. It will open the second time you click on it.
ISSUE-79326A green section with the Get next button appears above the To do list when no further work remains for the operator. Clicking the Get next button does not do anything.Ignore this button. Instead click the Home or Change requests landing page.
ISSUE-66384After all tasks are completed on a change request no instructions or visible tasks are shown, and there is no way to close the Change request case.Click on the Home or Change requests landing page and continue working as usual. This issue will be fixed in an upcoming release.
BUG-577647Operators lose their current sorting when resizing the Change requests table in the Change requests landing page, as the table results sort automatically.Avoid resizing the Change requests table. This issue will be fixed in an upcoming release.
BUG-591013In rare situations, after completing a task, the task does not disappear from the To do list.Refresh the browser and the task should disappear.

Known issues in Pega Customer Decision Hub simulations

IDDescriptionSuggested Resolution
ISSUE 653572In the value finder simulation type, the recall is wrongly calculated in the details of the second and third groups of under-served.A workaround possible as all counts are available. The number of under-served customers in the group should be divided by the overall number of under-served customers in the audience at this stage. This measure shows what fraction of all under-served customers in the audience value finder retrieves for this group instead of node recall. See Analyzing group descriptions for more information about under-served customers in a group. This issue will be fixed in an upcoming release.
ISSUE 646625In the ethical bias simulation type, the bias is falsely detected if the measured bias value is exactly the same as the boundary of the confidence interval (for example 0).This issue will be fixed in an upcoming release.
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#.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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