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-128580 · Issue 199345

Localization added for Audit screen

Resolved in Pega Version 7.1.8

Localization was missing from the 'Complete Task' section of the Audit screen. This has been added.

SR-128620 · Issue 193739

MapCases error resolved with blank page check

Resolved in Pega Version 7.1.8

The MapCases function was generating sporadic errors at a Wait Shape or after Updatestatus that required a logout/login before it was possible to proceed with the Case. MapCases runs tools.findPageByHandle(coverinskey) which can lead to an empty page being returned by the engine if one exists, leading to this error; a blank page check has been added that will then use the default work page if the cover key is empty.

SR-128634 · Issue 195936

Enhanced authentication setting carryover

Resolved in Pega Version 7.1.8

An issue was found with calling out-of-the-box authenticated activities from unauthenticated service activities. For example, when the declare page reload was triggered by a SOAP request (e.g. soap request creates new work which refers to the declare page), the report definition failed with an error saying that the requestor was not authorized to execute pxRetrieveReportData. This happened even though the SOAP Service Package and data page load activity had been set up to not require authentication. This authentication conflict was caused by the rule resolution disregarding the initial setting skipping authentication when it encountered the authentication requirement for the pxRetrieveReportData activity. This has been resolved by setting the authentication requirement to be applied to all rule execution in the same requestor.

SR-128670 · Issue 194884

Fixed removal of uncommitted hotfixes

Resolved in Pega Version 7.1.8

If a hotfix was installed in an environment but not committed, attempts to un-install the hotfix via System -> Tools -> Update Manager -> Uncommitted Hot fixes failed with the error "The following hotfixes could not be rolled back due to an exception". This was caused by the system not being able to switch threads context from the clipboard viewer, and has been corrected.

SR-128676 · Issue 194416

Existing BIX pr_extract_time tables preserved during install

Resolved in Pega Version 7.1.8

In older versions of the software, the pr_extract_time table was created by the core PRPC installation. This table creation was recently moved to the installation of BIX, but the system was improperly dropping this table from the data schema if it already existed during installation. This has been corrected.

SR-128689 · Issue 194302

Enabled line wrap for Display Shortcuts in RD

Resolved in Pega Version 7.1.8

Report definition was cutting off a long description rather than wrapping it to a new line. This was traced to pzDisplayShortcuts (a final rule) not being set to wrap text, and that setting has now been enabled.

SR-128701 · Issue 194839

getPropertyValue name collision resolved

Resolved in Pega Version 7.1.8

In order to accommodate custom RUFs called 'getPropertyValue', the Pega version of the rule is now called with full Library qualification.

SR-128714 · Issue 198058

Checks added to harness unload at logoff

Resolved in Pega Version 7.1.8

pyDeleteDocumentPg and pyOnBeforeWindowClose requests that happen on harness unload were causing 500/401 errors when called after logoff request. These calls are now prevented with logoff checks in harnessOnBeforeUnload.

SR-128720 · Issue 194443

Fixed CSS styling for buttons in repeating layouts with refresh

Resolved in Pega Version 7.1.8

Buttons in repeating layout are meant to have incremental IDs to make each distinct for actions applied per row, but if an onClick > refresh this section was applied the DOM that was given after the refresh was no longer distinct and the triggering of CSS styling was affected. This was a problem in repeating layouts where the field control's ID was not incremental but was only pointing to the property name. This has been resolved with unique generation of input IDs and labels for attributes.

SR-128720 · Issue 193408

Fixed CSS styling for buttons in repeating layouts with refresh

Resolved in Pega Version 7.1.8

Buttons in repeating layout are meant to have incremental IDs to make each distinct for actions applied per row, but if an onClick > refresh this section was applied the DOM that was given after the refresh was no longer distinct and the triggering of CSS styling was affected. This was a problem in repeating layouts where the field control's ID was not incremental but was only pointing to the property name. This has been resolved with unique generation of input IDs and labels for attributes.

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