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-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-128433 · Issue 194694

Added template to handle certificate needed by Word MacroManager

Resolved in Pega Version 7.1.8

Because the Word macrocode must be signed with a current certificate, a Signed and timestamped template has been added.

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

SR-129101 · Issue 195933

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