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-173162 · Issue 650793

Certificate match will use Subject Distinguished Name

Resolved in Pega Version 8.6.1

Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.

INC-174298 · Issue 650257

Instance count logic updated

Resolved in Pega Version 8.6.1

A performance issue was seen during update that resembled an upgrade hang. This was caused by a combination of incorrect logic in DDLGenerator.getInstanceCountForClass() around counting instances of 'core' classes and all of the site history-data- tables being mapped to the same table that had 1.4+ billion rows. This behavior has been addressed with more correct query logic while performing instance counts. In addition, instance count will be supressed during command line invocations (prpcUtils, platform upgrade).

INC-180479 · Issue 659640

DSS partition count setting made backward compatible

Resolved in Pega Version 8.6.1

After update, the DSS to limit the number of partition counted was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.

INC-155070 · Issue 637579

PDF generation corrected

Resolved in Pega Version 8.6.1

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

INC-155406 · Issue 638704

Clipboard security updated

Resolved in Pega Version 8.6.1

Security has been enhanced for clipboard properties by restricting registration for readonly properties.

INC-157367 · Issue 637946

PDF generation corrected

Resolved in Pega Version 8.6.1

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

INC-157404 · Issue 630694

Adaptive Model report information exports correctly

Resolved in Pega Version 8.6.1

Clicking export to Excel or PDF in the Prediction Studio Adaptive Model report was not working. Investigation showed the first double quote of the propositionName was getting replaced from & quot ; to "", which resulted in an error while performing openUrlWindow action. This has been resolved by adding a new helper handler, while creating context menu using Handlebars.

INC-157448 · Issue 638923

Latitude and longitude populated for CreateWork history

Resolved in Pega Version 8.6.1

After enabling geo location in the casetype rule, when the case was created using the Create menu option from either Dev studio or Manager portal the Latitude and longitude values were set on the pxRequestor page and were available in the Case Audit history in the Map control. When the same case was created using CreateWork action configured on a button, it did not log the latitude and longitude values in the case Audit history. Investigation showed this was caused by a 'when' condition in the AddWorkHistory activity which checks the requestor page for latitude value and which had a null value when a createWork action was used to create the case. To correct this, the template metadata of the form will be populated with latitude and longitude values from pxRequestor page to be used in the latitude and longitude hidden fields.

INC-157860 · Issue 633948

Corrected error message display in right-to-left locales

Resolved in Pega Version 8.6.1

When using the standard report definition view in the Arabic (ar_AR) locale, error messages for a filter condition were displayed with an incorrect extended horizontal scroll bar with white space. This was traced to the legacy popover styling causing an issue with locales that display text from right to left, and has been resolved by setting the default overlay left to 0PX for these locales.

INC-160805 · Issue 640852

PDF generation corrected

Resolved in Pega Version 8.6.1

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

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