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-B66297 · Issue 299892

Instance insertion fixed for PostgreSQL partitioning

Resolved in Pega Version 7.3.1

Obj-Save was failing when trying to insert an instance in a partitioned PostgreSQL table with 'only if new' enabled. This record insertion failed because of a system check that is present when inserting an instance into the child table, and the issue has been resolved by reworking the code that was checking (assuming) if the insert was successful based on the returned inserted count.

SR-B51825 · Issue 310042

Added handling for WO lock when OAuth2 token expires

Resolved in Pega Version 7.3.1

The expiration of the OAuth2 token committed the WOs in context and caused all WOs to lose their locks and eventually end up in the SLA broken queue. To fix this, code has been added to perform the commit on a new database thread so the commit operation will be independent from the actual thread context.

SR-B49520 · Issue 310724

Schema extraction over multiple DBs uses log table instead of class

Resolved in Pega Version 7.3.1

When running an extract, an Null Pointer Exception error was generated if the data being extracted was on a different schema / database than the Pega data schema. This has been resolved by reworking the sequence number generator to use a pr_log table connection of instead of using the class on which the extract was defined.

SR-B56540 · Issue 311961

Schema extraction over multiple DBs uses log table instead of class

Resolved in Pega Version 7.3.1

When running an extract, an Null Pointer Exception error was generated if the data being extracted was on a different schema / database than the Pega data schema. This has been resolved by reworking the sequence number generator to use a pr_log table connection of instead of using the class on which the extract was defined.

SR-B69447 · Issue 317927

Attachment links with commas open in Google Chrome

Resolved in Pega Version 7.3.1

After upgrade, attachment links containing commas were not opening as expected in Google Chrome. A check has been added to ensure attachments open properly.

SR-B69447 · Issue 317951

Attachment links with commas open in Google Chrome

Resolved in Pega Version 7.3.1

After upgrade, attachment links containing commas were not opening as expected in Google Chrome. A check has been added to ensure attachments open properly.

SR-B39427 · Issue 309252

Export to Excel fixed for DT >50 records

Resolved in Pega Version 7.3.1

After upgrade, clicking the Export button on a decision table with more than 50 records was not sending the data to Excel as expected. This was traced to a Null Pointer Exception generated by encountering an unneeded step page, and the erroneous step has been removed.

SR-B53476 · Issue 313103

JBoss installation config documentation corrected

Resolved in Pega Version 7.3.1

Deploying JBoss in single-user configuration and starting Pega was failing with the error "Services with missing/unavailable dependencies". This was caused by an incorrect configuration, and was traced to an error in the documentation for JBoss that reverted the installation instructions to an earlier version. The JBoss documentation has been corrected to reflect that configuring the adminPegaRULES datasource is not optional. If dual user config is not needed, the same configuration as PegaRULES datasource should be used.

SR-B54273 · Issue 310624

Resolved requestor hang and JVM crash

Resolved in Pega Version 7.3.1

Some application nodes were hanging or intermittently going down one by one after operators became stuck in the building session authorization stage. This was traced to an infinite loop situation in AuthorizationContextmanagerImpl combined with excessive firings of the operations in ContextUtils that expand the Rule App clipboard page and remove unwanted properties. This has been resolved with code improvements that include ensuring the 'while' loop will cycle a maximum of 10 times before exiting.

SR-B54273 · Issue 310713

Resolved requestor hang and JVM crash

Resolved in Pega Version 7.3.1

Some application nodes were hanging or intermittently going down one by one after operators became stuck in the building session authorization stage. This was traced to an infinite loop situation in AuthorizationContextmanagerImpl combined with excessive firings of the operations in ContextUtils that expand the Rule App clipboard page and remove unwanted properties. This has been resolved with code improvements that include ensuring the 'while' loop will cycle a maximum of 10 times before exiting.

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