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-163544 · Issue 639298

Accessibility corrected for Cosmos user portal left navigation panel

Resolved in Pega Version 8.4.5

It was not possible to see the focused control label in the left pane of the Cosmos user portal because it was not expanding when its control received focus from tabbing. Investigation showed the class acting as a polyfill for :focus-within was applied only on the observed element when using Microsoft Explorer 11, and this has been resolved by updating the CSS selectors and ensuring the class is applied to every parent element down the DOM tree.

INC-163596 · Issue 636234

Checkboxes receive correct focus with accessibility

Resolved in Pega Version 8.4.5

It was necessary to click the tab twice in order to check the checkbox in the filter popup. This has been corrected by adding a check in the firstfocuselement method so the focus is placed correctly over input type elements.

INC-164311 · Issue 635784

Correct datetime target property used

Resolved in Pega Version 8.4.5

When using a declare expression for a datetime property to get its value from another datetime property, attempting to change the source datetime later resulted in the error "28-mar-2021 is not a valid date/time value". This occurred when the source datetime property had display readonly formatting, and was traced to the formatted value being sent in the callGetTargets API instead of the selected date value, which caused the function to be returned as empty because there was no target property in the same page before submission. To correct this, a check has been added which will get the value from data-value instead of element.value and will skip callGettragets if the target is empty.

INC-164631 · Issue 641441

Updated Ajax container close to resolve intermittent portal freeze

Resolved in Pega Version 8.4.5

The portal was intermittently freezing after the "+" icon was clicked to create a new case from the Create menu. This was traced to the Ajax container not closing after creation of the create modal, and has been resolved.

INC-164892 · Issue 636538

PDF generation corrected

Resolved in Pega Version 8.4.5

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-164924 · Issue 639010

Serbia added to country codes list

Resolved in Pega Version 8.4.5

The CountryCode for Serbia (SRB) has been added to the existing country codes.

INC-165277 · Issue 645170

PDF generation corrected

Resolved in Pega Version 8.4.5

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-165363 · Issue 635076

Dirty Check Warnings added for decimal fields

Resolved in Pega Version 8.4.5

Dirty Check Warnings have now been added for decimal fields by adding the required logic to the isContainerDirty API in pzpega_ui_doc_dirtyhandling js file.

INC-165567 · Issue 643379

Window reference added for custom tab handling

Resolved in Pega Version 8.4.5

After configuring a tab layout in the portal harness rule to get tab view, launching the portal from Designer Studio and opening the tabs worked as expected, but opening the portal using end user operator and performing any operation in a tab resulted in the error "Uncaught ReferenceError: gIsCustomTabHeaderEnabled is not defined". This was caused by a reference property that was not being referred properly, and has been resolved by using gIsCustomTabHeaderEnabled from the window reference to handle the undefined scenario.

INC-165964 · Issue 656815

Harness context set for modal dialog on interaction portal

Resolved in Pega Version 8.4.5

An AddDelete refresh condition on a page list property was not triggering a ReloadSection as expected. This was a special use case in the interaction portal where a modal dialog was opened but the harness context was not set properly, and has been resolved by ensuring the harness context is correct.

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