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-D36091 · Issue 505613

Harness context will be stored to handle on click executed outside of the Ajax Container

Resolved in Pega Version 8.2.4

An exception was generated in the interaction portal on execution of a post-value action for the on-change event on a text-box in the service case: "Failed to find instance Work-Interaction-Research.EmailBodyRTE of type Rule-HTML-Section". This was traced to a condition where clicking outside of the Ajax Container context to trigger the change caused the Events code to execute the event in the active context when the active context had already been changed by clicking outside of the AC. To avoid this, the system will store the harness context in the event object using pega.ctxmgr.getContextByTarget(target) API.

SR-D23174 · Issue 499568

Check logic added for change in datetime

Resolved in Pega Version 8.2.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-D36970 · Issue 504985

Calendar icon updated to properly display the set number of years

Resolved in Pega Version 8.2.4

By default, the Calendar icon showed a date range of 10 years when -/+100 was expected. This issue was traced to the existing DSS setting (pyNumberofYears under Pega-UIEngine), which enables overriding the date year range, not being honored when the pyNoOfYears property was set to -1. To honor the pyNumberofYears setting, pyNoOfYears should be 21. This has been corrected so the value will be set properly.

SR-D37290 · Issue 506284

Null check added to ensure value "yyyyMMdd" displays correctly in DateTime Input

Resolved in Pega Version 8.2.4

An issue where the input value "yyyyMMdd" was not displayed correctly in a DateTime input field was traced to moment.calendar returning invalid formatting when executed on a null property. To resolve this, a check has been added to assess whether the datetimeframe has any properties or not.

SR-D30944 · Issue 503232

Corrected pagination alignment in tabbed layout sourced from RD

Resolved in Pega Version 8.2.4

Pagination numbers were not being presented inline with the next/back arrows when using a tabbed table layout with source:report definition. To resolve this, the pyGridPaginator function has been added to Pega-Gadgets in Work- .

SR-D31599 · Issue 503198

Table layout filter by format works for empty value

Resolved in Pega Version 8.2.4

If a DateTime property with empty values in a table layout grid was filtered by format, no result was returned even though the grid had the Records for empty DateTime property. This was traced to null value filtering being done with empty values instead of a formatted null value, a difference that could produce different results depending on the control. To resolve this, the activity has been updated to support null values filtering.

SR-D30428 · Issue 503423

Added handling for deprecated UI Kit in Pulse OpenURLInWindow

Resolved in Pega Version 8.2.4

After upgrade, clicking on a link in a Pulse comment opened a new window with an error message indicating no content was returned. Investigation showed that if an older deprecated version of the UI kit was used, 'Open URL in window' was configured as Run Script function. The more recent versions use an OpenURLInWindow action. To resolve this, the script has been updated to use an action and pass the correct parameters.

SR-D36120 · Issue 506242

Escape added to Radio button field value to handle HTML tags

Resolved in Pega Version 8.2.4

A radio button with a field label to display a help icon and to open the help URL when the icon was clicked did not display as intended. Changing the control to text area produced the desired results. This was traced to the radio button's label being assigned to a field value which returned a string that at some points contained HTML tags, and has been resolved by escaping the pyLabelFor value before assigning it to the aria-label attribute of the radio button's div tag.

SR-D29809 · Issue 505256

Extra <p> tag removed when not needed in RTE generation

Resolved in Pega Version 8.2.4

The RTE was generating an extra <p> tag in the Review harness or when the RTE was non-editable, causing alignment issues in the UI when RTE was displayed using inline dynamic layout with a textarea. This has been corrected.

SR-D31702 · Issue 505056

Added constraints to RTE resize

Resolved in Pega Version 8.2.4

When using Microsoft Internet Explorer 11 with a column layout with main (using RTE) and a side bar (with a text input), dragging the RTE box towards the right side from the bottom right hand corner caused it to expand and overwrite the contents of the side bar. This occurred irrespective of whether the column layout was placed in a dynamic layout or standalone. Investigation found that this was caused by there not being any restriction on the resize of RTE, which allowed it to expand beyond limit. This 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