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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B15663 · Issue 289919

Trend chart drilldown made consistent with chart display

Resolved in Pega Version 7.3

Trend chart drilldown did not match chart display due to issues with time zone being converted on the chart display but not on the the drilldown. When drilling down into a datetime group, the value of that group was used to create a single filter that matched the group (e.g., "Day of [.DateTime] = 20170101"). This caused the filter to match that time based on the server's time zone settings, not the user's (e.g., if the server was using GMT, then days always began at midnight GMT, so a user could drill down into a single day and get results spanning two days). To correct this, FusionChartDataGeneration.normalizeDateCal no longer localizes for the user's time zone if the time unit is larger than an hour, e.g. day or month units won't be normalized.

SR-B15673 · Issue 288077

DatePicker calendar pop works as expected

Resolved in Pega Version 7.3

Unexpected behavior was seen where the input box of a date control used as Date+calendar popped up the calendar on click when Text entry was not allowed and did not pop up the calendar when Text entry was allowed (both in disabled mode). This was traced to an error in the data-ctl attribute for that span, and has been fixed.

SR-B15673 · Issue 288076

DatePicker calendar pop works as expected

Resolved in Pega Version 7.3

Unexpected behavior was seen where the input box of a date control used as Date+calendar popped up the calendar on click when Text entry was not allowed and did not pop up the calendar when Text entry was allowed (both in disabled mode). This was traced to an error in the data-ctl attribute for that span, and has been fixed.

SR-B15790 · Issue 285997

Handling added for dot in visible-when rule

Resolved in Pega Version 7.3

On click of the icon next to the visible-when rule in order to open the rule, the error "Unable to open the rule as Base Class Value is empty" was generated if the 'when' rule of the conditions included a dot. To correct this, the pega_openRuleSP logic has been modified to fall back to the section class from the PRXML when the value of baseClassValue is empty.

SR-B15831 · Issue 286160

Fixed enter actions for grid layout in overlay

Resolved in Pega Version 7.3

Enter Actions were not working properly on a Grid layout in Overlay. To correct this, a Keyup check has been added for grid keypress events in the GenerateControlAction RUF.

SR-B15831 · Issue 304223

Fixed enter actions for grid layout in overlay

Resolved in Pega Version 7.3

Enter Actions were not working properly on a Grid layout in Overlay. To correct this, a Keyup check has been added for grid keypress events in the GenerateControlAction RUF.

SR-B15831 · Issue 283045

Fixed enter actions for grid layout in overlay

Resolved in Pega Version 7.3

Enter Actions were not working properly on a Grid layout in Overlay. To correct this, a Keyup check has been added for grid keypress events in the GenerateControlAction RUF.

SR-B15858 · Issue 286667

Fixed Right align of header in repeating grid

Resolved in Pega Version 7.3

When a Repeating grid was included in a section and the header used apply alignment as Right, the results did not display as expected. This was due to missing styles corresponding to Header Label Align class, which have now been added.

SR-B15884 · Issue 288287

Page level error display honors KeepPageMessages value

Resolved in Pega Version 7.3

Page level error messages on the perform harness were flickering when a flow action was submitted. This was caused by the message only displaying for half a second, and has been corrected by correctly honoring the "pega.u.d.KeepPageMessages" value.

SR-B16230 · Issue 287871

Dollar sign character will be escaped if present in data page value

Resolved in Pega Version 7.3

If a section was configured to show the data with a data page as source, using the dollar sign in the value caused the amount to not be displayed correctly in the grid. This has been corrected by adding code to escape the $ character when it's present in the data.

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