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.
INC-179727 · Issue 704545
Modified batch requestor handling to ensure cleanup
Resolved in Pega Version 8.6.4
A large buildup of batch requestors was seen, and restarting the node did not clear it. Investigation showed that in the case of one class reading a DSS value, a Pega requestor was being created when it was unable to retrieve any Pega context, and this requestor was not cleaned up afterwards. To resolve this, an update has been made to the way the requestor and Pega context is being created along with ensuring it will be cleaned up properly after use.
INC-180246 · Issue 664947
Support for apostrophe added to keyword tokenization
Resolved in Pega Version 8.6.4
A keyword containing an apostrophe was not detected properly in Text extraction model. This has been resolved by updating the annotator used in the tokenization.
INC-192826 · Issue 685797
PMML updated for nested 'if'
Resolved in Pega Version 8.6.4
Running a model on the openscoring API and the Pega PMML model gave different results. This has been resolved by updating the handling for nested 'if' in PMML.
INC-194382 · Issue 697615
ADM Model management page updates
Resolved in Pega Version 8.6.4
When accessing the ADM model management landing page in an environment with a large number of nodes, an "UnresponsiveNodeException" error was thrown from the pylaststrategyresults activity by various nodes on different days. Investigation showed the ADM factory table was truncated, leading to inconsistent ADM data in the Last Responses Section. This has been resolved, and the ADM model management page has been made more resilient to node failures.
INC-196561 · Issue 688846
Natural Language Processing (NLP) topic categorization working consistently for German
Resolved in Pega Version 8.6.4
A few German words were not recognized by the Natural Language Processing (NLP) topic categorization if they were given in capital letters. This was traced to upper case keywords being lowercased during model creation time, but not during prediction time. To resolve this, all words will be lower-cased before the model analyzes the text.
INC-206109 · Issue 706238
Delayed Learning works correctly with Volume Constraints
Resolved in Pega Version 8.6.4
When running an outbound campaign using NBA Designers predictions and delayed learning in conjunction with volume constraints, the adaptive models ended up with incorrect feedback if the prediction had an Alternative label configured with a defined waiting window. This has been resolved with the addition of a new flag 'isVolumeConstraintEnabled' during dataflow creation which will check for volume constraint, and a filter in HandleResponses for that flag.