Issues addressed in this release
This table describes issues resolved in this release that are of the most interest to and are likely to have the most impact on the Pega user and developer community.
The following ID reference is used:
- Reference numbers beginning with “ISSUE ” 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.
Fixed issues in Pega 1:1 Operations Manager
|ID||Title and Description|
|ISSUE 589839||Incorrect error displayed to NBA Specialist working on a case when the stage has been changed by a team lead.|
|ISSUE 590248||User is unable to submit the Configure engagement policy task.|
|ISSUE 584447||On browser refresh of the test stage, empty tasks are created in the To do list.|
|ISSUE 592369||Preview does not load the details if you click Preview after refreshing the browser.|
|ISSUE 577647||Operators lose their current sorting when resizing the Change requests table on the Change requests landing page, as the table results sort automatically.|
|ISSUE 591013||In rare situations, after completing a task, the task does not disappear from the To do list.|Previous topic Decision Data Store as action state storage on Pega Cloud Next topic Known issues in this release