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-C10445 · Issue 354093

Added Null Pointer Exception check to avoid Sync fail

Resolved in Pega Version 8.1

A null pointer check has been added to pzPackagingExceptionCatcher to handle exceptions.

SR-C10476 · Issue 354997

Corrected display of drilldown report popup

Resolved in Pega Version 8.1

Launching a report in a pop-up and drilling down sometimes caused the entire portal to be displayed instead of the single document. At other times the report appeared with a header and left side panel, which was not the expected behavior. This has been fixed.

SR-C10482 · Issue 355568

64

Resolved in Pega Version 8.1

Offline localization has been added to the Local Action modal dialog description.

SR-C10528 · Issue 355028

Enhanced engine startup exception logging

Resolved in Pega Version 8.1

In order to better diagnose engine startup failures, the logger has been modified to print the class name for which the exception was generated.

SR-C10543 · Issue 352808

Parameter value setting for read-only field label fixed

Resolved in Pega Version 8.1

A text field label value provided as a parameter (say Param.pyNextLabel) was not working for read-only sections. This was due to a missing case for param labels to render the param value properly, and has been fixed.

SR-C10550 · Issue 352390

GRS value added to authprofile in Connect CMIS

Resolved in Pega Version 8.1

Given a Connect CMIS with GRS syntax for Authentication profile, the code was not in place to get the configured GRS value for the authprofile, resulting in the runtime scenario failing while placing the file into CMIS repository. To correct this, code has been added to add that value to the Connector pyAuthenticationProfile property.

SR-C10617 · Issue 362409

Removed double-encoding for datatypes created in Japanese

Resolved in Pega Version 8.1

The data page and data page list were displaying junk values when the datatype was created in Japanese. This was traced to the classname being double-encoded, and has been corrected.

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.

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