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-C11017 · Issue 353403

Test Connectivity enhancement checks database availability

Resolved in Pega Version 8.1

An enhancement has been added to the Test Connectivity button on the Extract ruleform to test the ability to connect to the database.

SR-C11027 · Issue 353987

Check added to fix class not found exceptions

Resolved in Pega Version 8.1

A "Class does not exist" exception was appearing while invoking pzGetCaseDetails via REST client due to empty SLA flow pages being created by the API. A check has been added to correct this.

SR-C11041 · Issue 352810

UI retains layout when RTE maximized for editing

Resolved in Pega Version 8.1

After using the 'Maximize' button in a Rich text editor in a section, the screen layout was incorrect after visiting another window and toggling back to the one with the RTE. This was a timing conflict: when the RTE is maximized CSS styles are captured and removed from the Harness, and whenever refresh section fires onChange, RTE is destroyed and recreated. To make sure the UI does not get distorted, pzpega_ui_richtexteditor.js has been modified to resize the RTE before destroy and to set the CSS styles back to the harness.

SR-C11138 · Issue 357104

Removed stray attribute causing Accessibility error

Resolved in Pega Version 8.1

While validating the Case Manager portal, a critical error thrown by the Accessibility validator was traced to the attribute 'aria-selected' being set to false for Tabs. This was misplaced code applied to an element that did not need it, and has been removed.

SR-C11146 · Issue 355013

Corrected thread contention performance issues for requestor create/retrieve

Resolved in Pega Version 8.1

A thread contention on Requestor retrieval was traced to a global level lock in PRNodeImpl.class, and the global lock has been replaced with a ReentrantReadWriteLock.

SR-C11148 · Issue 354987

Performance improvement for AccessInfoConclusion evaluation

Resolved in Pega Version 8.1

In order to improve performance during an AccessInfoConclusion evaluation, data will be stored in a ConcurrentHashMap instead of a Hashtable.

SR-C11149 · Issue 355078

Added prconfig setting to adjust sync policy for LAC

Resolved in Pega Version 8.1

Some contention on the monitor lock for the LocalizedApplicationContext was seen on sites with with thousands of concurrent users logging in and out. To improve performance, a prconfig setting has been added to LAC - registerUse() & deregisteruse(). to allow use of a looser synchronization policy.

SR-C11241 · Issue 355607

Support added for secured Connectors to use "Keystore location"

Resolved in Pega Version 8.1

Support was recently added for "External keystores" on the Keystore ruleform, seen in the new "Keystore location" drop-down at the top of the form, but Connectors were not able to use the new Keystore types (File reference and data page) for HTTPS connections. This ability has now been added by modifying SSLUtils.java and KeyStoreUtilsImpl.java to support the file reference keystore.

SR-C11241 · Issue 360907

Support added for secured Connectors to use "Keystore location"

Resolved in Pega Version 8.1

Support was recently added for "External keystores" on the Keystore ruleform, seen in the new "Keystore location" drop-down at the top of the form, but Connectors were not able to use the new Keystore types (File reference and data page) for HTTPS connections. This ability has now been added by modifying SSLUtils.java and KeyStoreUtilsImpl.java to support the file reference keystore.

SR-C11319 · Issue 352584

Mobile dropdowns accept data binding from all sources

Resolved in Pega Version 8.1

When entering reports on Mobile, dropdowns were being reset after filling in autocompletes and other dropdowns. This was traced to data binding not being supported for sources other than Associated, and changes have been made to the generateDropdown RUF to support data binding for all sources of dropdown to correct this.

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