INC-199608 · Issue 692584
Added pause after Library Extraction to ensure Rule-Utility-Functions are present
Resolved in Pega Version 8.6.3
After upgrade from Pega 7 to Pega 8, nodes were not starting and the error "pub.context.InitializationFailedError: PRNodeImpl init failed" appeared. This was traced to an issue with the pzSharedTenant rule: when pzSharedTenant (Rule Access When) is assembled by the system, it uses the compareTwoValues Rule-Utility-Function. If the system is not able to find the correct version of compareTwoValues, it adds an UnresolvedAssemblyError in the assembly of the pzSharedTenant, causing the startup failure. This has been resolved by adding an await call after the LibraryExtraction task to wait for it to complete. This wait will ensure that the library extraction task completes before starting the search task which uses Rule-Utility-Functions.
INC-199679 · Issue 688737
Handling added to email encoding for ISO-8859-8-i charset
Resolved in Pega Version 8.6.3
After update, cases were intermittently not getting created from inbound email and the process became stuck. This has been resolved by adding handling to replace the ISO-8859-8-i charset with ISO-8859-8 for encoding the mail content.
INC-200029 · Issue 690169
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-201502 · Issue 696086
Parser updated for value list
Resolved in Pega Version 8.6.3
When attempting to process a JSON list using a File Data set that had a list attribute, the clipboard looked correct while performing the browse operation on the data set, but executing the data flow that referenced this data set resulted in the error "Expecting PageList and got String List". If this was changed to a text property, the browse operation on Data set failed but the data flow worked without any issues. and the values were copied into the text properties.This has been resolved by changing the parser for value list.
INC-201648 · Issue 696965
Corrected duplicate record error message
Resolved in Pega Version 8.6.3
When inserting a duplicate record in a grid, the error was shown at the harness level instead of the record level. This was traced to the error messages being removed from the step page, and has been resolved by updating the system so messages will not be cleared if the same value is being set.
INC-201991 · Issue 692861
Explicit connectivity close added to Queue Manager error handling
Resolved in Pega Version 8.6.3
Performing a connectivity test on the MQ Connector page with an invalid queue name aborts the test connectivity but the MQ connection was not closing. This can become an issue when using IBM MQaaS (MQ as a service) where only a limited number of connections are allowed. This has been resolved by adding an explicit Queue Manager close in the error handling block.
INC-202510 · Issue 695890
SOAP connector supports OAuth2 profile
Resolved in Pega Version 8.6.3
Support has been added for using an OAuth2 profile as one of the allowed profiles for SOAP connector.
INC-202743 · Issue 697115
Cleanup added for disabled/deleted operator passivation data444
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-206240 · Issue 698248
Custom headers work in MS Graph
Resolved in Pega Version 8.6.3
Custom headers were not working for MS Graph. This was a missed use case for checking headeractualname to identify whether it is a custom header, and has been corrected.
INC-239902 · Issue 628577
Handling added for multi-file upload of duplicated files
Resolved in Pega Version 8.7
Attaching the same file multiple times during a single upload caused some of the duplicated files to not be included. The issue was not seen when attaching the same file multiple times but in different attempts. The exception "Can't continue with file attachment. FileData.xlsx is missing and might have been quarantined by anti-malware software" was logged. This was caused by the files being uploaded without updating filenames to have a unique ID, so multiple files with the same name were overwriting the previous file. This has been resolved by setting the appendUniqueIdToFileName parameter to true in the upload request so each copy of the filename is treated as an individual file.