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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A20073 · Issue 235672

Corrected runtime handling for List Utility functions inside strategies

Resolved in Pega Version 7.2.1

When the List Utility functions 'IsInPageListWhen' and 'IndexOfPageList' were used inside strategies, the functions worked in the API(webservice) request but generated UnsupportedOperationException errors in the Program run. This was traced to a missing implementation of DSMClipboardProperty.indexOf(), which has now been added.

SR-A20470 · Issue 240001

Twitter harvesting enhanced

Resolved in Pega Version 7.2.1

Data recovery has been improved for Pega Customer Service Social Engagement customers harvesting Twitter streaming data. If a steaming data set fails for any reason, whether due to disconnecting of the API for a short period, server failure, or for any other scenario where Tweets are not ingested in real time, the data recovery capability will fetch missed Tweets within a given set time window of recent Twitter historical data. This is done through an activity to create a Twitter search data set which can then be used to work act as a data source for the data flow. Additionally, logic has been added to identify the appropriate language for short inputs (one or two words).

SR-A21081 · Issue 242397

Strategy rule information added to tracer

Resolved in Pega Version 7.2.1

A tracer invoked with SOAP service --> Activity --> Flow --> Interaction rule --> Strategy was only showing the the executed components in its (reversed) execution order and did not show the execution strategy path. This has been fixed.

SR-A21756 · Issue 244285

defined-on class error resolved

Resolved in Pega Version 7.2.1

A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.

SR-A21756 · Issue 243206

defined-on class error resolved

Resolved in Pega Version 7.2.1

A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.

SR-A21844 · Issue 241153

VBD enhancements

Resolved in Pega Version 7.2.1

The following enhancements have been added to the Visual Business Director feature of PRPC Decisioning: - Support added for changes in field sizes after partitions load - Partitions will be loaded immediately on VBD server startup - Data expiration based on inactivity is disabled to reduce query latency - Timeout added to VBD queries to handle latency when Partitions initially load - Code that processed Actuals query JDBC resultset is optimized

SR-A22841 · Issue 245073

All Data Flow keys considered for filtering

Resolved in Pega Version 7.2.1

When a Data Flow containing a Filter was run , the filter step showed incorrect results in the "Successful records" column even though previewing it from the Data Flow rule it showed the correct result. The algorithm that queries a secondary source shape in the data flow was ignoring all but the first key, and has been updated to properly process all of the keys before displaying any results.

SR-A23035 · Issue 245109

Enabled bulk delete of ADM models

Resolved in Pega Version 7.2.1

In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria." PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."

SR-A23395 · Issue 245032

Optimized decision data components

Resolved in Pega Version 7.2.1

Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.

SR-A23395 · Issue 243235

Optimized decision data components

Resolved in Pega Version 7.2.1

Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.

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