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-206483 · Issue 707092

Delegated rules page displays proper warning in Vietnamese

Resolved in Pega Version 8.7.2

Opening the "Configuration" left navigation item for delegated rules and clicking on edit to modify the rule did not display the guardrail warning message properly in Vietnamese. This has been resolved by ensuring the Vietnamese date time is properly formatted as "Ngày dd tháng M năm yyyy".

INC-206773 · Issue 708375

ScreenFlow called from Dataclass section completes as expected

Resolved in Pega Version 8.7.2

When calling a screen flow from a section of another screen flow, the flow did not work properly in the modal dialog screen flow but did work in the process flow. Investigation showed that when the second screenflow was opened from the Data class section, the assignment of the first screenflow was not deleted post submission. This has been resolved by adding a conditional block for screenFlow Dataclass section.

INC-208116 · Issue 712907

PD4ML upgraded

Resolved in Pega Version 8.7.2

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-208199 · Issue 706446

Added input null check to resolve loading error

Resolved in Pega Version 8.7.2

The application was freezing while loading if action was taken on the controls while a page level message was visible. This has been resolved by adding an additional null check for input before calling the focus API.

INC-208499 · Issue 714947

Corrected Ajax container scrollbar with tabs

Resolved in Pega Version 8.7.2

The scroll bar was not working as expected for a pyCaseWorker Section configured with an Ajax container and "Show as tabs". This has been resolved by overriding the div[data-mdc-recordid] with overflow-x: auto style to get the proper horizontal scroll in the Ajax container.

INC-208629 · Issue 704589

ReviewArchivedCase shows case hierarchy

Resolved in Pega Version 8.7.2

After update, opening the archived cases in the ReviewArchivedCase harness did not show the case hierarchy dropdown. Investigation showed this was caused by the D_CaseBreadCrumb data page calling the source activity with wrong instance key, along with the pxCaseBreadCrumbPopulate activity not supporting breadcrumbs for archived cases. This has been resolved by changing the method how the parent case item is being fetched from storage, using Obj-Open-By-Handle instead of Obj-Browse as the latter doesn't support checking the second storage. The pxBreadcrumbsCount Declare Expression has also been removed in order to facilitate the data page loading.

INC-208729 · Issue 711402

Repaired Perform for 'Assignments with Errors'

Resolved in Pega Version 8.7.2

The 'Perform' button was not working on the "Assignments with errors" pop-up. This was an inadvertent side effect of changes made in 'pega_desktop_support' (Pega-Desktop ruleset), and has been resolved by adding a check before calling pega.mobile.isMultiWebViewPegaMobileClient.

INC-208848 · Issue 703874

Cosmos landing page configuration icon updated

Resolved in Pega Version 8.7.2

In order to allow changing the Cosmos landing page configuration icon, the harness has been made available. The default icon has also been updated.

INC-209071 · Issue 706039

Other Currency resolves value in Pega DX

Resolved in Pega Version 8.7.2

When using Pega DX with the pxDisplayText currency set to "Other currency", only the property name was sent as part of the metadata and not the actual value. This has been resolved by updating "Other currency" to resolve the property reference and get the value.

INC-209906 · Issue 704865

AddMessage function shows error on UI

Resolved in Pega Version 8.7.2

After updating from Pega 8.1 to 8.6, an addmessage function which previously displayed an edit validate rule error message was not working. This was an issue with textinput inside a grid, and has been resolved by adding a style to input text when it has a symbol left aligned and giving the error icon a z-index to show the message when the symbol is configured.

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