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-A7611 · Issue 217142

Ampersand not rendered properly for DropDown

Resolved in Pega Version 7.2

In case of dropdowns with defer load, options having "&" were being double-encoded and displayed as '&'. The API has been updated to correctly handle the special character.

SR-A1440 · Issue 213844

Added catch for unspecified layout format

Resolved in Pega Version 7.2

Layouts saved without a format name were not rendering correctly; the container format was changed to 'other', which generated an exception due to the 'other' format not being available in the XML. To prevent this error, the layout format assignment is now wrapped in the JS with a try-catch.

SR-A3540 · Issue 210203

Added check for duplicate Date Control validation error

Resolved in Pega Version 7.2

In a screen flow, it is possible to move forward despite validation errors on the Date control. However, returning to the control caused the validation error message to be displayed twice. This was caused by both the server side and the client side generating the error. To correct this, logic has been added to check if the clipboard already has the messages defined in pClientErrors and avoid adding them to the clipboard if so.

SR-A6010 · Issue 215099

Added handling for special characters in RUF labels API

Resolved in Pega Version 7.2

A change in the handling of special characters such as quotation marks was causing compiler errors after upgrade. This was traced to the StringUtils.escapeIntoJavaString api for label generation in generateCellContent RUF and has been corrected.

SR-A6636 · Issue 215085

Added missing hover text for closing work object

Resolved in Pega Version 7.2

Hovering the mouse over the "X" (Close) icon in a work object was displaying the same message given when hovering over the tab. This was due to a missing "Title" attribute in the dynamic container, and has been fixed.

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