INC-173434 · Issue 672675
Pushservlet cookie path updated to resolve error
Resolved in Pega Version 8.6.3
A very large number of exceptions were being logged indicating "Unhandled error in web.request.internal.URLComponentProcessorImpl.populateCSRFToken", impacting the ability to perform log analysis. This exception has been resolved by updating the pushservlet cookie path.
INC-176138 · Issue 668938
Decision table query performance improvements
Resolved in Pega Version 8.6.3
Work done previously to improve performance by preventing the decision rule from being treated as a custom rule has been further augmented by preventing the standard Declarative Rules from being treated as Custom Rules while building the Declarative Cache.
INC-183728 · Issue 665132
Oracle handling updated for primary key in upgrade DDL
Resolved in Pega Version 8.6.3
Previously, when a primary key of a table was created Oracle would automatically create a unique index with the same name as the primary key. However, with the introduction of Oracle 19, an optimization was added which will not do that if there is another unique index on the table which contains the column(s) of the primary key. This difference can cause updates to fail with the error "cannot drop index used for enforcement of unique/primary key". This has been resolved by updating the handling for primary key constraint and the corresponding index name.
INC-185614 · Issue 684848
Resolved access errors for external database class mapping generation
Resolved in Pega Version 8.6.3
After update, opening the Database Class Mappings landing page displayed all database tables linked to customer data schema as an exclamation mark with the error tooltip : "width = device-width". In addition, the error "Class: com.pega.pegarules.pub.PRRuntimeException Message: Error: You lack access required to execute Pega-Landing-DataModel-DBClassMappings.pzLPCheckDBMapRowCount" was logged. The application behaved normally despite the exceptions. This was traced to the the warning tool tip not loading correctly for the Exposed/Mapped column in Configure-Data Model->Class and properties->Database class mappings->select class category(Data)->for CustomerData, and has been resolved by updating the security settings to re-allow invocation from browser, require authentication, and set the correct privileges.
INC-185758 · Issue 678456
Resolved database contention during high-performance case creation
Resolved in Pega Version 8.6.3
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-185943 · Issue 679139
1000 character limit on prconfig DSS setting removed
Resolved in Pega Version 8.6.3
Previously, a limit imposed in the Data-Admin-System-Settings.ValidateKeyContent activity limited any prconfig setting to a value of 1000. As there are settings such as prconfig/alerts/parameterpage/allowedKeywords/default that could exceed the 1000 character limit, this limit has been removed.
INC-186094 · Issue 683694
MQ jar handling updated to resolve initialization error
Resolved in Pega Version 8.6.3
After update, errors were seen indicating a NoClassDefFoundError relating to initializing com.ibm.mq.jms.MQQueue. This was traced to a difference in the handling of imported MQ jars, and has been resolved.
INC-186616 · Issue 669062
Cleanup added for disabled/deleted operator passivation data
Resolved in Pega Version 8.6.3
In some scenarios, a passivated session for a non-active operator was able to be resumed after cluster restart. This has been resolved by adding a check for disabled or deleted operators which will then delete any lingering passivated data.
INC-186634 · Issue 672150
Expanded debug logging for requestors
Resolved in Pega Version 8.6.3
In order to assist with diagnosing issues, debug loggers have been added for requestor activation and validation.
INC-187553 · Issue 675430
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.6.3
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.