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-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.

SR-128823 · Issue 193672

Added localization for CategoryActions navigation rule

Resolved in Pega Version 7.1.8

The CategoryActions navigation rule has been made available for localization.

SR-128861 · Issue 195852

Corrected temp directory for upgrade file extraction

Resolved in Pega Version 7.1.8

On upgrade, the extractedfiles directory was being written to the java.io.tmpdir location instead of to the Web-tier temporary path, i.e.. the temp location of the application server. This was incorrect, and the web temp directory is now set as the default temp directory in PRPC.

SR-128883 · Issue 195834

Fixed button contrast when using accessibility

Resolved in Pega Version 7.1.8

The "Select Values" button in the dialog to edit report filter had a low contrast ratio when accessibility was enabled. This was caused by the unintentional application of the repeat layout CSS to the button, and has been fixed.

SR-128895 · Issue 193902

LDAP authentication password issue resolved

Resolved in Pega Version 7.1.8

After reopening and saving an Authentication Service rule, the Test Connectivity failed due to a credentials problem. This was due to the password field being modified (increased) on a refresh/reopen of the record. This issue was caused by a double-encryption flaw on refresh, and has been corrected.

SR-128932 · Issue 194789

Added support for -x and -y parameters to ApplicationBundle import

Resolved in Pega Version 7.1.8

Previously, the use of the -x and -y parameters in the command line utility prpcUtils only worked with PegaArchives and not ApplicationBundle archives. In order to facilitate automation, the app bundle command line import command now honors the -x (override) and -y (skip) import parameters, and these options will be passed along to any nested par files.

SR-128945 · Issue 197784

Ensured compliance for localization checkbox on RadioButtons control label

Resolved in Pega Version 7.1.8

In RadioButtons control, it was seen that a label was localized without regard to the status of the localization checkbox checked at the section level. This has been fixed.

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