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.

INC-217855 · Issue 731911

Uncommitted hotfix able to Rollback All after install

Resolved in Pega Version 8.8

A security hotfix was installed through Hotfix manager and left as uncommitted. When new hotfixes for the same files were received, the process required the uncommitted hotfixes to be rolled back, but attempting to do so generated exceptions in the logs reading "Exception in rolling back the archive PegaRULES Process Commander: code: 0 SQLState: Message: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PRPC_RULE_ADM_P7.PR_ENGINECLASSES_PK) violated". The issue was caused by the Date field only accepting dd/mm/yyyy HH:MI:SS, so attempting to insert two records of the same jar in the pr_engineclass generated this error from pr_data_restore in Oracle. To resolve this, an update has been made to insert rolled-back jar removals with their original patch date to avoid PK conflicts.

INC-222835 · Issue 721065

UI messages updated for hotfix catalog issues

Resolved in Pega Version 8.8

Here is the issue/enhancement request that was seen and can be a more general issue. After the restart there is not a catalog available and for environments that cannot access the internet this means they cannot actually do anything like commit all or rollback all. When clients tried this they clicked on the button and nothing happened. If you look in the PegaRules log you see a message that tells you that the catalog is not available.

INC-223074 · Issue 720454

Fallback handling improved for import synchronization

Resolved in Pega Version 8.8

Upgrade to CRM 8.7 was failing during the import of the CRM jar. There are some rare edge cases where instances may be in the database, but not visible to the engine until the import is already underway, such as when rollback has deleted a class definition and mapping but not the instances of the class itself. To mitigate the risk of PK constraint violations when this happens, the process has been modified to mark all the instances that cannot be directly synchronized as updates so that the data layer will upsert them.

INC-229641 · Issue 739454

Enhanced logging related to rule skimming

Resolved in Pega Version 8.8

In order to assist with diagnosing issues related to skimming of a ruleset, an update has been made which will log the complete stack trace along with the pzinskey being processed in debug mode.

INC-RCA-921 · Issue 713987

Updated debug logging

Resolved in Pega Version 8.8

Debug logging within IndexReferenceSynchronizer and FastLoader has been updated. With this update, IndexReferenceSynchronizer debug logging will indicate what the action is for each instance, FastLoader will include information about the keys being loaded and statements being executed, and duplicate logging has been removed from BatchSQLExecutors.

INC-183485 · Issue 699787

ClientCache performance optimization

Resolved in Pega Version 8.8

In order to improve performance for the mobile app, updates have been made to optimize the ClientCache list interations.

INC-190053 · Issue 680232

Mobile attachment count corrected

Resolved in Pega Version 8.8

Parametrized data pages were not being populated as expected, causing an incorrect attachment count when opening a case in Mobile. This has been corrected.

INC-192649 · Issue 706132

Basereference context available for attach content control

Resolved in Pega Version 8.8

An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.

INC-198193 · Issue 723626

Error correctly shows for each attempt to upload an oversize file

Resolved in Pega Version 8.8

The error message indicating an uploaded file exceeded the permitted file size was only shown on the first try on Android. Subsequent attempts to upload the same oversize file did not generate any error. This was due to a persisting value, and has been resolved by explicitly clearing the input value for the mobile browser upload.

INC-198249 · Issue 705091

Security updates for packaging mobile app

Resolved in Pega Version 8.8

Unsafe properties such as password and userId are now explicitly filtered from the Operator object during the mobile app packaging process.

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