INC-189811 · Issue 679936
Updated XMLDataToPage privilege
Resolved in Pega Version 8.6.3
Cases were not being created or moved due to a privilege issue on EndUser portal after update. This was traced to the XmlDataToPage activity now including the OpenDeveloperForm privilege, which end user operator profiles do not have. This was a missed use case, and has been resolved by updating XMLDataToPage so it requires authentication but not privilege to run.
INC-190111 · Issue 693527
Security updated for viewing data tables
Resolved in Pega Version 8.6.3
In order to improve security related to viewing data table instances, the privilege pxListClassRecords has been created in @baseclass and added to the "may start" activity ListEditor. Please add the privilege pxListClassRecords to access groups using ListEditor.
INC-190111 · Issue 695615
Security updated for viewing data tables
Resolved in Pega Version 8.6.3
In order to improve security related to viewing data table instances, the privilege pxListClassRecords has been created in @baseclass and added to the "may start" activity ListEditor. Please add the privilege pxListClassRecords to access groups using ListEditor.
INC-190380 · Issue 678644
CreateVersion rule updated for REST Integration Wizard
Resolved in Pega Version 8.6.3
When using a JSON response in the Create REST Integration wizard to generate the rules, the wizard displayed a null pointer exception during the final generation. The error pop up message "Generation process has been canceled and all created records have been removed" was displayed on the screen. This was traced to the REST Integration Wizard putting data rules in the wrong ruleset version when the context of both the Integration Layer and the Data Layer were configured to use an existing ruleset and to create a new version of that ruleset, and has been resolved by modifying the pzCreateVersion rule to support this.
INC-191033 · Issue 684371
Security updated for viewing data tables
Resolved in Pega Version 8.6.3
In order to improve security related to viewing data table instances, the privilege pxListClassRecords has been created in @baseclass and added to the "may start" activity ListEditor. Please add the privilege pxListClassRecords to access groups using ListEditor.
INC-191673 · Issue 679946
"Keep file open" updated
Resolved in Pega Version 8.6.3
When "keep file open" was checked, Connect-File was failing with a java.io.IOException: Stream Closed error if called more than once. When "keep file open" is checked, the very first Connect-File call saves the handle to the OutputFileStreamWrapper of the requestor page. Any subsequent Connect-File calls will access this saved OutputFileStream but the stream is already closed, resulting in the exception. To resolve this, the try-with-resources statement that closed the OutputStream has been removed.
INC-192820 · Issue 680454
Classmap will not be rebuilt if there are no class changes
Resolved in Pega Version 8.6.3
The get MBA service was not working as expected after update. This was traced to a Strategy FUA contention issue with ClassmapImpl: each time the System Pulse processed a CACHE type, it resulted in the ClassMap being rebuilt even if a Class was not added or deleted. To resolve the issue, a condition check has been added on the two places in ProcesChangesFromPulse.processChanges() that call DatabaseImp.noteConfigChangesInClassMap(). If the size of the list is 0, there is no need to rebuild.
INC-192820 · Issue 697830
Resolved time zone logging thread contention
Resolved in Pega Version 8.6.3
Contention was observed in a call stack when multiple threads were logging alerts concurrently related to time zone. This was due to the TimeZone.getTimeZone method being synchronized, and has been resolved by switching to a static instance of a JSR 310 DateTimeFormatter that it is immutable and thread safe.
INC-193507 · Issue 681749
DSS added to control DADT purge
Resolved in Pega Version 8.6.3
Thread dumps and service restarts were seen when Decision Engine data nodes were working with a very large number of tables. This has been resolved by adding a DSS as part of the CDH layer which will skip CDH DADT that contains pattern DATA_BATCHOUT, for instance "DATA-ADMIN-DB-TABLE DATA-BATCHOUTPR469001" to prevent the deletion causing full cache invalidation of the table information map. With this DSS set to true, when the purge agent runs and deletes the DADT, class cache should no longer be invalidated. With the DSS missing or set to a value other than true, the class cache invalidation will still occur.
INC-193767 · Issue 683300
Handling updated for validating properties with a FieldValue
Resolved in Pega Version 8.6.3
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.