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-115798 · Issue 167885

Improved handling for abstract case classes

Resolved in Pega Version 7.1.7

An extra hyphen was being inserted into a newly created case's class when the parent class was an abstract class already indicated by '-'. To correct this, a check has been added to avoid appending a dash if the parent class name ends with "-".

SR-115808 · Issue 169924

Instantiation logic enhanced

Resolved in Pega Version 7.1.7

In an application with a parent case (CaseInstancePOC) and two lower levels of cases (Case_Level2 and Case_Level3), the top level case starter flow CaseInstancePOC creates multiple subcase instances of type Case_level2. This is caused by automatic case instantiation of Case Level3 based on Case level2 Work Status - Open being configured. In some cases, this may not be the desired behavior. For example, when there are two Case_Level2s and one work status is changed to Open, the user may want a child case to be instantiated for only that particular Case_Level2and not the other Case_Level2. To allow more flexibility, an enhancement has been added to limit scoping through the AddChildWork setting.

SR-115912 · Issue 168208

Updated failure handling for Word editing with IE

Resolved in Pega Version 7.1.7

When using IE, failure to load correspondence for editing in Word generated the message "Error: Loading Open Authoring Control". This was caused by the carried-over use of a span tag that is not valid under HTML5, and has been corrected with updated JavaScript.

SR-115934 · Issue 170092

Corrected deadline escalation for reassigned work

Resolved in Pega Version 7.1.7

When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.

SR-115934 · Issue 170387

Corrected deadline escalation for reassigned work

Resolved in Pega Version 7.1.7

When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.

SR-115934 · Issue 174331

Corrected deadline escalation for reassigned work

Resolved in Pega Version 7.1.7

When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.

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-116220 · Issue 168848

Report drill downs for embedded summary charts open in a new window

Resolved in Pega Version 7.1.7

If a Summary View chart has a drill down to another summary view and then to a list view, when the section is launched, clicking on the pie of a summary chart in the portal gets drilled down to the next level. However, when the chart was maximized (opened in a pop up), it was not drilling down. This was traced to the way actions were configured: when reports were maximized, the main window was set to the parent window and drilling down refreshed the main window and not the maximized window. To remedy this, report drill downs now open in a new window instead of modifying the parent window.

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-116300 · Issue 167205

Added display expansion capabilities for accessibility mode

Resolved in Pega Version 7.1.7

Previously, expanding displays with "+" in the listview category headers required a mouse click. An enhancement has been added to additionally allow use of the enter key at this location to expand and display the attachments of that category type (Notes, Files, Emails, etc.).

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