INC-194806 · Issue 680968
Performance improvement for message processing
Resolved in Pega Version 8.7
Severe performance degradation was seen for message processing in pdc-central after update. Investigation showed there was an issue with a write lock not not being acquired while reloading the datapage definition, causing concurrent dirty reads and multiple definition reloads. To resolve this, DeclarativePageDefinitionCacheImpl has been updated to acquire a write lock to prevent dirty reads of the same stale data page definition while reloading.
INC-196313 · Issue 688605
Added pause after Library Extraction to ensure Rule-Utility-Functions are present
Resolved in Pega Version 8.7
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-196604 · Issue 686005
New or updated operators properly updated on other nodes
Resolved in Pega Version 8.7
Newly imported or updated operators were not getting properly pulsed to other nodes. This was traced to operator pages being cached while the system pulse for 'Data-Admin-Operator-ID' was not permitted on the allow list, and has been resolved.
INC-197112 · Issue 689260
Corrected unnecessary Severe Warnings for MSGraph account
Resolved in Pega Version 8.7
After configuring an email account with MSGraph settings and saving the the email account instance, three unneeded severe guardrail warnings were generated related to using D_pxGetApplicationSettingValue instead of a constant value. This has been resolved.
INC-198632 · Issue 687582
Handling added to correct class setting during DX-API
Resolved in Pega Version 8.7
When a DX-API call was made (assignments/{ID}/actions/{actionID}/refresh) the ApplyPageInstructions activity was updating the case with an incorrect class, causing the rules from the wrong class to be picked and blocking the case progression. This has been resolved by setting the proper parameter Param.workPage while calling pzApplyPageInstructions from pzUpdateCaseWithRequestBody to calculate the proper class for the content.
INC-200029 · Issue 690167
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.7
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-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.