INC-182082 · Issue 694613
API added to handle digital signing from proxy layer
Resolved in Pega Version 8.5.6
When an email account was configured with a valid email account and keystore for message signing, it was possible to send emails with valid digital signatures. When the same email was used in case type email instantiation, no digital signatures were included in it. This was due to keyStoreInstance properties being read from the email account top level page when they need to be retrieved from pyEmbedSenderProtocol page when using SMTP. This has been resolved by adding an API to handle the signing logic from the JavaEmailClientProxy class.
INC-182148 · Issue 668007
Handling added for missing schema for persistClusterState
Resolved in Pega Version 8.5.6
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 667590
French added to Locale List Separator
Resolved in Pega Version 8.5.6
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 667097
License Usage logging expanded
Resolved in Pega Version 8.5.6
Diagnostic loggers have been added to assist in debugging license usage.
INC-182959 · Issue 668735
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-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.