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.

INC-180184 · Issue 665090

Assistance and diagnostics added for issue with opening imported 'when'

Resolved in Pega Version 8.6.2

After update, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.

INC-180901 · Issue 666446

Heap dump ability added for OpenJDK

Resolved in Pega Version 8.6.2

Support for OpenJDK has been added to the heap dump generation process.

INC-181921 · Issue 666931

Date normalization enforced for reference time

Resolved in Pega Version 8.6.2

A job which was scheduled to run weekly once on Monday at 8AM CET was running a second time at 9AM CET. Investigation showed the original recurrence pattern implementation was normalizing the reference time only at construction; this has been resolved by forcing the date normalization on each reference time update.

INC-182148 · Issue 668008

Handling added for missing schema for persistClusterState

Resolved in Pega Version 8.6.2

The message "Error retrieving database indices java.lang.NullPointerException" was being logged repeatedly, indicating an issue with ClusterManagementAPI. Investigation showed there were missing default Schema values in the prconfig files, and this has been addressed by adding fallback scenarios for missing schema information during PersistClusterState.

INC-182537 · Issue 667591

French added to Locale List Separator

Resolved in Pega Version 8.6.2

Exporting data to Excel in CSV format resulted in text with French accent characters such as "Décision pour une nouvelle demande de règlement" to appear as random characters, and columns were not being split. This has been resolved by adding a record for the French locale in the pzGetLocaleListSeparator decision table rule.

INC-182828 · Issue 667098

License Usage logging expanded

Resolved in Pega Version 8.6.2

Diagnostic loggers have been added to assist in debugging license usage.

INC-182959 · Issue 668736

SQL queries modified to use qualified table references

Resolved in Pega Version 8.6.2

Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references.

INC-182984 · Issue 665938

Accessibility label added to delete column header of delegated data table

Resolved in Pega Version 8.6.2

After delegating a data table, the header row of the delete column added to the grid was empty and JAWS was reading "HEADER". This has been resolved by adding a label for the delete column which will also be displayed in the delegated rules in the case manager portal.

INC-184668 · Issue 665957

Check added for null mColumn values while estimating size

Resolved in Pega Version 8.6.2

A null pointer error indicating an issue with AbstractDataPageHandler.estimateDataSize was traced to missing handling for null values in mColumns while calculating size. This has been resolved with the addition of a null check.

INC-184699 · Issue 666462

Agent name validation added

Resolved in Pega Version 8.6.2

After creating an agent name that contained "/", the Agent API returned "Resource not found". This was due to the "/" character's incompatibility with the REST API, and has been resolved by adding agent name validation (pzvalidateagentname) to embed-rule-futurequeue to prevent the inclusion of "/" in an Agent name.

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