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

SR-129159 · Issue 196998

Replaced missing OperatorID page for LDAP tab thread

Resolved in Pega Version 7.1.8

The OperatorID page in the clipboard was not visible in the tab thread when logged in through LDAP though it was visible in other threads or when not using LDAP. This was an error, and has been corrected.

SR-129276 · Issue 194879

Replaced missing help search button

Resolved in Pega Version 7.1.8

When launching the Pega help contextually, the button to get to the search field in the Pega help was missing. This has been replaced.

SR-129687 · Issue 195885

Updated locale clock handling for Java 7 and PAL

Resolved in Pega Version 7.1.8

Java 7 changed how locales are handled, and the two different NumberFormat classes within PRPC were sometimes leading to errors including blocking access to PAL. In particular, the way PAL set wall clock time was not compatible, and the system has been updated to parse it correctly with the new format.

SR-129690 · Issue 197180

BIX extracts made consistent independent of run method

Resolved in Pega Version 7.1.8

The property format outputted by BIX was different when BIX was run via the command line versus running it from an extract rule in the application's user interface UI. This was traced to running from the UI the batch requestor as unauthenticated and properties created in application rulesets not having property information: the XML page did not have pxObjClass set, hence the property info was null and formatting was ignored. To resolve this, the current requestor will be used (which is properly authorized), and If it is null, then a new app requestor will be created.

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