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.

SR-C83050 · Issue 422977

IE width calculation fixed for imported built-on with dymanic layout

Resolved in Pega Version 8.2.1

After upgrade, the Built On input for the application screen in Designer Studio was not rendering in the IE11 browser if dynamic layout was used. This was caused by a browser-specific issue with width calculation for pzDefinition, and code has been added to handle this issue.

SR-C89316 · Issue 426077

Lower major ruleset versions will not be considered during design time validation

Resolved in Pega Version 8.2.1

After circumstancing a rule by property and withdrawing the rule in higher version, the same rule was circumstanced by template. Later after major skimming, attempting to perform a save-as of the circumstanced template rule resulted in an error stating that the circumstanced property already existed. During design time, the system validated the rule with rules from all other ruleset versions. In this corner case where a property-based circumstanced rule was withdrawn and then skimming was performed, the error occurred because it was being saved in a different major ruleset instead of into the same major ruleset. In order to better handle this condition, the system will not consider rules from lower major versions during design time validation.

SR-C75723 · Issue 421826

Rollback filter query updated to handle very large classes mapped to the same history table

Resolved in Pega Version 8.2.1

When rolling back the imported product file using deployment manager, the error "DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: column "pzinskey" does not exist" was seen. This was traced to the rollback process picking the already processed items from the history table due to an incomplete filter query that occurred when there were more than 1000 classes mapped to same history table. This has been resolved.

SR-C81410 · Issue 422137

Radiobutton aria-label enhanced to retrieve localized field value

Resolved in Pega Version 8.2.1

Localization code has been added to the pzpega_ui_template_radiogroup file to support using RadioButton aria-labels for Field value.

SR-C83468 · Issue 424950

Legacy multipart upload support added for very large hotfix catalogs

Resolved in Pega Version 8.2.1

After a package containing 100+ hotfixes was installed, the fixes were not visible in the Hotfix Manager page even though the database status showed them as "Installed". Investigation showed that performing a system scan on the catalog upload was resulting in thread dumps while decoding the request URL due to the control used for catalog upload posting the entire content in form data rather than sending a multi-part request. To unblock this use case for catalogs with huge data, the system has been updated to perform a legacy upload where a form submit is used with content-type as "multipart/form-data" rather than sending the entire data in the request header.

SR-C76412 · Issue 425189

Content type header removed from default inclusion in JWT token to support MS integration

Resolved in Pega Version 8.2.1

In order to integrate Pega with Office365 to use the Outlook API to Send and Get messages, an access token is required as a part of Authentication process. For obtaining an access token from the Azure directory, the process is to follow the OAuth 2.0 client credentials flow which requires the generation of a JSON Web Token (JWT) with the required Header, Payload and Signature. However, because Pega adds the tag "cty": "application/json" by default, using the out-of-the-box 'Token Profile' rule to generate the JWT and pass the same in a REST call to Microsoft was resulting in a error response indicating that there was an unsupported token header. This has been resolved by removing the content type header in the JWT token.

SR-C79482 · Issue 424536

DSS added to allow custom timeout for BIX query

Resolved in Pega Version 8.2.1

The BIX query to retrieve the blob column was taking up to 60 seconds for large volume, causing timeouts. Previously, the extract defaulted to using repost pzSample which is internal/final and has a default timeout of 30 seconds. In order to avoid timeouts, the new DSS "BIX/selectQueryTimeout" has been added to allow setting a custom value. Further refinements will be made for multi-tenant environments in a future release.

SR-C85614 · Issue 427439

BIX extract connection leak repaired

Resolved in Pega Version 8.2.1

The first time that a BIX extract was run it failed with a timeout. Running it again immediately was successful. Investigation showed that if the BIX connection timed out, the connection was not being returned to the connection manager due to a failure to reset the autocommit for a connection that partially ran but was not properly closed. This has been resolved by adding handling that will return the connection to the pool and clear the map if there is an exception. Further refinements will be made for timeout issues in multi-tenant environments in a future release.

SR-C84135 · Issue 424531

Metadatatree updated to be function-scoped in UI to resolve custom tab control display issue

Resolved in Pega Version 8.2.1

When switching rapidly between two custom tabs, especially clicking in and then clicking away before the busy icon could be displayed, the section containing the tab controls was intermittently refusing to display. Refreshing the browser or clicking on the Pega button made the section visible again. This was traced to the template "metadatatree" getting overlapped with subsequent template processing due to a timing issue as "metadatatree" was being maintained in the global window object. To resolve this, "metadatatree" has been updated to be function-scoped in renderUI to avoid timing issues.

SR-C82059 · Issue 423071

Support added for configuring key stores using prconfig or system properties

Resolved in Pega Version 8.2.1

Previously, stream service only supported key store and trust store configuration using Data-Admin-Keystore instances. Unlike cluster encryption, it did not allow the configuration of key stores using prconfig or system properties. In order to align Stream service SSL configuration with the rest of the platform, support has now been added for the following system and prconfig properties: -Dpega.cluster.keyStore -Dpega.cluster.keyStorePassword -Dpega.cluster.trustStore -Dpega.cluster.trustStorePassword

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