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-D22219 · Issue 491446

Dropdown UI CSS corrected

Resolved in Pega Version 8.4

An issue with incorrect generation of the Dropdown UI CSS has been resolved by directing the Preflight Crawler to the field holding the CSS Format.

SR-D22225 · Issue 504357

Added handling for iPad special characters in any key event

Resolved in Pega Version 8.4

When using an iPAD, there were 5 characters that were not caught when typed by the anykey event on a text control that was supposed to take only numeric data. The control worked as expected on iPhone. Investigation showed that the Keycode is 0 in the event object for some special characters with the iPad, and this has been resolved by using key instead of depending on keycode for those special characters.

SR-D2272 · Issue 486163

RDL updated to ensure unique ID generation

Resolved in Pega Version 8.4

An Android hybrid mobile app was showing data on the UI which did not match with the data available in pyWorkPage. This was traced to the use of timestamps for ID generation, and has been resolved by updating RepeatingDynamicLayoutAssembly Java to ensure unique ID generation.

SR-D23036 · Issue 500574

XSS protection added to paragraph rules

Resolved in Pega Version 8.4

XSS filtering has been added for property references in paragraph rules.

SR-D23174 · Issue 499570

Check logic added for change in datetime

Resolved in Pega Version 8.4

After selecting a valid date in the calendar UI, clicking outside of the DateTime control caused the date to disappear when using the Microsoft Internet Explorer browser. Investigation showed that the order of events execution is different in Microsoft Internet Explorer and Google Chrome, so that by the time the getReadOnlyFormatting method was called, the data-changed attribute had already been updated to 'false'. This caused the read-only formatting to not be applied so the data-display-value was considered to be empty. To resolve this, a check has been added to better detect the change so that read-only formatting gets applied.

SR-D23340 · Issue 497608

Calendar begins with Saturday in the Arabic locale

Resolved in Pega Version 8.4

When using the Arabic locale, the week was not starting on Saturday as expected, but was showing Thursday as the first day. This has been corrected.

SR-D23417 · Issue 493544

Image Attachment File Type error localized

Resolved in Pega Version 8.4

Localization has been added to the error message generated when an unsupported image is uploaded while in live-chat.

SR-D24083 · Issue 498489

Guardrail warning removed for setting filter by format on RD sourced grid

Resolved in Pega Version 8.4

After upgrade, use of the 'filter by format' (Configuration on table layout column) for grids sourced with report definition caused confusion in that the option now exists to either to see the value or the formatted value in the filter panel. Previously, a grid layout would show a date format in both the column of a grid and the filter of that column, but the filter changes produced a date format on the column within the grid but the date time format applied on filter of the column. This behavior change will be reflected in updated documentation. In addition, there is a workaround to recreate the old behavior by changing the column 'Date assigned' from a filter by value to format, but a moderate guardrail warning was created when filter by format was set on any column of a grid sourced to a report definition. This has been removed: when filter by format is selected, no guardrail warning will be displayed in design time.

SR-D24318 · Issue 494060

Dom API updated to resolve Microsoft Internet Explorer 11 not loading async data with refresh when calling an activity

Resolved in Pega Version 8.4

The browser was continuously showing "loading" if Microsoft Internet Explorer 11 was used for a section which was sourced from a data page and configured to load the data asynchronously from a external service while calling an activity and using a 'refresh when' rule to refresh the section if a property changed. Investigation showed that the initial data load was successful and the section with the data was visible, but if the property changed and the section loaded once again due to the 'refresh when' condition, the browser was unable to render the defer loaded section case because the dom returned had the wrong value. To resolve this, the API used to check for the dom element has been updated.

SR-D24682 · Issue 501080

Added check for undefined targetTD in repeating tab layout

Resolved in Pega Version 8.4

Given a repeating tab layout and a validation on the flow action which used edit validate, clicking on the next button set an error on the page. Putting in the correct data and clicking the next/submit button a second time resulted in a console error indicating the targetTD was undefined for the markSectionTabErrors function in pzpega_ui_doc_tabsupport. This has been resolved by adding a check for the undefined targetTD.

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