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-119899 · Issue 177532

Breadcrumb functionality disabled for Process Modeler pending further development

Resolved in Pega Version 7.1.8

Some complex installations experienced OOM events and crashes when opening flows in Process Modeler that contained nested levels of nested sub flows. The root cause of this problem was code that allowed excess data to be opened into the clipboard for every sub flow that could potentially be run as a result of running the top level flow. To prevent this problem, breadcrumbs functionality has been disabled at this time. The canvas viewer is being rewritten for ML9 together with a new implementation of multi-level process navigation in order to resolve this issue.

SR-119899 · Issue 182818

Breadcrumb functionality disabled for Process Modeler pending further development

Resolved in Pega Version 7.1.8

Some complex installations experienced OOM events and crashes when opening flows in Process Modeler that contained nested levels of nested sub flows. The root cause of this problem was code that allowed excess data to be opened into the clipboard for every sub flow that could potentially be run as a result of running the top level flow. To prevent this problem, breadcrumbs functionality has been disabled at this time. The canvas viewer is being rewritten for ML9 together with a new implementation of multi-level process navigation in order to resolve this issue.

SR-120468 · Issue 184320

Appearance order retained for multiple swimlanes

Resolved in Pega Version 7.1.8

After putting multiple swimlanes in a flow, the order of their appearance was returning to the original state after saving it. This was caused by the rendering being performed in the order the server store/sent the swimlane data. To ensure proper behavior, the swimlanes are now reordered based on the swimlane layout (horizontal, vertical) and their coordinates before being rendered.

SR-120468 · Issue 185827

Appearance order retained for multiple swimlanes

Resolved in Pega Version 7.1.8

After putting multiple swimlanes in a flow, the order of their appearance was returning to the original state after saving it. This was caused by the rendering being performed in the order the server store/sent the swimlane data. To ensure proper behavior, the swimlanes are now reordered based on the swimlane layout (horizontal, vertical) and their coordinates before being rendered.

SR-121825 · Issue 181670

Multiple annotations now allowed for swimlane objects

Resolved in Pega Version 7.1.8

When two annotations were used with swimlanes, the description in the annotation is unexpectedly changed or the annotation itself disappeared due to an ID conflict. There was a workaround of adding the shapes using the right click, but the annotation shape is now correctly added to the work flow using the proper unique ID.

SR-122025 · Issue 181153

Dropped rule added to DSM rules for SR properties

Resolved in Pega Version 7.1.8

A set of rules was inserted into the UI of Proposition LP and Strategy rules in DSM (Designer Studio) for use in retrieving a list of SR properties. This set was inadvertently missing the rule 'Activity Embed-Decision-SPContainer . pyRefreshSPList', and this has been added.

SR-122902 · Issue 182835

Shutdown issue with Tomcat resolved

Resolved in Pega Version 7.1.8

During shutdown, errors were reported on the App Server window. Shutdown did not complete and the App Server Window remained open. This was due to the "Shutdown" button/feature not properly terminating Tomcat. There was a workaround to manually close the Tomcat window, but the DNodeServiceListener has been modified to release all of the threads properly.

SR-123031 · Issue 182673

Corrected inheritance logic for ComputeSegment

Resolved in Pega Version 7.1.8

ComputeSegmentLogic activity logic was not considering inheritance path. This was an issue with having the run-time rule resolution at design-time, and has been changed to pass propagate the apply-to class to sub-activity calls so that it can pick up the right rule.

SR-123968 · Issue 194580

Added special character handling to Process Modeler

Resolved in Pega Version 7.1.8

After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.

SR-123968 · Issue 194306

Added special character handling to Process Modeler

Resolved in Pega Version 7.1.8

After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.

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