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-B2905 · Issue 273518

Obj-Save of large numbers of classes with CLOB properties

Resolved in Pega Version 7.2.2

Clob code for Oracle has been optimized to support Clobs > 4K in size

SR-A98978 · Issue 266552

Property references work on parameterized data pages

Resolved in Pega Version 7.2.2

Doing a property reference between data pages from a parameterized source page to target page loaded both pages, but also created a 'phantom' D_SourcePage[] loaded on the clipboard. This was traced to having the Property-Ref of a property in the data page refer to another data page property using the syntax D_SourcePage[test].pyNote. When such a syntax is written, instead of the parametrized overloaded method, the unparameterized version of the method is called. Later display of the data page XML only acted on the source page name since keys weren't set during setAsReference, effectively doing a findPage without a parameter. To correct this, the reference will use the data page source while doing setAsReference to ensure that the keys are available while trying to display the data page XML and thereby load the data page with the correct parameters.

SR-A15627 · Issue 230719

JBoss shutdown errors resolved

Resolved in Pega Version 7.2.2

During a controlled shutdown, database-level exceptions occurred and a hard reset was required. This was traced to the container not correctly detecting dependecies, leading to JBoss prematurely terminating JMS and JDBC resources that were needed during Pega shutdown. Pega applications on JBoss now contain information to ensure the application server understands that this resource has dependent processes and the lookup-name (with the JBoss specific namespace) is maintained correctly to make sure it isn't cleaned up prematurely. The web.xml file has also been updated to include a lookup-name in the entry for ResourceRef_1 to handle cases where the datasources are injected using CLI scripts after JBoss is started and before Pega is deployed.

SR-A88329 · Issue 258343

JBoss shutdown errors resolved

Resolved in Pega Version 7.2.2

During a controlled shutdown, database-level exceptions occurred and a hard reset was required. This was traced to the container not correctly detecting dependencies, leading to JBoss prematurely terminating JMS and JDBC resources that were needed during Pega shutdown. Pega applications on JBoss now contain information to ensure the application server understands that this resource has dependent processes and the lookup-name (with the JBoss specific namespace) is maintained correctly to make sure it isn't cleaned up prematurely. The web.xml file has also been updated to include a lookup-name in the entry for ResourceRef_1 to handle cases where the datasources are injected using CLI scripts after JBoss is started and before Pega is deployed.

SR-A98390 · Issue 264755

Scheduled report cleanup error resolved

Resolved in Pega Version 7.2.2

Exceptions were thrown in the logs by the scheduled reports task when trying to clean up the previous day's generated attachment reports. This was due to the name exceeding the length restriction on the property (60 characters) and failing validation, and has been fixed by truncating the field.

SR-A93149 · Issue 263069

Resolved excessive rollbacks with batch mode disabled

Resolved in Pega Version 7.2.2

Excessive rollbacks were seen when batch mode was disabled. To correct this, the rollback statement in BatchProcessor.close() will be conditionally executed based on the value of currentBatchCount (on successful commit, batchCount is set to zero).

SR-A71561 · Issue 262640

Resolved corrupted transactionID caused by empty AJAX call

Resolved in Pega Version 7.2.2

Executing an activity in an AJAX call which returns no content can corrupt the Engine opinion of the proper pzTransactionID. Given two tabs, one on thread A and one on Thread B, where each thread has its own pzTransactionID, switching tabs from thread A to thread B and immediately firing the activity (via an AJAX call, e.g., reloadSection), caused thread B to become corrupted and believe that the pzTransactionID from thread A is the proper pzTransactionID for thread B. This was seen as a transactionID mismatch in logs and a failed request. To fix this issue, changes have been made to check for both null and empty framedata before resetting the transactionID on a thread.

SR-A92074 · Issue 264473

All child classes reported in BIX extraction

Resolved in Pega Version 7.2.2

If a BIX extract was configured on a class with no instances but there were child classes with eligible instances for extraction, not all all the instances of child classes were extracted. This has been fixed with a null check that will handle cases where the property is an orphan.

SR-A43557 · Issue 266493

HttpAPI processing order updated

Resolved in Pega Version 7.2.2

If a repeat grid source was configured using a property that referred to a read-only parameterized thread-level data page, clicking on a link in a row repeat intended to open a URL in a window resulted in an Unauthenticated or not available error. This was traced to the refresh and process order contained in the HttpAPI, and this has been changed to refresh the primary page after authentication and before processing data.

SR-A93675 · Issue 266549

HttpAPI processing order updated

Resolved in Pega Version 7.2.2

If a repeat grid source was configured using a property that referred to a read-only parameterized thread-level data page, clicking on a link in a row repeat intended to open a URL in a window resulted in an Unauthenticated or not available error. This was traced to the refresh and process order contained in the HttpAPI, and this has been changed to refresh the primary page after authentication and before processing data.

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