Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-119213 · Issue 178963

Updated flow default for SAE-I course

Resolved in Pega Version 7.1.8

The PRPC: System Architect Essentials I training course shows how to create draft process outlines. An SAE exercise where Stage "Decision" has steps "Background Check" and "Assess Candidate" which run in parallel was not working as expected. The first step is an assignment, and the second is a multi-step process with a decision shape which points to a decision tree. If that decision shape referenced an undefined decision record, the process would not execute and there was no way to proceed with the case. This was traced to the DRAFTMODECHOICE flow rule in which "Process commander internal flow" was checked by default. This was not the preferred work flow behavior, and the default is now to leave "Process Commander Internal Flow" unchecked so the flow is not marked as internal. In addition, the instructions for DraftModeChoice assignment were modified to reflect this change.

SR-119376 · Issue 179579

Resolved checkout conflicts with discarded rule edits

Resolved in Pega Version 7.1.8

After a private edit of a work flow rule in the tenant layer, discarding that rule and then trying to do another Private Edit on the same rule generated the error "Status: **Check out failed. A checked out version with the same keys already exists. Please check-in that record first. This was traced to an issue with the clipboard retaining the discarded rule, and has been corrected.

SR-119762 · Issue 176867

Case Manager search accessibility enhancement

Resolved in Pega Version 7.1.8

The 'Search' field in CaseManager has been enhanced to be more informative for end users to perform tasks and includes information that the follow-on menu holds options for 'search by' criteria. In addition, the 'Landmark Menu' has been provided with a search field for quick navigation and accessibility.

SR-119780 · Issue 175524

Added accessibility for CalendarViewGadget's month switch

Resolved in Pega Version 7.1.8

The CalendarViewGadget's month switch arrow buttons/icons have been updated to support navigation with the keyboard and respond to the TAB key, allowing full access to this function within the accessibility framework.

SR-120381 · Issue 179868

TopLevelClass updated to accept a hyphen in the name

Resolved in Pega Version 7.1.8

Previously, the new application wizard Top-Level class did not support the use of a dash between two ruleset classes. An enhancement has been added to allow this format.

SR-120518 · Issue 180099

Corrected error handing on"Post Action on Click Away"

Resolved in Pega Version 7.1.8

When an assignment in a screen flow was configured to use the "Post Action on Click Away" setting, it was not possible to go back if there were validation messages on the screen. Without the "Post Action on Click Away" setting, the click back worked and the validation message was cleared by the jumpToTask activity. This work flow issue has been fixed by clearing the page error messages before calling performflowaction.

SR-120566 · Issue 181231

Bulk Actions filtering error resolved

Resolved in Pega Version 7.1.8

In Bulk Actions, if a filter was renamed from "Assigned to Operator" to something else, ex "Application ID", the filter was not being applied. If the "Assigned to Operator" filter was deleted and a new one added, the filter was applied correctly. This was found to be an issue with the filters "Assigned to Operator" and "Assigned to Workbasket" setting the flag pyUsage = operator on the filter condition, causing a custom SQL to be generated. This has been corrected.

SR-120585 · Issue 182421

Work object history corrected for failed flow action submissions

Resolved in Pega Version 7.1.8

If a a flow action is submitted which encounters errors and generates Page-Messages, correcting the errors and re-submitting the flow action created duplicate entries in the work object history that included entries for the failed flowaction submission. This was caused by improper rollback of the addhistory when the commit of the WO is rolled back, and has been corrected.

SR-120586 · Issue 179198

Assignment dependencies with child cases now properly resolve

Resolved in Pega Version 7.1.8

Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.

SR-120586 · Issue 178686

Assignment dependencies with child cases now properly resolve

Resolved in Pega Version 7.1.8

Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.

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