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-120654 · Issue 179938

Made busy indicator location consistent in SFA portal

Resolved in Pega Version 7.1.8

The 'loading' icon (aka "Throbber") was not being displayed in a consistent location in the SFA Portal. This was traced to the busy indicator being registered in reference to the workarea gadget, causing the busy indicator to appear in an unexpected place if the gadget was hidden. This has been corrected by showing the indicator directly on the portal window.

SR-120780 · Issue 178357

Corrected text input focus highlighting for accessibility

Resolved in Pega Version 7.1.8

When using an accessible application, the fields with pxTextInput control were not highlighted on focus. This has been corrected.

SR-120781 · Issue 177810

Changed close modal icon text for JAWS

Resolved in Pega Version 7.1.8

If focus is given to the X icon on the modal dialog, JAWS was reading "Unlabeled 2 Button." In order to indicate that it is the Close modal icon, the title="close modal" has been added to the modal dialog's X button.

SR-120876 · Issue 185865

Required date properties now working correctly in modal windows

Resolved in Pega Version 7.1.8

Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.

SR-120876 · Issue 183543

Required date properties now working correctly in modal windows

Resolved in Pega Version 7.1.8

Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.

SR-120946 · Issue 180460

Ensured custom formats for dynamic layouts appear consistently

Resolved in Pega Version 7.1.8

Custom formats for Dynamic Layouts in an application skin were not appearing after upgrade. This was caused by stale code related to alignment issues, and has been resolved.

SR-121048 · Issue 192690

Corrected dynamic select refresh behavior

Resolved in Pega Version 7.1.8

When a Dynamic select with "OnChange + refresh" was configured, the values in dynamic selects were not retained after a refresh in the Google Chrome and Firefox browsers. This occurred most often when selecting a value for a second dynamic select box caused a refresh and forced the previously selected value to be lost from the first box. The values were reset to "Select.." and the drop values were also not populated. The root cause of this problem was trailing white spaces in the values returned by the service that populated the dynamic select. While Microsoft Internet Explorer automatically trimmed these spaces, Google Chrome and Firefox did not. This has been corrected by trimming results when getting data from xml in the DynamicSelect JavaScript file.

SR-121105 · Issue 180175

Corrected text wrapping for attached notes

Resolved in Pega Version 7.1.8

When using out-of-the-box functionality for attaching a note, the text was not wrapped and showed in one long line. The root cause of this problem was the "pre" tag in the HTML not breaking the lines and not wrapping, and styles have been added to fix the attachment issue.

SR-121475 · Issue 188297

Row repeat behavior smoothed for HTML5

Resolved in Pega Version 7.1.8

After migrating, row repeat was expanding the width of all the cells each time the section was refreshed even if the width was selected as pixel (fit to content). Selecting "include HTML5 document type" option at the application level prevents the issue, but this issue has been addressed with the "Align Column With Data" Check box available on header cell.

SR-121535 · Issue 188591

Autocomplete response tuned to resolve latency

Resolved in Pega Version 7.1.8

When the autocomplete list was displayed, a delay was seen between the focus highlight and the mouse pointer when using Google Chrome or Microsoft Internet Explorer 11. The highlight style is applied using CSS hover selector and the style is applied by the browser, so any delay is dependent on overall performance of the application in the browser, however the system has been optimized for performance and some memory leaks were tightened, and the overall application should display a noticeable improvement in response time.

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