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-C10766 · Issue 359295

Added check to pxUpdateDateTime to compensate for DST/UTC timestamp inconsistencies

Resolved in Pega Version 8.1

Existing customer data created during the DST transition hour in November had an incorrect pxUpdateDateTime, causing Obj-Refresh-and-Lock to disregard local changes and always pull from the database when saving a work object. This was traced to an inconsistency in how timestamp data for pxUpdateDateTime is saved; the value in the database column reflects UTC, while the value in the BLOB reflects the user's system time. This presents an inconsistency during DST as the system time will just move back 1 hour at 2 AM on DST, while UTC will continue on. Objects created during this single hour are out of sync by 1 hour, thus failing a check within Opener.isTimestampDeltaInTolerance(), which is called by OpenIfStale(), used within Obj-Refresh-and-Lock. To resolve this, if the pxUpdateDateTime is exactly one hour off when comparing the column and clipboard on an Open, the system will now ignore the optimization, re-open from the database, and compare again.

SR-C10790 · Issue 351446

Help documents updated for DB2/zOS tablespace and aux tables DDL

Resolved in Pega Version 8.1

n Pega 7.3.1, the ability to explicitly generate create tablespace and aux tables DDL for a DB2/zOS database was added to the import wizard. For a Database-Admin-DB-Name rule for a DB2/zOS database there are dynamic system settings needed. For the PegaRULES and PegaDATA databases these DSS are setup as part of an installation/upgrade. To use this feature for other D-A-DB-Name rules the database configuration properties need to be set up with in Pega using prpcUtils. The help documents have now been updated with this information.

SR-C10853 · Issue 353638

System status in Extractimpl corrected for BIX extraction failures

Resolved in Pega Version 8.1

When a BIX Extraction failed during parsing command line params the JVM went through normal shutdown while the expectation was to have an abrupt shutdown. This was traced to the System exit status not properly setting the error level var in Extractimpl to true, and has been corrected.

SR-C10925 · Issue 352602

Set source list for Repeating Dynamic Layout works for Microsoft Internet Explorer

Resolved in Pega Version 8.1

When using Microsoft Internet Explorer , setting the source as property using PageList or Page Group / Datapage for Repeating Dynamic Layout and submitting the property dialog resulted in "Source is UNSPECIFMicrosoft Internet Explorer D" errors. This was caused by an error in the pzpega_ud_section file, and has been fixed.

SR-C11008 · Issue 353589

Documentation added for Work Group "Authorized Managers" field

Resolved in Pega Version 8.1

As of v7.3.1, the Work Group configuration has a new field "Authorized Managers" which takes a list of manager IDs who can also see the work of that team. This is the field previously given as "Contacts". The documentation has now been updated to reflect these changes and to clarify that work group = team. Legacy style tables have also been converted into task topics.

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.

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