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-117230 · Issue 172209

JAWS no longer reads out table structures

Resolved in Pega Version 7.1.7

When JAWS encountered tables, it considered them to be data tables if there were no aria labels or roles defined on it and proceeded to read out the table structure to the user. If one of the td had ' ' it read out as blank. Table tags being generated for layouts are now given a "role" attribute as "presentation" for accessibility compliance: this will mark the table structure not to be read out by JAWS. In addition, JAWS will read out any html associated to the input rather than the aria-label format information.

SR-116648 · Issue 170323

Form level messages retained by parameter for Tree layout

Resolved in Pega Version 7.1.7

Error messages were not retained when "Select On Load" option was selected for the Tree control. By request, an enhancement has been added through the parameter pega.u.d.KeepMessages, and the clearing of page messages will be done depending on this parameter, both in client and server.

SR-116661 · Issue 169635

TrackSecurityChanges enhanced to capture index information

Resolved in Pega Version 7.1.7

While the properties of a pagelist are displayed in the TrackSecurityChanges history tab, the corresponding index of what was changed on the page list was not included. In order to more accurately track what is being changed, an enhancement was added with new field values for tracking the index history.

SR-116679 · Issue 169078

"Save preferences" button visibility corrected

Resolved in Pega Version 7.1.7

The ability to save report filtering preferences for Summary View was only appearing if the report included an interactive chart. The system has been updated to present the 'Save Preferences' button in all report types.

SR-116681 · Issue 169378

BIX Column length increased

Resolved in Pega Version 7.1.7

At runtime BIX checks the target DB metadata for column length. If it could not find the metadata with schema associated with the BIX DB user, it was setting the length at 32 characters even if a larger column length was specified in PRPC and SQL. This was due to a mismatch in the stored value location, and has been corrected so BIX will reflect the length specified on the Extract rule form.

SR-116716 · Issue 167507

Execute RDB runs in batch mode for very large data sets

Resolved in Pega Version 7.1.7

The executeRDB query was not able to handle very large large data sets, resulting in an OOM error after clicking on "Create Prior Authorization". ExecuteRDB (which is a select query) has been modified to run in batched mode, i.e. run the same query with limit on max rows, so as to avoid OOM when copying the whole result set into the memory object (similar to Report Definition paging).

SR-116719 · Issue 167427

Added handling for SOAP elements with empty case types

Resolved in Pega Version 7.1.7

If customers created a SOAP element with an attribute like Text, the generated WSDL from services wizard did not have a type for the element "CaseStatus" and failed validation with the error "Element 'CaseStatus' with empty content type cannot have text or element content." The XML has been updated to correctly handle this use case.

SR-116761 · Issue 169833

FormatNumber use clarified

Resolved in Pega Version 7.1.7

Attempting to use the "pxFormatNumber" function in an activity step generated the error message "com.pega.pegarules.session.internal.mgmt.Executable cannot be cast to com.pega.pegarules.pub.runtime.StreamBuilderToolKit". Formatter RUF were not intended to be called directly from activities, but RUF has been enhanced to work with reduced functionality in case it is called from activity. The documentation has also been updated to reflect preferred usage.

SR-116769 · Issue 174513

Case narrative ordering enhanced

Resolved in Pega Version 7.1.7

The Case Narrative ordering appeared incorrectly when the events are very close together (multiple events within the same second), though the History items displayed in the correct and expected order. When more than one event occurred within the same second, the DATE datatype did not provide a lower level of distinction to allow more granular sorting or ordering. To resolve this, the time value for sorting is now extracted from InsKey.

SR-116778 · Issue 168295

JavaScript error resolved for repeat grids in IE8

Resolved in Pega Version 7.1.7

When using IE8 and Master / Detail editing with a modal window, hitting the enter key to submit a button attached to a repeat grid caused a JavaScript error. This was traced to tabbing forward from the header of a grid: if the grid has no records, the 'no results' message was getting selected as a row and causing a miscalculation. The code has been updated to ensure the 'no results' message is not selected.

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