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.

INC-144543 · Issue 600086

Keyboard accessibility added to Cosmos buttons

Resolved in Pega Version 8.4.4

Focus states were missing on the standard and icon buttons in Cosmos. These have been added to facilitate keyboard navigation.

INC-144572 · Issue 600758

Corrected mobile tab layout highlighting

Resolved in Pega Version 8.4.4

When switching between three tabs in a layout group (Other – Mobile Tabs) in a section, the highlight was appearing on the active tab and the inactive tabs. This has been resolved by updating the CSS generation to not consider hover styles for touchable devices.

INC-144709 · Issue 608797

Removed unnecessary decoding from GetDropdownOptions

Resolved in Pega Version 8.4.4

When using a dropdown sourced by a data page with parameters in the section, passing multiple values as the parameters of the data page resulted in the error "pzGetDropdownOptions:Invalid JSON Stream for data page params" and the parameter values were not resolving at runtime. This was traced to unnecessary decoding in the process, and has been resolved.

INC-144851 · Issue 604482

Date Time picker works with locale es_US

Resolved in Pega Version 8.4.4

When an Operator had the locale es_US (Spanish) set on the Profile, the Date Picker on the application was throwing validation errors when a date or time was chosen from the out-of-the-box Date Time Control. Investigation showed the date-time format for locale es_US was not supported, and the getDateTimeFormat API has been updated to support this format (11:00 a.m.).

INC-144888 · Issue 603618

Custom rich text editor plugin support updated

Resolved in Pega Version 8.4.4

At runtime, two rich text editors were used in the same harness under two different sections, one regular and one hidden till clicked. A custom plugin was implemented for rich text editor at the harness level. After upgrade, the custom plugin was not getting displayed in the hidden rich text editor. Investigation showed that if plugins were added to pega.ctx.customrich text editorPlugins, then the plugin manager discarded plugins from pega.u.d.customrich text editorPlugins. To resolve this, the rich text editor plugin manager has been modified to merge the plugins from pega.ctx.customrich text editorPlugins and pega.u.d.customrich text editorPlugins.

INC-144924 · Issue 614769

System improvements related to ActiveDocumentType

Resolved in Pega Version 8.4.4

Alerts were seen for unexpected properties in HTTP requests related to pyActiveDocumentType, and system slowness was seen when the request was trying to update the properties. This was traced to a condition where a page remove cleared property registration, and has been resolved.

INC-145119 · Issue 601713

Client side validation works with Reference page property

Resolved in Pega Version 8.4.4

A reference page property in a 'when' rule was not evaluating properly for checking a Date field when client side validation or Client side template UI was checked on the Harness level. This was traced to pyRequired being boolean: the boolean being compared to a string false value yielded a wrong comparison, leading to the wrong validation type required. To resolve this, the system will use the === comparator to compare boolean false in datetime to remove the required validator.

INC-145263 · Issue 600037

Query logic modified for Anypicker

Resolved in Pega Version 8.4.4

A search for results in the Anypicker control for the first time showed the results, but if the results were deleted and the search run again without focusing out from that field, no results were found for the second search. This has been resolved by using slice than splice in the query to avoid mutating the original array source.

INC-145467 · Issue 617216

isDCSPA flag added to ensure correct harness after reload

Resolved in Pega Version 8.4.4

When moving from a Process Flow to a Screenflow configured with tabbedscreenflow7, the first reload caused a switch to a Perform Harness that resulted in the error "Unable to open an instance using the given inputs", and footer buttons disappeared until multiple refreshes were done. This was an issue specific to the environment configuration at the site, but to avoid future issues a code update has been made that will add the isDCSPA flag if the value is not present in the parameter page.

INC-145535 · Issue 600787

Corrected layout group overlapping content

Resolved in Pega Version 8.4.4

When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors.

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