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-182969 · Issue 677284

Updated AgentName handling for QueueItemID

Resolved in Pega Version 8.5.6

A report was showing as scheduled but no mail was received when it was supposed to run. Investigation showed this was due to the reports being corrupted, leading to the flow skipping the necessary Queue-For-Agent method. While there was a workaround of doing a "Save As" to create a new version of the report, this has been addressed by setting the agentName before saving to the database to handle missing agentName cases and ensure pyAgentname is always populated when pzQueueItemID is not empty.

INC-184790 · Issue 666123

Details added to pxLogMessage History tab

Resolved in Pega Version 8.5.6

Usage and Description details have been added to the History tab for the pxLogMessage Rule-Utility-Function, as below: Description: Logs message for the logger Rule_Utility_Function.pxLogErrorMessage.Default with specified level. Used for error handling in response data transform in a data page. Parameters : sMessage - Specify the log message cLevel - Specify character to indicate log level, as below 'd' to DEBUG 'i' to INFO 'f' to forced INFO 'w' to WARN 'e' to ERROR This will return true or false depending on whether it logged or not.

INC-185758 · Issue 678454

Resolved database contention during high-performance case creation

Resolved in Pega Version 8.5.6

During extreme load on the application, updating the latest pyLastReservedID column of 1 row in the data.pc_data_uniqueid table for a particular case type could cause database contention. This was a missed use case for recent ID generation optimization, and has been resolved by amending the MERGE statement to resolve an SQL exception sometimes seen on on Oracle and SQLServer.

INC-185760 · Issue 668740

SQL queries modified to use qualified table references

Resolved in Pega Version 8.5.6

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-186634 · Issue 672149

Expanded debug logging for requestors

Resolved in Pega Version 8.5.6

In order to assist with diagnosing issues, debug loggers have been added for requestor activation and validation.

INC-187553 · Issue 675428

Service Email handling updated for MSGraph "From" address

Resolved in Pega Version 8.5.6

While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.

INC-187708 · Issue 680011

Handling added to StreamChangeTracker for non-String mode

Resolved in Pega Version 8.5.6

Incorrect StreamChangeTracker mode properties were being tracked for value changes. Investigation showed this was due to the StreamChangeTracker.trackValueChanges API tracking value changes on properties of mode page and page list, which resulted in logging a WrongModeException in the logs. This has been resolved by updating the behavior of the StreamChangeTracker.trackValueChanges API to return false when value change tracking is invoked for a property other than mode String.

INC-187750 · Issue 675634

Error message removed for adding a new datatype to a branch

Resolved in Pega Version 8.5.6

Clicking 'add data type' for an application when no unlocked rulesets were available resulted in the error message "No unlocked Rulesets/Versions found that are valid for this record. Unlock at least one Ruleset/Version that can contain records of this type.". However, it was possible to create a data type by choosing branch. Investigation showed this message was added by the activity pzLoadTypeToBeAdded and is not needed: it has been removed from the step that appended the message when validating on click of submit.

INC-188080 · Issue 673782

Service Email handling updated for MSGraph "From" address

Resolved in Pega Version 8.5.6

While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.

INC-188143 · Issue 674971

Service Email handling updated for MSGraph "From" address

Resolved in Pega Version 8.5.6

While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.

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