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.

INC-136057 · Issue 587164

Modal dialog close for date/time works as expected

Resolved in Pega Version 8.5.1

When a date/time property was used in a modal screenflow in Google Chrome, changing the date property on the pop up calendar and then clicking the modal close caused the screen to freeze. This was caused by the plf.handleModalClose() being called a second time for a container close event that was not available in window.event. This has been resolved.

INC-137276 · Issue 585298

Arrow key navigation updates for layout grid tabs

Resolved in Pega Version 8.5.1

When a layout grid was configured as Tab mode, the up and down arrows allowed navigation between tabs. This has been modified to meet W3 standards of using left/right arrow keys to navigate between tabs and up/down arrow keys to scroll the page.

INC-128805 · Issue 579164

Timing corrected for modal dialog window height

Resolved in Pega Version 8.5.1

When creating a modal dialog with text area inputs, the height style attribute of the text areas appeared to use the width of the previous modal dialog window. If a small modal dialog was opened and then a large one, the text areas in the latter were oversized. Creating the same dialog twice caused the text areas to return to the intended size. This was traced to a timing issue with updating the modal dialog height, and has been resolved by adding a delay of 300ms to ensure the window height is updated properly.

INC-129984 · Issue 584552

Templated Sections render on first open when no height given

Resolved in Pega Version 8.5.1

When opening a section rule based on a template (like pyCaseMainInner), the contents did not load on first open. A browser refresh and/or rule refresh caused the contents in the section to appear. This was traced to a logic skip introduced as a resolution for the live preview being jumpy when changing between tabs, which did not take into account the initial load of the preview when it has no height. To resolve this, an update has been made to triggerReflow in the pzpega_ui_dynamiccontainer js to use an 'or' condition for resetting the height if live preview is not being used.

INC-133944 · Issue 586016

Future DateTime Property picks operator timezone

Resolved in Pega Version 8.5.1

When selecting the DateTime in a property field configured to accept future data input, the input failed validation due to the DateTime field being compared with the System time zone (IST instead of the operator time zone. This has been resolved by adding a condition to honor the operator timezone in isFutureDate validation, and to fall back to the browser timezone if necessary.

INC-134634 · Issue 584946

FSM Mobile app correctly starts phone call after closing Google

Resolved in Pega Version 8.5.1

When two controls were configured in the FSM Mobile app, one for Get Directions and one to handle a phone call, clicking on the phone call control worked correctly when it was used first, but clicking on the Get Directions control and opening and closing Google Maps before clicking on the Phone call control caused the phone call control to not work. Investigation showed that after the Get Directions control was used, the # in the href attribute was automatically prepended with window.location. To resolve this, a check has been added that will compare the attribute with the completely formed {URL}# so that entire window.location will not be prepended.

INC-125341 · Issue 560436

JAWS reads the remaining character count in text input area

Resolved in Pega Version 8.5.1

When using a JAWS reader with a textarea control, the remaining character count was not being read out as expected as text was added. This has been resolved by updating the textarea tag to add an aria-describedby charcount attribute.

INC-131523 · Issue 573851

Parameters to Property UI Field available in report

Resolved in Pega Version 8.5.1

When using a parameterized control like Decimal for a property in the UI control of the Property rule with inputs given to the parameters, once the property was optimized and referred to in Report Definition, the value was rendered using the Control with parameters defined in its rule form. In the report, the column was not rendered as it is designed on the property rule, but the same worked as expected in a section. This behavior was a change after upgrade. This was traced to "pyPropertyName" being added to the stepPage as part of the pzMergeAutoGenForProp Activity, and has been resolved by adding it to the stepPage only when it is an auto-generated control.

INC-133637 · Issue 581342

Refresh handling added for cancel 'add item' while offline

Resolved in Pega Version 8.5.1

When using iPad and iPhone offline, filling in one required field, hitting submit (click action: 'Add item') without filling in a second required field, and then hitting cancel resulted in a blank record being added. Clicking the cancel button first without clicking submit before did not add the item. This was traced to the underlying repeating dynamic layer being refreshed during the submit and adding the record, and has been resolved by adding a refresh for the cancel button process as well.

INC-129848 · Issue 580459

Refresh handling added for cancel 'add item' while offline

Resolved in Pega Version 8.5.1

When using iPad and iPhone offline, filling in one required field, hitting submit (click action: 'Add item') without filling in a second required field, and then hitting cancel resulted in a blank record being added. Clicking the cancel button first without clicking submit before did not add the item. This was traced to the underlying repeating dynamic layer being refreshed during the submit and adding the record, and has been resolved by adding a refresh for the cancel button process as well.

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