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.

INC-137875 · Issue 608104

Update for special characters in operator name

Resolved in Pega Version 8.4.4

Handling has been added for encoding an operator full name field which contains special characters.

INC-137915 · Issue 604618

App Studio compliance tool shows category results

Resolved in Pega Version 8.4.4

After upgrade, results were not displayed categorically while running the app studio compliance tool: only the number of total issues was available. Investigation showed that pzLPApplicationGuardRailsInnerTable was not resolved correctly, and since there was no object class defaulted there was an issue in creating the results in the correct class. This has been resolved.

INC-137966 · Issue 597738

Embed-ReportFilter supports pyDateproperties

Resolved in Pega Version 8.4.4

After creating a report definition with Date time filter values where the 'from' date and 'to' date are input and propagated as “pyStartDateTime” and “pyEndDateTime” in the clipboard, opening the pyDate properties from clipboard resulted in a 'rule not found' exception. No properties of other data types generated the error. This has been resolved by creating the pyStartDateTime,pyEndDateTime and pyDisplayTimeperiod properties in Embed-ReportFilter to support this use.

INC-139054 · Issue 598151

PD4ML library updated

Resolved in Pega Version 8.4.4

When generating a PDF, lines were broken up for the content boxes. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.

INC-139086 · Issue 597144

"Show next error" correctly displayed on user portal

Resolved in Pega Version 8.4.4

In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.

INC-139790 · Issue 607416

Tenant Switching updated

Resolved in Pega Version 8.4.4

When working on new “tenant switching” implementations in a multi-tenant environment, the API itself seemed to be working as expected (case details from another tenant were shown correctly in review mode), but clicking on the assignment unexpectedly opened the case in a new window that contained the same review view of the case rather than the perform view. Clicking the assignment link again caused yet another review window to open with the same issue, over and over. This has been resolved by adding a UI-side update to send the requests on proper sub-domain URL instead of using the parent domain, and by ensuring the document threads are properly deleted for multitenant usecases.

INC-139966 · Issue 606844

JAWS announces popup error message

Resolved in Pega Version 8.4.4

When a form is submitted without giving value to required field, a browser pop up appears. The expected behavior is that the screen reader (JAWS) should move the focus to the field that has error and read the error message However, JAWS was not announcing the error "Value cannot be blank". This was traced to a scenario where if pega.u.d.fieldErrorType === "ERRORTEXT" is true, the class on the span within the error div will be set to "inputSpans", and this resulted in the return of an empty array for document.querySelectorAll("span.iconError.dynamic-icon-error"). To resolve this, support has been added for the "inputSpans" class.

INC-141302 · Issue 614993

UI automation script documentation update

Resolved in Pega Version 8.4.4

To provide a more consistent experience, explanatory comments in the code for UI automation scripts have been removed.

INC-141387 · Issue 612826

Autocomplete/autopopulate in table works properly with keyboard

Resolved in Pega Version 8.4.4

When two autocompletes in a table (two separate columns) were sourced by different properties within the same data-page, clicking to select a “reason-code” in the first autocomplete column correctly populated the corresponding “reason description” in the second column autocomplete. However, when using configured keyboard presses on the auto complete with post value and data transform actions (enter-key, tab-key, and on change), selecting from the auto-complete list and pressing enter or tab to select the item populated the second column as expected but the first column auto-complete showed the selected code for a moment and then was cleared. This as traced to the associated property set value executing after all associated properties setvalue actions were completed, and has been resolved.

INC-141451 · Issue 601141

Radio button helper text is localized

Resolved in Pega Version 8.4.4

The localized value from content was not being served for helper text in a radio button group. This has been resolved by adding the necessary localization support to the button template.

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