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-A17175 · Issue 234726

Corrected results display for upgraded pysearchResultWork filters

Resolved in Pega Version 7.2.1

When applying the pysearchResultWork filter on the native work objects search bar, some results were not displayed as expected after upgrade. This was caused by an error in setting the property for ad hoc cases inside a child activity, and has been fixed.

SR-A17183 · Issue 241734

Swimlane flow connectors visible after upgrade

Resolved in Pega Version 7.2.1

After upgrade, some of connectors between the flow shapes were not appearing as expected when opening flow rules forms designed with Swimlane even though the flows ran as expected. Attempting to amend the flow rules by reconnecting the shapes caused the ruleform save to fail. This issue stems from problems opening the Decision Tree rule Data-MO-Connector-Transition.pyBuildLabel on a Pega 7.1.8 system. This has been fixed.

SR-A17193 · Issue 236190

Custom height settings retained for progress bars

Resolved in Pega Version 7.2.1

After upgrade, the settings contained in the final rule pzjquery_ui_progressbar_dotluv CSS were overriding custom height settings for progress bars. The code has been updated to ensure custom settings are retained.

SR-A17223 · Issue 238044

Fixed JS error for Date Calendar changes

Resolved in Pega Version 7.2.1

Using Microsoft Internet Explorer, the Date Calendar was intermittently throwing a JavaScript error when trying to select another date from the date picker. This was caused by the rapid changing of dates overwhelming the onChange refresh section configured on the date input and leaving a stale input element, and has been fixed.

SR-A17399 · Issue 233769

Cleared authentication requirement check box for PZINVOKECASETYPE

Resolved in Pega Version 7.2.1

SOAP clients were not able to execute authenticated activities (DATA-PARTY-PERSON VALIDATE , WORK-COVER- PZINVOKECASETYPE) due to the out-of-the-box final activity pzInvokeCaseType having 'Require authentication to run' default to checked. This default interfered with the ability to remove a covered case from a cover case, and has been changed.

SR-A17403 · Issue 236170

Microsoft Internet Explorer browser check added to screenshot tool

Resolved in Pega Version 7.2.1

When closing an Microsoft Internet Explorer browser tab with an interaction open, an error is generated relating to the create snapshot tool. This screenshot functionality is only supported in Microsoft Internet Explorer8 and Microsoft Internet Explorer9, and a browser check has been added.

SR-A17411 · Issue 234053

Alignment resolved for repeating grid headers

Resolved in Pega Version 7.2.1

Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.

SR-A17476 · Issue 234924

Autocomplete working on node level data pages

Resolved in Pega Version 7.2.1

The auto complete feature was not working if the Categorize search results option was checked on node level data pages. The SortClipboardData now has support for node level data pages categorization.

SR-A17560 · Issue 234697

Added dynamic check to HarnessPurpose parameter

Resolved in Pega Version 7.2.1

If a main flow referenced a subflow with a parameter "HarnessPurpose" and value "Perform", accessing the subflow generated the error "Failed to find instance XXX-Work-Test.Param.HarnessPurpose of type Rule-HTML-Harness." This was an issue where the HarnessPurpose parameter caused a reset of the pxFormName property in the newassignPage, and this has been fixed by checking if the harnesspurpose is dynamic before setting the pxFormName.

SR-A17670 · Issue 236156

New display control for attachment category delete privilege

Resolved in Pega Version 7.2.1

If an attachment category delete privilege was set to 'never' but there was no access group referenced for it, it was possible for the user to delete the attachment. This was a scenario where even though the delete-all option was enabled for the attachment category, the display of the delete icon was not controlled by this access specifier. A new when condition "HaveAttachmentDeletePrivileges" has now been added on the delete icon to control whether or not the icon appears.

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