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-A6740 · Issue 214445

Bulk delete activity added for ADM models

Resolved in Pega Version 7.2

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."

SR-A8236 · Issue 217334

Data flow respects vertical scalability settings

Resolved in Pega Version 7.2

The number of threads per node specified in Decision->Simulation Settings->Topology landing page was not taken into account by data flow execution, leading to the inability to configure vertical scalability per PRPC node and/or exclude certain nodes from data flow execution. This was an error where the configuration was being ignored and a default value was always used, and has been corrected.

SR-A5666 · Issue 215313

Flow Image available in "WhereAmI" option of iframe

Resolved in Pega Version 7.2

In some cases, it was not possible to see a flow canvas when the request was made from external system (e.g.. calling Pega URL from iframe). The framework was not taking into account the case where the frame was embedded in a document from a different domain. The cause of this issue is that the iframe and the parent frame have different origins, which prevents Viewer Data registering correctly. The system has been updated to detect whether the parent frame has the same origin as iframe, then choose correct the parent context to register Viewer Data. The object used to contain viewer data should be created in the right context in order to avoid cross origin exceptions.

SR-A7256 · Issue 218467

Flow image resolution now set by default

Resolved in Pega Version 7.2

In some flows with widely spaced shapes, the resolution of the flow image was insufficient- i.e., the text inside the flow shapes is not legible. The flow image is captured at a user defined zoom level, causing the captured flow images to have non-uniform resolution. The image capture now is done at a default origin and zoom level. The image capture will then restore the user selected zoom level after the capture happens.

SR-A9615 · Issue 218861

Resolved NPE in batch processing Decision data flows

Resolved in Pega Version 7.2

A null pointer exception was being thrown when accessing the batch processing function for Decision data flows if the 'initservices/dnode' dynamic system was set to false. This was traced to a failure of the Flow Action pre-processing activity attempting to call DNodeServiceListener to initialize it, and a check has been added so the Data flow run manager will now try to initialize each time it is asked for an instance if it was not initialized already.

SR-A8387 · Issue 217780

Added prevention for inappropriate Google Chrome autofill

Resolved in Pega Version 7.2

When login userid and password were stored in the Google Chrome browse and autofill was enabled, Google Chrome was using those values to populate the RuleSet rule form's input field (hidden on UI on Versions tab) and password field (on the Security tab). Those invalid values caused a save failure. To fix the issue, the system will pre-populate the hidden input field so that Google Chrome does not auto fill this field on the client side.

SR-A3950 · Issue 209476

Corrected order of tabbing focus in Activity rules

Resolved in Pega Version 7.2

After opening an Activity rule, the Description text field did not receive focus at the expected point when tabbing through the steps. The activity steps have been rebuilt to correct the tabbing order.

SR-A5453 · Issue 215368

Fixed Edit in Excel with load balancing enabled

Resolved in Pega Version 7.2

Edit in Excel was not working for decision tables if a load balancing was enabled. This was traced to the load balancer port number being added to the RequestHomeURL, causing a malformed strURL for opening the decision table in Excel. A check has been added to evaluate whether the strURL starts with a proper protocol and host instead of checking for RequestHomeURL.

SR-133163 · Issue 203273

Refined property-set expansion to support complex activities

Resolved in Pega Version 7.2

Attempting to expand a property-set in an activity with many steps (20+) caused a failure and the activity locked up. Tin order to support complex activities, the activity call and clipboard functions in this call have been refined for efficiency.

SR-A5355 · Issue 215511

Resolved browser hang with large Map Values

Resolved in Pega Version 7.2

While opening very large Map Value ruleforms, some systems were hanging and thread dumps were seen in the logs. With Microsoft Internet Explorer , the error was "There was an error while loading the content given. Microsoft Internet Explorer Error Description: Not enough storage is available to complete this operation." This was an issue with the display grid not being able to show huge number of records in the map value grid. To resolve it, the map value grid will be hidden if it exceeds the given cell threshold.

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