Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number in order to find the associated Support Request.

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-A96852 · Issue 264159

Resolved OOM error when adding VDB DNode

Resolved in Pega Version 7.2.2

A memory leak was found relating to JBDC PreparedStatement objects (char arrays allocated to hold database query results) used when VBD loads its data partitions. This has been fixed with the addition of code to close the PreparedStatement objects created when loading Actuals partition data.

SR-A99782 · Issue 266250

XSS vulnerability closed in Warning Justification Text field

Resolved in Pega Version 7.2.2

A potential XSS vulnerability has been addressed in the Warning Justification Text field.

SR-A96515 · Issue 267504

Added handling for Qualsys security scan

Resolved in Pega Version 7.2.2

A stack overflow error was being generated when running a Qualsys vulnerability security scan on servers hosting IBM WebSphere and Pega, resulting in two of the three Pega nodes in production becoming unresponsive and requiring a restart. This was caused by the third party tool connecting to port 7003, which is used by Stream data set server, and sending unknown requests. To avoid this, the system has been updated to not send back a response if the channel is closed

SR-A79502 · Issue 253855

Corrected ability to add DNode port via prconfig

Resolved in Pega Version 7.2.2

Adding DNode Port via prconfig was not taking effect due to the configuration values being stored as strings, but the code which reads the storage port configuration treats the setting as integer. This has been fixed.

SR-A87150 · Issue 256602

Dynamic setting added to override ADM JMS default

Resolved in Pega Version 7.2.2

ADM (a part of Pega DSM) was detecting JMS and switching over to JMS when available and using HttpInvoker in other cases. In order to allow customization, it is now possible to override the ADM JMS configuration and allow EAR deployments by way of a dynamic system setting to disable JMS at will.

SR-A102723 · Issue 270420

Pulse will not fire ADM model update until node is ready

Resolved in Pega Version 7.2.2

ADMExceptions were seen during ADM node restart due to ADM clients triggered by Pulse trying to update models on the server when the server is not yet in NORMAL state. To correct this, Pulse operation has been modified to not to fire the model update process when the node is not yet in NORMAL state.

SR-A95909 · Issue 265781

PegaMarketing custom shape RUF compilation fixed

Resolved in Pega Version 7.2.2

After upgrade, the PegaMarketing custom data flow shape was failing while calling Rule-Utility-Function libraries. This was caused by an error in the compilation process, and the data flow generation code has been modified to use a different class loader that takes libraries into account.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us