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-117877 · Issue 178627

Report on implementation classes corrected for descendant class

Resolved in Pega Version 7.1.8

Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.

SR-117877 · Issue 175972

Report on implementation classes corrected for descendant class

Resolved in Pega Version 7.1.8

Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.

SR-118224 · Issue 182305

Report Definition "Pick Value" list resolves to correct layer

Resolved in Pega Version 7.1.8

When a report definition in the framework layer has "Report on descendant class instances" checked, running the report from the implementation layer should retrieve pick list values for "Available Values" on filter popup from the implementation layer. Instead, it was getting the values from the framework layer. This was caused by the code that generates the SQL query to populate the "Pick Value" list resolving to the wrong work class name, using the framework layer work class rather than the implementation layer work class. There was a workaround of performing a 'Save As' of the affected reports to each implementation layer, but this has been fixed.

SR-118224 · Issue 182203

Report Definition "Pick Value" list resolves to correct layer

Resolved in Pega Version 7.1.8

When a report definition in the framework layer has "Report on descendant class instances" checked, running the report from the implementation layer should retrieve pick list values for "Available Values" on filter popup from the implementation layer. Instead, it was getting the values from the framework layer. This was caused by the code that generates the SQL query to populate the "Pick Value" list resolving to the wrong work class name, using the framework layer work class rather than the implementation layer work class. There was a workaround of performing a 'Save As' of the affected reports to each implementation layer, but this has been fixed.

SR-119715 · Issue 178060

Corrected Microsoft Internet Explorer horizontal scroll bar access within large list views

Resolved in Pega Version 7.1.8

If the data present in the list view is huge (2000+ characters), selecting the filter option caused the horizontal scrollbar to not be visible in Internet Explorer. As a result, the apply button was not accessible. This was caused by a lack of overflow settings to handle the excessive width for that browser, and has been fixed.

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-120324 · Issue 179256

Corrected DateTime controls in GroupBy

Resolved in Pega Version 7.1.8

Specifying any of the DateTime-* controls (e.g., DateTime-Short) in the Format field of the Group By property in a summary view was not working with the out-of-the-box settings; the DateTime property would be displayed in DateTime (GMT) format. This was found to be a field name hard coded to a value with a data type of text, causing the selected control to be ineffective, and has been changed.

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.

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