SR-C53967 · Issue 392506
New wrapper API created to handle external Cassandra nodes for ADM models
Resolved in Pega Version 8.2
When the Decision Data Store Service was configured to use an external Cassandra instance, the Adaptive Models Management landing page did not list the number of models when a strategy referencing an ADP Model was run, and the message "Error loading adaptive decision management server data. Ensure adaptive decision manager and decision data store service nodes are available." was displayed. This issue was traced to the ADM service relying on a FunctionalNodes API provided by DSM service infrastructure that was not able to recognize external Cassandra nodes. To correct this, a new wrapper API pyADMHasFunctionalNode has been created.
SR-C53999 · Issue 393425
Added missing validation trigger for survey question page
Resolved in Pega Version 8.2
Validate rule or preaction was not firing as expected for the Question page in Pega Survey. This was due to a missing step which has now been added to pzDisplayQuestionPagePostAct.
SR-C49844 · Issue 394996
Added check for external Cassandra cluster to avoid unnecessary DDS pulse error logging
Resolved in Pega Version 8.2
After upgrade, DDS pulse errors were filling up the jvm.out logs. This was caused by a check in system_auth keyspace that was redundant for sites running their own Cassandra cluster (external). To fix this, DDS pulse operation will check If the Cassandra cluster is external; if it is, it will not check system_auth keyspace and will Omit DDS pulse operation actions except update logging.
SR-C57025 · Issue 395184
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.2
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-C40145 · Issue 392708
Restarting the SVM training analysis checks for existing model request to continue
Resolved in Pega Version 8.2
When creating a predictive model there was an issue with completing the SVM training analysis either due to error or browser crash. In previous versions of Designer Studio the session would stay alive and continue to execute, however more recent versions of the decision analysis's portal expected the user to keep the session active in order for the model to complete even though for long-running model training it is not viable to keep a session open for many hours. This was caused by the model generation process being kicked off again when the wizard was relaunched, and has been resolved by adding a check to the relaunch that will look for an existing model generation request and continue with the same request if one is found.
SR-C58241 · Issue 402735
Agent Access Group corruption resolved
Resolved in Pega Version 8.2
The Access Group used by agents was intermittently becoming corrupted. This was caused by a timing issue where sometimes the conclusion was built before the rulesets to the requestor were set up, resulting in the role being added to the RoleNotFound cache. To resolve this, the RoleNotFound cache has been removed so that every time a role lookup happens the system will check the database.
SR-C42849 · Issue 395987
Validation corrected to honor Read-Only designations
Resolved in Pega Version 8.2
Validation was happening on Read-Only fields due to pyReadonlyValidation not being honored in all editable cases. This has been corrected.
SR-C54754 · Issue 395508
Work by Work Queue modified to use RD in place of deprecated list view
Resolved in Pega Version 8.2
When the "Find" button was selected in Designer Studio >> Case Management >> Tools >> MyWork >> Work by Work Queue, a series of dotted lines that exceeded the section limitation appeared. This was traced to the use of the deprecated function List-view in workbasketlistPopup. In order to support the needed display, the Pega-Landing.pzProcessAndCaseRulesMainMenu Navigation rule has been modified to call a report definition Assign-WorkBasket.pyASSIGNMENTSFORWORKBASKET instead of the deprecated list view. While there is a small difference in user experience and behavior, all the columns being fetched and filters being added will be similar to that of the ones previously seen in the list view.
SR-C55269 · Issue 395845
Custom filter values correctly pass to custom drilldown filters
Resolved in Pega Version 8.2
Reports with summarize column, drilldown, and custom inline sections were not forwarding values from the custom filter to the drilldowns custom filter. This was a missed use case in earlier work done to ensure custom filter values are populated during runtime, and has been added.
SR-C59762 · Issue 402287
Custom filter values correctly pass to custom drilldown filters
Resolved in Pega Version 8.2
Reports with summarize column, drilldown, and custom inline sections were not forwarding values from the custom filter to the drilldowns custom filter. This was a missed use case in earlier work done to ensure custom filter values are populated during runtime, and has been added.