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-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.

INC-166168 · Issue 643922

Leading space will be trimmed from date string

Resolved in Pega Version 8.4.5

A given value in the date calendar icon was reverting back to the current date. This was traced to an imported list of date strings in different formats that included a leading space. To handle this, code changes have been made that will trim the extra space in the date when processDate method is called.

INC-166444 · Issue 642030

FlexModalTemplate Modal window size consistent

Resolved in Pega Version 8.4.5

The FlexModalTemplate modal window size was changing on second click. This was a missed use case for dirty dialog CSS implementation, and has been resolved by moving the CSS necessary into the isDirtyDialogOpen if condition.

INC-166706 · Issue 647477

Handling added for Rich Text Editor base tag in email

Resolved in Pega Version 8.4.5

Clicking on an email interaction case from the worklist was not opening the case. This was traced to a base tag present in Rich Text Editor content which impacted security protections, and handling has been added to remove this tag.

INC-167379 · Issue 640577

Unescape function added to CSR portal layout template rule

Resolved in Pega Version 8.4.5

When older sections previously used by the CSR portal were carried forward into more recent versions and were 'saved as' in the application ruleset, the error "Uncaught TypeError: pega.util.Dom.unescapeHTML is not a function" appeared. Dashboard loading took an excessive amount of time or didn't load at all, and no actions were working on the dashboard screen and tabs. This was traced to there being an older implementation of pega.util.Dom.unescapeHTML in pzpega_ui_template_layout_header, and this issue has been resolved by adding a custom unescape function in the rule itself so that it doesn't fail in cases where the dependent rule is not able to load the standard unescapeHTML utility.

INC-167599 · Issue 648281

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-167747 · Issue 646577

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-168050 · Issue 640133

Resolved unregistered request for Dev Studio clipboard viewer

Resolved in Pega Version 8.4.5

After upgrade, running a report in Dev Studio and then clicking to start the tracer or clipboard did not open, but instead generated the error "Unregistered request encountered." This has been resolved by adding a pySecureFeatures check in step1.

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