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-183530 · Issue 668470
Null check added for missing compiler path
Resolved in Pega Version 8.7
After upgrading from Pega 7.3 to Pega 8.6, libraries were not loading correctly and a java error was seen. This was traced to the compiler default path values not getting picked from DSS / settings->compiler->Default paths, which was caused by a null value for the DASS setting in the systemSettings map. To resolve this, a null check has been added and an update has been made to use getEngineDynamic to ensure this setting is picked on node startup.
INC-193767 · Issue 683299
Handling updated for validating properties with a FieldValue
Resolved in Pega Version 8.7
Running a report which included a property calculated by a Declare Expression generated an excessive number of log messages indicating "Error occurred while executing forward chaining on page 'pyReportContentPage.pxResults". Degraded system performance, stack overflow, and other similar issues were seen. This was traced to an infinite loop that resulted from a missed use case for a Report Definition with a Target property of a Declare Expression with FieldValue, and has been resolved by disabling autochain while validating properties with a FieldValue.
INC-161737 · Issue 639845
Queue processor correctly moves items to Broken Items
Resolved in Pega Version 8.6.1
When an exception occurred while Queue Processor processed an item, he queue item was not moved to Broken Items. The error " inconsistent datatypes: expected - got CLOB DatabaseException caused by prior exception" was generated. This has been resolved by modifying the NativeSQL builder and NativeSQLBatchExecutor to allow the batch of queries to be retried. Additional changes were also added for Oracle databases to identify the correct column types.
INC-168983 · Issue 645791
Jobs restart after system failure
Resolved in Pega Version 8.6.1
Several key standard CLUSTER type jobs were left in disabled state after a performance break test with rolling restart of the nodes. This was traced to prevention code that was originally intended to disallow stopping the scripts, but had an unexpected result after a system failure when the request to restart the standard pzDelayedQueueProcessorSchedule was rejected if the check of the job name matched the deny list. This has been resolved by removing the preventative code.
INC-175672 · Issue 652943
ServicePackage threads properly released
Resolved in Pega Version 8.6.1
After completing a system stress test, the requestor pool threads for the ServicePackage were not released. Investigation showed that the threads were waiting for Data Pages to be loaded in the background even though there was no background job corresponding to those data pages in the Async Services pool. This has been resolved by making an update to avoid removing the object handlers when the load-datapage finds that an entry exists with a NOT_STARTED state.
INC-175672 · Issue 652944
ServicePackage threads properly released
Resolved in Pega Version 8.7
After completing a system stress test, the requestor pool threads for the ServicePackage were not released. Investigation showed that the threads were waiting for Data Pages to be loaded in the background even though there was no background job corresponding to those data pages in the Async Services pool. This has been resolved by making an update to avoid removing the object handlers when the load-datapage finds that an entry exists with a NOT_STARTED state.
INC-187708 · Issue 680012
Handling added to StreamChangeTracker for non-String mode
Resolved in Pega Version 8.7
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-174243 · Issue 655887
Links to specifications persist appropriately
Resolved in Pega Version 8.6.1
When linking Rules to Specifications, check-ins of some unrelated rules deleted the link. Investigation showed the deletion happened in the pzHandleLinksPostCheckIn activity, and was caused by an empty parameter page name that caused pcInsKey to not have a value, so all links returned by "Obj-Browse" were later deleted. To resolve this, an update has been made to insure the "Pass current parameter page" option in step 2 of the Connect REST PostCheckIn activity is enabled so that the downstream activity pzHandleLinksPostCheckIn behaves as expected.
INC-174243 · Issue 655886
Links to specifications persist appropriately
Resolved in Pega Version 8.7
When linking Rules to Specifications, check-ins of some unrelated rules deleted the link. Investigation showed the deletion happened in the pzHandleLinksPostCheckIn activity, and was caused by an empty parameter page name that caused pcInsKey to not have a value, so all links returned by "Obj-Browse" were later deleted. To resolve this, an update has been made to insure the "Pass current parameter page" option in step 2 of the Connect REST PostCheckIn activity is enabled so that the downstream activity pzHandleLinksPostCheckIn behaves as expected.