INC-143861 · Issue 597558
pzIsScalar 'when' rule updated for Value list and Value group
Resolved in Pega Version 8.2.8
When using the GET/Cases/{ID} API to fetch details about a case, an intermittent HTTP 500 error appeared. This was traced to the 'when' condition pzIsScalar being returned as true for the ValueList property types and trying to set the value on the summaryData embedded page. This has been resolved by updating the pzIsScalar 'when' rule to better handle Value list and Value group.
INC-144358 · Issue 601013
Localization added for "Automatically" and "Manually" field values
Resolved in Pega Version 8.2.8
The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.
SR-D72456 · Issue 561116
Added duplicate page handling for Bulk actions
Resolved in Pega Version 8.2.8
Trying to resolve cases using Bulk Actions and Bulk Resolve resulted in the exception "Trying to save an invalid page. The cover open count is incorrect; it is -1". This was traced to duplicate pages available on the clipboard with same the insHandle. To resolve this, the pzUpdateAndDeleteAssignments activity has been updated to check for duplicate pages, then pick the right page which is not being served by the findPageByHandle engine API.
SR-D77719 · Issue 569770
OpenIfStale updated to resolve optimistic locking race condition
Resolved in Pega Version 8.2.8
A race condition was created in optimistic locking by having two assignments save at overlapping times. This has been resolved by modifying the pzShowConflicts activity to use a version of openIfStale which will consider a workpage as stale even if the difference in pxUpdateDatetime is in milliseconds.
SR-D98224 · Issue 580592
Updated endpoint Cross-site scripting protection
Resolved in Pega Version 8.2.8
Cross-site scripting security has been updated for Endpoints in Display activities.
INC-126129 · Issue 569667
PropertyToColumnMap made more robust
Resolved in Pega Version 8.2.8
The DF_ProcessEmails dataflow was intermittently failing with a StageException error. This was traced to schema changes being propagated asynchronously by system pulse, which seem to have caused PropertyToColumnMap to cache stale schema. To resolve this, if the property mapping is not found the first time, the system will make a second attempt to get the mapping. Additional logging has also been added for better diagnostics.
INC-126319 · Issue 566343
Able to add offer to Change Request after deleting other offer from the landing page
Resolved in Pega Version 8.2.8
A Change Request creation was failing after deleting an offer rule from the revision management landing page. While deleting the offer rule, the activity pyDeleteRuleFromLP is called and pxDeleteRecord API is used to delete the rule. The pyWorkPage is being modified with class Work-ProjectManagement-CheckIn when the pxDeleteRecord activity is executed, but after this, the Change Request creation failed due to the wrong context of the pyWorkPage. This has been resolved by adding Page-New of pyWorkPage conditionally.
INC-126801 · Issue 576324
Improved cleanup for adm_response_meta_info
Resolved in Pega Version 8.2.8
The adm_commitlog.adm_response_meta_info column family was growing, leading to gradual increase in CPU utilization on the ADM nodes over time. Investigation showed that the compaction on the adm_response_meta_info table was not being triggered by the ADM service, and the compaction did not remove rows that belonged to models that had been deleted. To resolve this, compaction of the adm_response_meta_info table has been moved from the ADM client nodes to the ADM service nodes, which will correctly trigger the compaction on a predefined schedule. The compaction logic has also been refactored to remove rows that belong to models that have been deleted.
INC-128342 · Issue 594184
Improved cleanup for adm_response_meta_info
Resolved in Pega Version 8.2.8
The adm_commitlog.adm_response_meta_info column family was growing, leading to gradual increase in CPU utilization on the ADM nodes over time. Investigation showed that the compaction on the adm_response_meta_info table was not being triggered by the ADM service, and the compaction did not remove rows that belonged to models that had been deleted. To resolve this, compaction of the adm_response_meta_info table has been moved from the ADM client nodes to the ADM service nodes, which will correctly trigger the compaction on a predefined schedule. The compaction logic has also been refactored to remove rows that belong to models that have been deleted.
INC-129212 · Issue 572541
Strategy restoration repaired
Resolved in Pega Version 8.2.8
Once a strategy was deleted, it could not be restored afterward and a validation error appeared. This was an issue with some rule components being erroneously marked as required, and has been corrected.