INC-193917 · Issue 683684
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-194224 · Issue 682649
New or updated operators properly updated on other nodes
Resolved in Pega Version 8.6.3
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-194269 · Issue 681047
Added handling for Create Source and Target properties of Date
Resolved in Pega Version 8.6.3
A report definition was not displaying results after update, and a stack overflow was reported. This was a missed use case for Create Source and Target properties of Date, and has been resolved by adding a boolean flag to avoid autochain during validations when data type is Date.
INC-194348 · Issue 682340
Resolved multiple copies of Pega0050 alerts
Resolved in Pega Version 8.6.3
The PDC alert Pega0050 was seen multiple times for the standard pxgetoperatordetails activity, step 6.This has been fixed by removing the pagecopy and updating the data page properties.
INC-194490 · Issue 685240
Parameter handling updated for GetRepositoryFolderName
Resolved in Pega Version 8.6.3
An UnresolvedAssemblyError was generated with an Unauthenticated Thread exception after opening the declare expression Embed-Application-StorageProvider pyFolder and performing a private edit. This error was traced to the Rule-Utility-Function call "pxGetRepositoryFolderName()", which was expecting a parameter "tools" which was not being passed from the declare expression rule. To resolve this, the pyFolder and pyFoldeIf declare expressions and pzsetContentStorage have been modified to pass 'tools' as a parameter to pxGetRepositoryFolderName.
INC-194594 · Issue 684715
Parameter handling updated for cloned environment
Resolved in Pega Version 8.6.3
The Editable data page parameters were not getting set in a cloned environment. This has been resolved by adding code to detect the use case ('append and map to action' with 'a new page' relation) and let it fallback to legacy code generation.
INC-194806 · Issue 680969
Performance improvement for message processing
Resolved in Pega Version 8.6.3
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 688604
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-196389 · Issue 690787
ConfigurationReconciliationTask updated for greater compatibility
Resolved in Pega Version 8.6.3
After updating from Pega 8.3 to Pega 8.6, models which previously had learning and performance AUC greater than 0.7 reported an AUC of 0.5. This was traced to the update handling in ConfigurationReconciliationTask. AdmRuleBrowser does not perform ruleset resolution, so all rules were returned, for example the rule for model A in both the 08-01 and 08-03 ruleset. The system then iterated over all of the adaptive model rules returned by AdmRuleBrowser in order to assess whether a configuration update was necessary. The condition to update the model rule was met when either the config key did not exist (indicating a newly added configuration) or the model rule was "old" (version <2). For models generated in Pega 8.3 or earlier the version number for all rules must be 1, and the update to Pega 8.6 therefore caused the ConfigurationReconciliationTask to be applied to all adaptive model rules. To resolve this, the configuration update check in ConfigurationReconciliationTask has been removed.
INC-196415 · Issue 686315
Performance improvements for revalidate and save
Resolved in Pega Version 8.6.3
In order to improve performance when working with very large numbers of class definitions, an update has been made to optimize the revalidate and save process by avoiding looking up all classes on the system instead using ClassDefinition for existence and checking ancestor data to ensure class is a Rule- or Data- descendant.