INC-160767 · Issue 628373
Email headers correctly mapped when using MSGraph
Resolved in Pega Version 8.6
The value of "Send Date" was not correctly populated when using MSGraph instead of IMAP, causing the Email Listener to fail. Microsoft populates the "sendDateTime" field in the JSON with the value of the RFC 822 email header "Date:", but this value was not being passed to Java object of type "Message" as part of the query. To resolve this, ReceivedDateTime and SentDatetime have been added in the select filter of getMessagebymessageID.
INC-138243 · Issue 584898
Performance improvement in When parsing
Resolved in Pega Version 8.6
After upgrade, performance issues were seen in the execution of rules with When conditions. This has been resolved by modifying the code to address some inefficiencies in the parsing method.
INC-137882 · Issue 599137
Hazelcast will be used to determine node presence
Resolved in Pega Version 8.6
When calling logoff from the end user portal, sporadic PresenceStandardLifeCycleListener exceptions were seen during high load periods. This was traced to changes made in the Service Discovery behavior: when there is an issue with the node and heartbeats are missed, the node goes to Safe Mode. This caused the topology to change and trigger clearing off presence sessions, but the node still received service requests and this issue was seen. To resolve this, an updated has been made so the system will rely on the Hazelcast listener instead of service discovery to determine whether a node has left.
INC-189259 · Issue 692033
Big Decimal used while converting List to Page
Resolved in Pega Version 8.5.6
Previous work done to handle precision numbers in the JSON response that were being rounded or truncated when parsed for the DataSource page has been updated to also handle the case of mapping a list to a page.
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-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-191779 · Issue 677519
Updated use of declarative processing during performance testing
Resolved in Pega Version 8.5.6
After update, the performance test script build was not working. A stack overflow indicated an issue with the load activity for the D_InteractionHistory data page referenced by expressions/properties. This has been resolved by disabling declarative processing during the estimation of data size.
INC-199749 · Issue 695536
Updated use of declarative processing during performance testing
Resolved in Pega Version 8.5.6
After update, the performance test script build was not working. A stack overflow indicated an issue with the load activity for the D_InteractionHistory data page referenced by expressions/properties. This has been resolved by disabling declarative processing during the estimation of data size.
INC-129400 · Issue 567403
Data page form displaying activity parameters from 'when' rules
Resolved in Pega Version 8.4.2
While displaying the parameters list for source activity in data page rule form, an icon was displayed. This was traced to the visibility condition being an expression but mentioned as a 'when' rule, causing the parameter dialog to not load. This has been resolved by updating the pzActivityParamList activity to change the visibility condition as expression from a 'when' rule.
INC-138840 · Issue 599259
Data-Summary reports default will not use the rule resolved setting
Resolved in Pega Version 8.6
An intermittent issue was seen where a query could become stuck for ~2 hours in the database. This has been resolved by setting the default for Data-Summary reports to not use the rule resolved setting.