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-116153 · Issue 165729

CaseTypeValues correctly created for child cases

Resolved in Pega Version 7.1.7

CaseTypeValues were not being properly set on the child case when it was added to the cover through agent creation, causing the trigger not to execute because the change was not detected. Manual creation was detected properly. This inconsistency was traced to the agent using the AddToCover activity vs. the manual creation using AddChildWork, and has been corrected.

SR-116242 · Issue 171896

Work item correspondence loading fixed for IE11 Enterprise

Resolved in Pega Version 7.1.7

When trying to view correspondence attached to a work item, using IE11 in Enterprise mode, an error "Error: Loading Open Authoring Control" is generated. This was caused by the Open Authoring ActiveX control APIs used by the correspondence viewing functionality: the currently used method of verifying that an ActiveX control has been successfully loaded into the HTML page was not working in IE11 Enterprise mode, and has been updated.

SR-116347 · Issue 166799

Error resolved for adding Stage Step Specifications using RTE and Google Chrome

Resolved in Pega Version 7.1.7

While configuring a stage behavior in Google Chrome, if a user had focus within the Rich Text Editor for a specification and submitted the modal, an error was generated. This was caused by an invalid post-value check, and the unnecessary post value has been removed.

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-116587 · Issue 170222

Clarified default values for Create Class

Resolved in Pega Version 7.1.7

The Create Class screen was offering default values that had the potential to lead to classes being created in an incorrect / invalid part of the Class Structure. This has been corrected.

SR-116661 · Issue 169635

TrackSecurityChanges enhanced to capture index information

Resolved in Pega Version 7.1.7

While the properties of a pagelist are displayed in the TrackSecurityChanges history tab, the corresponding index of what was changed on the page list was not included. In order to more accurately track what is being changed, an enhancement was added with new field values for tracking the index history.

SR-116769 · Issue 174513

Case narrative ordering enhanced

Resolved in Pega Version 7.1.7

The Case Narrative ordering appeared incorrectly when the events are very close together (multiple events within the same second), though the History items displayed in the correct and expected order. When more than one event occurred within the same second, the DATE datatype did not provide a lower level of distinction to allow more granular sorting or ordering. To resolve this, the time value for sorting is now extracted from InsKey.

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-116893 · Issue 169075

Corrected browser display errors for large decision tables

Resolved in Pega Version 7.1.7

A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.

SR-117937 · Issue 173922

Corrected browser display errors for large decision tables

Resolved in Pega Version 7.1.7

A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.

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