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-C80958 · Issue 419199

Added check for appname to avoid HarnessFail execution error on Mashup reload

Resolved in Pega Version 8.3

A HarnessFail execution error was occurring on Mashup reload. This was caused by the appname being appended twice during the reload, and has been resolved by adding a check to the _finalizeNavURL method in the PegaCompositeGadgetMgr.js file to remove appName if it is present in the URL to prevent duplication.

SR-C63789 · Issue 419236

Corrected double call to defer load activity on composite

Resolved in Pega Version 8.3

When specifying a pre-activity in defer load, the pre-activity was getting called twice when that dynamic layout was in a Layout group. This has been corrected.

SR-C75823 · Issue 419474

DSS added to handle Amazon S3 socket timeout exception

Resolved in Pega Version 8.3

In Amazon S3, a timeout exception occurs when the socket is idle more than the default timeout value (50 seconds). In order to compensate for this, an enhancement has been added which provides a DSS “repository/s3sockettimeout” where the s3 socket timeout can be specified in milliseconds. When a value is provided to this DSS, it will override the default value of 50 seconds.

SR-C29160 · Issue 419494

Performance improvements made on bulk actions

Resolved in Pega Version 8.3

Latency was observed when performing transfer Bulk Action on cases. Investigation showed that the "Select Action" button in pzBulkProcessingActionSection contained a refresh other section action for the pzBulkProcessingCheckbox section that executed on each row of the grid rendered. This refresh is not needed as the "Post value" action will take care of posting the selected checkbox data to clipboard, so it has been removed to resolve the performance issue.

SR-C61562 · Issue 419880

CPU time will be fetched from MBeanServer instead of the JRE application to provide consistency

Resolved in Pega Version 8.3

The value of CPU time in the Enterprise health metrics was being given in nanoseconds instead of seconds after the IBM JRE version was upgraded by applying Websphere Application Server patches. The CPUTimer is a platform class which has logic specific to different JRE vendors; in order to provide consistent results regardless of which JRE is used, the system has been updated to always fetch the values from the MBeanServer.

SR-C81857 · Issue 420241

Enhancement added to support dropdown with page list property

Resolved in Pega Version 8.3

To enable the use of a dropdown control with a property of type page list, an enhancement has been added to support a clipboard page for drop down and autocomplete.

SR-C82530 · Issue 420610

Atmosphere cross-site scripting Vulnerability fixed

Resolved in Pega Version 8.3

Atmosphere has been updated to close a potential cross-site scripting vunerability.

SR-C73440 · Issue 420679

Batch Execution report performance improved, and counts calculation checkbox control added

Resolved in Pega Version 8.3

Running the Batch Execution report in PegaMarketing was causing poor performance and heap dumps along with node crashes. If paging was enabled and the report had very large result sets, getting the total result count was a very expensive database operation. In order to improve performance, the system has been modified to utilize a new paging mode, A checkbox has also been added that allows turning on or off calculating the total result count and pagination count.

SR-C75566 · Issue 420775

Added null check to avoid DisplayCardAccountHeader rendering issue

Resolved in Pega Version 8.3

When the out of the box section DisplayCardAccountHeader was created by View editor and then converted to full section editor, the embedded sections were empty or not seen. This was traced to the design view javascript hitting an error which caused the design view rendering to fail. To correct this, pzpega_ud_gridlayout_model has been updated to wrap the line in question with a null check and set the value to empty string if it doesn't already exist in the model.

SR-C82254 · Issue 421055

Support added for saving draft survey flows in production level 5

Resolved in Pega Version 8.3

With production level set to 5, creation of a survey was generating two errors: in UI, "Default survey flow creation failed", and in trace, "Update record failed: .pyDraftModeON". Because in most cases Survey authoring would be done in a system with a lower production level where users would not see any issues, the code did not include support for saving draft mode flows when the system was set to production level 5. This ability has now been added to support this use.

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