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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-118884 · Issue 172536

Create Work correctly encodes Japanese characters

Resolved in Pega Version 7.1.7

When Japanese characters are passed as parameter to Create Work action, the newly created work item was registering cryptic characters instead of the expected Japanese characters. This was traced to a deprecated API, and has been corrected.

SR-118929 · Issue 177444

Fixed CPM alerts popup for Internet Explorer 8

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

The CPM messages and Alerts screen was not displaying correctly in Internet Explorer 8, and the selecting the 'Show All Workgroups?' checkbox did not show the workgroups on the 'Create a new alert message' popup window.This was caused by the z-index of chart legend being higher than the modal dialog, and has been fixed.

SR-118956 · Issue 175342

Smoothed error handling for searching in listview gadgets

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

When using a gadget with a listview that includes a header and has "Display data in a frameset" under the Format tab checked, a sporadic "Missing Property .pyStreamName" error appeared when performing a search. This was traced to a timing issue with multiple clicks that caused some pages to be cleared once the report has been run. To correct this, whenever the stream name is empty, an error message to resubmit the request will be displayed to the user instead of an exception.

SR-118970 · Issue 176298

Corrected error flag location in layout with hidden tabs

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

When working with a harness using tabgroups layout with multiple tabs where each tab contains sections with properties that are associated to validation rules, when validation failed the red cross error icon appeared on the wrong tab. This issue only occurred when there was a hidden tab in-between. This was caused by missing logic for handling the hidden tabs scenario, and has been fixed.

SR-119030 · Issue 172922

Clipboard privileges tightened to enhance security

Resolved in Pega Version 7.1.7

Using standard browser development tools, it was possible to insert a client-side modification into a Pega-served HTML page to allow a customer to access partial clipboard inspection functionality. To correct this, starting activity privileges have been tightened.

SR-119036 · Issue 176992

Flow rule form header fixed for Google Chrome

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

When using Google Chrome, the background flow rule form header was dragged upwards and became invisible when any shape property dialog box was scrolled down to specifications tab. No scroll bar was presented to scroll the flow rule form back to the original position, resulting in inaccessibility of the header of the flow rule. This was caused by the presence of hidden iframes that were not properly handled by the display, and has been fixed.

SR-119055 · Issue 174515

Corrected drop-down onchange event firing for accessibility mode

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

If a select button was associated to a DynamicSelect control in a Cascading Dynamic Select configuration with WAI, at runtime, the child DynamicSelect list was auto loaded once the value on the parent DynamicSelect list was changed. In accessibility cases, the select button was introduced to be beside the drop down to set the value selected from the drop down. However, in cascading dynamic select, selecting the value from first drop down caused the values in the second drop down to load because an onchange event was fired. In order to handle this correctly, pega_ui_dynamicselect js has been updated to not fire upon change event when in accessibility mode, but instead fire upon click of the select button.

SR-119074 · Issue 175337

Calendar Control accessibility enhanced

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

In accessibility mode, the Calendar Control defaulted to the current year +/- 10 years. This did not allow dates for lifetimes or for long-term activity dates. In order to improve functionality, the dynamic system setting 'pyNumberofYears' has been inserted to allow modification of the datetime cell properties as desired.

SR-119074 · Issue 176791

Calendar Control accessibility enhanced

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

In accessibility mode, the Calendar Control defaulted to the current year +/- 10 years. This did not allow dates for lifetimes or for long-term activity dates. In order to improve functionality, the dynamic system setting 'pyNumberofYears' has been inserted to allow modification of the datetime cell properties as desired.

SR-119095 · Issue 174195

TagCloud rendering corrected

Resolved in Pega Version 7.1.7

When opening pxTagCloudViewGadget it generated the error: 'Unable to open an instance using the given inputs: pxObjClass = "Rule-Obj-Report-Definition", pyClassName = "", pyStreamName = ""' . The tag cloud gadget reported "Can not render @baseclass.pxTagCloudInit", and when run or included in a section, it did not render any tags. This was found to be a design time error in Obj-Open of the report definition, and has been fixed.

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