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.
INC-132976 · Issue 580682
Performance improvements for Test Strategy data flow
Resolved in Pega Version 8.2.8
In the Test Strategy panel under Single case -> "Settings", selecting the "Data flow" option and choosing CustomerData dataflow was taking an excessive amount of time to run on a system with an extremely large database. To improve performance, two areas have been addressed: 1) the default behavior for record key suggestions in the test panel has been modified to collect only the ID as the additional data is not necessary at that time; 2) a DSS has been added that will opt out of reading and collecting the customer IDs in order to minimize data stored on the clipboard.
INC-136394 · Issue 582526
Improved performance for WebTreatments
Resolved in Pega Version 8.2.8
When there were a very large number of treatments propositions in WebTreatments DDR, one analyst trying to save a Treatment caused another analyst to get a DDR locked error. This was traced to the save process for a Proposition taking an excessive amount of time, and has been resolved by modifying the pzModifyDDRule activity to handle cleanup of the pxResults page on edit/update of a decision data rule.
INC-137255 · Issue 584906
Resolved Cassandra query read/write latency
Resolved in Pega Version 8.2.8
Read/write latency was seen when certain Cassandra queries were triggered by the system. This was traced to an unusual case where a flush was not done for an exceptionally long time period, and has been resolved.
INC-142084 · Issue 599876
Support added for expression in strategy scorecards
Resolved in Pega Version 8.2.8
When invoking REST against a dataflow that had a strategy containing a scorecard that used an expression and the "Include model explanations option" was enabled in the Strategy configuration, the system failed with the error "PropertyValueInvalid .pxMaxScore Cannot cast the value (unknown) to double". This was traced to the Scorecard explanations failing during serialization when an expression was used, and has been corrected.
INC-143927 · Issue 599491
Oracle database performance improvements
Resolved in Pega Version 8.2.8
When the IH Summary was enabled and materialized on an ADM model, updating the ADM model was very slow on large sites. This has been resolved by adding several performance improvements for working with Oracle databases, including Oracle pre/post processing steps.
SR-D93777 · Issue 565692
Handling added for Oracle Aggregate IH Summaries
Resolved in Pega Version 8.2.8
When using using (Non Materialized) IH Summaries to aggregate IH data, the data returned by the IH summary did not include all the expected records. If the same criteria was executed on the database via SQL or by using a strategy to process raw IH data then the results were as expected. This was due to a difference in handling of Oracle vs postgres which causes an order by clause not to be generated in the query: the postgres column name is lower case, while in Oracle it is upper case. This has been resolved by updating the system to get the column name correctly from the propertytocolumn map so IH records are returned in correct order by Browse By Keys operation.
SR-D95605 · Issue 565486
Data Flow correctly saved to Database table Dataset
Resolved in Pega Version 8.2.8
After setting up a dataflow with Report definition as a source and Database table dataset as destination with the option "Insert new records and override existing", a data transform was used to modify a few of the values and write to the same database table. This table was mapped to pegadata schema and didn't have a pzpvstream column. Running the data transform generated an exception stating "DataStoreSaveStatementWithoutStream(PageDatabaseMapperImpl). The error was not seen when the pzpvstream column was added or if pzInskey was also removed along with pzpvstream, or if "only insert new records" was selected. This was traced to pzInsKey and pxInsName being null in the query formed while writing. There are two execution paths for the database dataset save operation, one for internal tables and another one for external tables. For a table with pzInskey but no blob, the system was incorrectly using the external table logic. This has been corrected.