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-162198 · Issue 628703
Tracelist cleared to address parser exception in REST Service
Resolved in Pega Version 8.6
In a requestor pool of mixed types, HTTP and REST, the alert data was not initialized properly if there was a parse exception due to invalid data in the incoming payload. For example, last_input, first_activity, and last_step could all be left over from the prior HTTP service request. This was caused by the system pulling in seemingly unrelated activities for the "Last activity called" in the stack trace of a service when a single alert was created by two different service types which were sharing the same package, and has been resolved by explicitly clearing the tracelist for the service to prevent inaccurate information being reported in the logs.
INC-162217 · Issue 635889
Default sorting with Pagination, Data Page and Report Definition corrected
Resolved in Pega Version 8.6
After configuring a section with the table sourced from a data page and personalizing the table with the pagination and sort-by features available in a report definition, the table content sourced with the data page was not sorting the data. This has been resolved by updating the pxRetrieveReportDefinition activity so that the sort order for queryable data pages will not be reset for a first-time request.
INC-163295 · Issue 631472
Cookie filtering logic updated to better handle upgraded environments
Resolved in Pega Version 8.6
After upgrade from Pega 8.3 to Pega 8.5, login issues were seen if cookie/HttpOnly was set to 'true' and the cookie was sent as part of headers based on the prconfig setting. This was due to handling changes, and has been resolved by updating the cookie filter logic.
INC-163791 · Issue 633298
JobScheduler time zone display expanded
Resolved in Pega Version 8.6
The Time zone control on the JobScheduler rule form displayed only the first few characters for the time zone. This was due to a hard-coded CSS setting for the width, and has been resolved.
INC-163863 · Issue 632427
Monthly agents run correctly on non-English locales
Resolved in Pega Version 8.6
Nodes with non-English locales were not starting when using an Agent with a monthly execution pattern. This was due to incorrect handling of the user locale, and has been resolved.
INC-163898 · Issue 635397
DASS added to configure Property Query inclusion in ADM flows
Resolved in Pega Version 8.6
After upgrade, ADM flows were failing to compile if the model had more than 300 predictors. Investigation showed that the generated code of the rule included both the Property Query as well as scaler reference, causing the generated code to exceed the maximum size. This was due to a change instituted to support the move from scaler references to Property Queries for performance reasons, and has been resolved by adding a DASS configuration which can be adjusted to disable the Property Query inclusion. By default the value of this DASS is false.
INC-163985 · Issue 635145
Class mapped to CustomerData is incrementally indexed as expected
Resolved in Pega Version 8.6
When using a class which mapped to customerdata, instances that were added/updated were not automatically getting indexed unless a full reindex was performed. If the class mapping was changed from customerdata to pegadata then the incremental indexing was done. To resolve this, the UpdateProcessor class that resolves CustomerData to the correct database name has been updated to use PegaData. ConfigurationMapImpl contains the resolution mapping and a call is made to ConfigurationMapImpl to retrieve the correct database name.
INC-164472 · Issue 635113
Performance improvements for archiving and purging
Resolved in Pega Version 8.6
Archiving and purging jobs were not working in Prod. Investigation showed this was caused by the system timing out. To resolve this, improvements have been made to purging by batching the deletions and refactoring the Where condition to simplify the complex expression queries that determine the cases to be archived.
INC-164514 · Issue 635085
Unnecessary logging removed from startup
Resolved in Pega Version 8.6
The error "SettingMisusageFailure: Database is null" was repeatedly being logged following an update that consolidated error-handling logic for using a third-party custom jar file during the compiling process. This was an unnecessary message for this scenario as the database is often null at the early stages of startup, and SystemSettingsImpl has been updated to skip logging this error.