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-B13785 · Issue 278965

Added tenant ID check for batch thread in MT environment

Resolved in Pega Version 7.3

When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.

SR-B15497 · Issue 286469

Styling corrected for last row in tree grid sourced from RD

Resolved in Pega Version 7.3

Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.

SR-B15497 · Issue 295707

Styling corrected for last row in tree grid sourced from RD

Resolved in Pega Version 7.3

Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.

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-B15685 · Issue 292401

Flexibility enhancement for mobile dropdown displays

Resolved in Pega Version 7.3

As a part of an enhancement for mobile apps, a checkbox for "Allow scrolling for more results" has been introduced in the property panel of the Autocomplete. By default its value will be unchecked, implying the old behavior which limits the "Dropdown" options on autocomplete to 8 for backward compatibility. If the checkbox is used, it will honor the "Max results displayed" setting used for list based autocomplete. If the max results value is not specified, using the checkbox will cause the dropdown to show all the results.

SR-B15880 · Issue 289450

Enable/disable of "+" icon in mobile app fixed

Resolved in Pega Version 7.3

The enabling and disabling of the "+" icon was not happening in the Mobile Hybrid app even when disabling condition were met. This has been fixed.

SR-B1734 · Issue 272443

Added content to blank headers for screen readers

Resolved in Pega Version 7.3

The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.

SR-B1734 · Issue 272039

Added content to blank headers for screen readers

Resolved in Pega Version 7.3

The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.

SR-B2863 · Issue 275455

Improved offline decision shape handling for GoToPreviousTask

Resolved in Pega Version 7.3

The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.

SR-B2863 · Issue 275455

Improved offline decision shape handling for GoToPreviousTask

Resolved in Pega Version 7.3

The skipFlow condition in handleNotAFlowAndNotDisplayableShape function in the pzpega_process_engine rules has been updated to better handle offline use of customized GoToPreviousTask decision shapes.

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