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-117844 · Issue 170991

Auto-refresh only available for Section Tabs

Resolved in Pega Version 7.1.7

When the "Refresh when active" checkbox was checked in a harness used in the Case Manager dashboard, creating or closing a WO did not update this page automatically. This is because auto-refresh is unsupported in the harness; it is better to use Section Tabs (the best practice statement explains why) and they are encouraged over using Harness tabs. In order to make this use clear, the auto-refresh checkbox will not be displayed in harness tabs.

SR-118016 · Issue 174520

Spellcheck on text area fixed for IE8

Resolved in Pega Version 7.1.7

Using IE8, a text area with SpellCheck enabled generates the error "Script Error: Message: 'null' is null or not an object" if there is more than one line present. This was caused by the handling of the check for list length, and has been modified to work with all browsers.

SR-118053 · Issue 172515

Added edit format for Designer Studio integer control in read-only when

Resolved in Pega Version 7.1.7

In the Integer Control for Designer Studio, it is not possible to set properties on the Edit Format when the presentation is ReadOnly based on a when rule. Both the Formats appear when the Edit Options is selected as Auto. Options have now been added to set the properties.

SR-118081 · Issue 169902

Focus correctly set for dynamic select using accessibility

Resolved in Pega Version 7.1.7

When using a cascading dynamic select control configuration with the PegaWAI accessibility ruleset, setting the focus of the first DS list did not work when attempting to navigate the UI components via the keyboard. When reaching the first DS control, users could only select the next item in the list and then the focus switched to the second DS list immediately. The DynamicSelect control was missing a name attribute, and has been updated to address the focus issue.

SR-118106 · Issue 174462

Improved accessibility for UI properties

Resolved in Pega Version 7.1.7

When a property is put on the UI from a different Page the generated UI was not setting the correct LabelFor - it striped the Page context but didn't strip the dot from the front of the property. Accessibility JAWS and other assistive technologies were therefore not associating the label with the input and did not read it out for the given input. The label generation function has been changed to address the reported issue.

SR-118111 · Issue 175580

Drop-down focus modified for accessibility

Resolved in Pega Version 7.1.7

When an onChange event is set on a dropdown (select) while using the accessibility framework, the focus automatically shifted onto the next element in the UI. This was not the desired behavior, and the system has been modified.

SR-118159 · Issue 174990

Improved handling for Case notes when spellchecker is active

Resolved in Pega Version 7.1.7

If a lot of content was added for a case Note, clicking on the Notes tab caused the text to display in a big yellow box which could not be dismissed. This was traced to the spell checker not properly handling RTE's hidden textarea field, and the code has been modified to correct this.

SR-118194 · Issue 170594

Declarative refresh now working for IE

Resolved in Pega Version 7.1.7

When using IE, property changes on the clipboard did not trigger a declarative refresh. This was traced to a duplicate refresh section list that was not getting cleared properly with addition of cross thread change tracking, and has been corrected.

SR-118307 · Issue 172330

Integers with embedded spaces now prompt screen edit during validation

Resolved in Pega Version 7.1.7

If an Integer property was populated with a number with spaces ("12345 67890"), it generated the validation error "** PropertyValueInvalid null .pegaToInteger() Invalid number format (was 12345 67890)". A numeric value with embedded spaces will fail during conversion to Integer, but this will now be caught with a screen edit in the same way a non-numeric character would be during screen validation.

SR-118675 · Issue 172991

Corrected duplicated validation errors

Resolved in Pega Version 7.1.7

In some cases, validation error messages were being duplicated in the display. This was traced to code in the dynamic display being executed twice, and 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