INC-120600 · Issue 565199
Handling added to avoid primary key exception in pxExtractDataWithArgs
Resolved in Pega Version 8.2.8
While running the activity pxExtractDataWithArgs with -c, the "Error while getting the sequenceNumberERROR: duplicate key value violates unique constraint pr_log_pk" occurred if both Parent and Child classes were pointing to different table and extraction started from the child class. In this case, because the Parent and Child classes were pointing to different tables while extracting with the -c option, the class list order caused a primary key constraint violation exception while generating the process sequence number. To resolve this, while adding the classes to the instance map, the order will be changed to parent followed by child classes.
INC-128899 · Issue 578020
Resolved BIX Extract Summary Status Count mismatch
Resolved in Pega Version 8.2.8
A mismatch was seen between the summary of the Extract Summary Status Count in the Execution History stats versus the logs, for example the execution history saying 98.74% completed while the log says 100% or 100.45% completed. Investigation showed there was mismatch in the query based on the filter value given in the extract rule and the where clause in the query that resulted in an error in calculating percentage in case of any exception. This has been resolved.
INC-133173 · Issue 573440
Landing page refresh modified to avoid frequent reloads
Resolved in Pega Version 8.2.8
Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.
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.
INC-130761 · Issue 570061
ADMSnapshot agent defaults to running on a single node
Resolved in Pega Version 8.2.8
The ADMSnapshot agent runs when ADM is used, and should be run on only one node to prevent duplicate snapshots being created. To ensure preferred behavior, the "Run this agent on only one node at a time" option has been selected by default for ADMSnapshot agent.
INC-131620 · Issue 577537
DSS added to control monitoring data mart purge
Resolved in Pega Version 8.2.8
An enhancement has been added to automatically purge older data in the monitoring data mart at regular intervals so that it doesn't grow large enough to cause a lack of space or cause stress on the database resources. This is handled through the DSS decision/monitoring/daysToKeepData; the default is six months.