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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-128380 · Issue 194162

Refined Excel specifications import

Resolved in Pega Version 7.1.8

Importing specifications from Excel was registering unexpected characters. This was caused by the system mistakenly importing rPh tags from the "sharedStrings.xml" in the "xl" folder, and has been corrected.

SR-128397 · Issue 193116

reRunReport modified to use fully qualified RUF from Procomm ruleset

Resolved in Pega Version 7.1.8

In some cases, re-running a report would fail due to an inability to pick the correct instance of the Rule-Utility-Function getPropertyValue from two rulesets with the same parameters (in the KYC ruleset and the Procomm ruleset). This has been resolved by modifying the reRunreport activity to use the fully qualified RUF from the PegaProcom ruleset.

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

SR-129101 · Issue 195816

Smoothed error handling for operator password change process

Resolved in Pega Version 7.1.8

After the password change error screen appeared, the error popup showed again after dismissal and the the operator-id edit screen had to be closed and reopened, requiring entering the operator information again in order to proceed. This was due to incomplete clearing of the errors, and has been corrected.

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