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.

SR-C18637 · Issue 360155

Logic repaired in toGMT RUF

Resolved in Pega Version 8.1

A logic error in the toGMT RUF has been fixed to correctly handle dates before the epoch date.

SR-C18766 · Issue 364186

SignatureMethod Algorithm attribute in Authentication Activity now obtained from certificate

Resolved in Pega Version 8.1

When creating an authentication request in pySAMLWebSSOAuthenticationActivity (step 6), the system was generating the wrong SignatureMethod Algorithm if the site was using certificates with RSA - SHA256 encryption. This was due to the signature algorithms being hardcoded in SAML code, and has been resolved by getting the signature algorithm from the certificate.

SR-C18766 · Issue 362376

Logout binding switched to signed certificate for signature

Resolved in Pega Version 8.1

HTTP Redirect logout binding uses a hard coded "rsa-sha1" from a open SAML library file to calculate the signature; this created an issue with ADFS. To override this, the system will use the subclass buildRedirectURL() to get the signature algorithm from signed certificate instead of the hard coded signature algorithm (Sha1).

SR-C1883 · Issue 359736

Added iFrame garbage collection to improve memory use for multiple child cases

Resolved in Pega Version 8.1

Client Side memory was piling up due to multiple child cases being attached to the same parent case without a garbage collection process passing over the iframes. Performance has been improved by adding garbage collection to files pega_ui_busyindicator and pzpega_mobile_hybrid, pzpega_ui_doc_lifecycle.

SR-C18868 · Issue 362502

Improved performance and error handling for assembled 'when' rules

Resolved in Pega Version 8.1

This release features a major re-working of the assembled 'when' rules to improve performance. The vast majority of rule dispatch costs come from unnecessary work. By optimizing VTable dispatch, eliminating unnecessary validation, increasing intrinsic usage, and optimizing dispatch routines, rule dispatch has been made 5-100x faster for IL-Assembled rules. In addition there is improved error handling for exceptions.

SR-C18883 · Issue 362411

Recipient flexibility added to scheduled Guardrail reports

Resolved in Pega Version 8.1

Scheduled guardrail reports were delivered only intermittently. This was traced to the report having an email address (as opposed to an operator ID) in the recipient list, and the page references have been updated to correct this.

SR-C18883 · Issue 369045

Recipient flexibility added to scheduled Guardrail reports

Resolved in Pega Version 8.1

Scheduled guardrail reports were delivered only intermittently. This was traced to the report having an email address (as opposed to an operator ID) in the recipient list, and the page references have been updated to correct this.

SR-C18886 · Issue 358530

Enhancement to support international currencies in SmartDispute

Resolved in Pega Version 8.1

An enhancement has been added to the Smart Dispute application to support using international currencies. The currency control 'pxCurrencyInternational' is available in the base Pega Platform, similar to the existing control 'pxCurrency' but with format type as 'Text'. The control also has a script that removes any text other than non- numeric, comma, decimal, or negative sign values and supports both comma and dot as decimal separators.

SR-C18932 · Issue 360087

Fixed product file list view filter error

Resolved in Pega Version 8.1

When creating a product file, the error "An Exception occurred while processing contents of Rule-Admin-Product" appeared when using a list view filter in Product rule. This was caused by the instances not having the ruleset name present when it was expected, and code has been added to make sure those are included when needed.

SR-C18936 · Issue 358807

API added to customize properties used in checksum calculation

Resolved in Pega Version 8.1

In order to provide a way to customize certain system properties from a checksum calculation, an API has been added to set a list of properties to be excluded.

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