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-116508 · Issue 170253

Large flow handling improved for IE8

Resolved in Pega Version 7.1.7

When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.

SR-116818 · Issue 167121

Corrected swim lane routing with shapes

Resolved in Pega Version 7.1.7

While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, and has been corrected.

SR-117228 · Issue 168249

Resolved issues with Flow shapes distributed across Swim Lanes

Resolved in Pega Version 7.1.7

Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.

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-A733 · Issue 207631

Edited Propositions retain format

Resolved in Pega Version 7.2

When updating a Proposition using the "Edit" button, the format was lost, however updating the proposition using the "Bulk Edit"-> 'Edit in Excel' button preserved the formatting. This has been addressed by making the default UI control for the text values a Text Area, which maintains the multi-line format.

SR-A6547 · Issue 217014

Updated handling for empty keys in DataSet-Execute

Resolved in Pega Version 7.2

When executing a 'delete by keys' operation in a DataSet-Execute method, passing empty keys would intermittently cause the whole dataset to be truncated or deleted. To create a more robust execution environment, when a Dataset-Execute is called and no key is passed it will trigger a delete statement matching the key value to null.

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