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.
INC-187708 · Issue 680013
Handling added to StreamChangeTracker for non-String mode
Resolved in Pega Version 8.6.3
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 675636
Error message removed for adding a new datatype to a branch
Resolved in Pega Version 8.6.3
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-187857 · Issue 697096
Added debug logging and exception recovery for unexpected data object
Resolved in Pega Version 8.6.3
When rules were complied in lower environment and deployed into production, they later became corrupted and system behavior changed. The error "Java generation failed: caught exception while expanding property pyGetCasePredictionsByClassName on page CurrentRecord" was generated. Investigation showed the auto-populate property pyGetCasePredictionsByClassName was attempting to get the metadata property "pzDataObjectParams": this was a string value in this scenario instead of the expected java object, and caused the exception. To resolve this, a debugger has been added which will check if the property is a java object or not. If it is not, the system will skip the processing and then display an error message with a stack trace.