Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C53680 · Issue 402914

Filter value Autocomplete uses localized text for the 'Case Type' string

Resolved in Pega Version 8.1.1

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-C53788 · Issue 402936

Cassandra enhancement added to allows enabling or disabling table truncation

Resolved in Pega Version 8.1.1

Truncations of Cassandra tables sometimes failed if the compactions were interrupted or if all nodes in the cluster were not available. In order to support more customization, operations have been added to allow compaction of Cassandra tables to be disabled and enabled. The system will also log if a truncate is not possible due to the consistency of the cluster. In order to disable compactions for a DDS Dataset's Cassandra table the following code can be included in an Activity: com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSet dataset = (com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSet)com.pega.dsm.dnode.api.dataset.DataSets.instance(tools, "<Application Name>", "<DDS DataSet Name>"); com.pega.dsm.dnode.api.dataset.operation.Operation<?> operation = dataset.getOperationByName("Disable Auto compaction"); operation.execute(tools, myStepPage, null); To re-enable compactions for a table the following code can be run as an Activity: com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSet dataset = (com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSet)com.pega.dsm.dnode.api.dataset.DataSets.instance(tools, "<Application Name>", "<DDS DataSet Name>"); com.pega.dsm.dnode.api.dataset.operation.Operation<?> operation = dataset.getOperationByName("Enable Autocompaction"); operation.execute(tools, myStepPage, null); It is recommended that the disabling of staging tables be performed after the completion of a successful upload and the reading of the staging table is complete. It is recommended that the compactions be re-enabled after the truncation of the table is complete and before the loading of the staging table.

SR-C53788 · Issue 402937

Cassandra enhancement added to allows enabling or disabling table truncation

Resolved in Pega Version 8.1.1

Truncations of Cassandra tables sometimes failed if the compactions were interrupted or if all nodes in the cluster were not available. In order to support more customization, operations have been added to allow compaction of Cassandra tables to be disabled and enabled. The system will also log if a truncate is not possible due to the consistency of the cluster. In order to disable compactions for a DDS Dataset's Cassandra table the following code can be included in an Activity: com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSet dataset = (com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSet)com.pega.dsm.dnode.api.dataset.DataSets.instance(tools, "<Application Name>", "<DDS DataSet Name>"); com.pega.dsm.dnode.api.dataset.operation.Operation<?> operation = dataset.getOperationByName("Disable Autocompaction"); operation.execute(tools, myStepPage, null); To re-enable compactions for a table the following code can be run as an Activity: com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSet dataset = (com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSet)com.pega.dsm.dnode.api.dataset.DataSets.instance(tools, "<Application Name>", "<DDS DataSet Name>"); com.pega.dsm.dnode.api.dataset.operation.Operation<?> operation = dataset.getOperationByName("Enable Autocompaction"); operation.execute(tools, myStepPage, null); It is recommended that the disabling of staging tables be performed after the completion of a successful upload and the reading of the staging table is complete. It is recommended that the compactions be re-enabled after the truncation of the table is complete and before the loading of the staging table.

SR-C53967 · Issue 402919

New wrapper API created to handle external Cassandra nodes for ADM models

Resolved in Pega Version 8.1.1

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 402911

Added missing validation trigger for survey question page

Resolved in Pega Version 8.1.1

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-C54754 · Issue 402915

Work by Work Queue modified to use RD in place of deprecated list view

Resolved in Pega Version 8.1.1

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-C55017 · Issue 402951

Mapping corrected for Constraints rule properties

Resolved in Pega Version 8.1.1

The Constraints rule was not working for page list due to Page context and Page Context class both referring to the same property of pyPageContextClass. This was an error introduced during a UI Ruleform upgrade, and has been resolved by correcting the mapping of the "Page Context" field to pyPageContext.

SR-C55058 · Issue 402925

Stream Service stability improvements and Kafka upgrade

Resolved in Pega Version 8.1.1

A number of improvements have been made to Stream Service stability, and apache-Kafka has been updated to v1.1.0.1.

SR-C55269 · Issue 402958

Custom filter values correctly pass to custom drilldown filters

Resolved in Pega Version 8.1.1

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-C55337 · Issue 402905

Removed duplicated parameter encoding from Create Work action string generation

Resolved in Pega Version 8.1.1

Multibyte characters such as Japanese or Chinese passed as parameters to the Create Work action of a button were being encoded/decoded twice. This resulted in parameters being incorrectly interpreted in the newly created Work. To correct this, the parameters will not be encoded during the action string generation for Create New Work, and the necessary encoding will be handled only by SafeURL.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us