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-A22298 · Issue 243924

Refresh corrected for tabbed screen flow perform harness

Resolved in Pega Version 7.2.1

When using the "TabbedScreenFlow7" perform harness, an incorrect refresh call caused the Actions menu on the work object to disappear from the screen. This has been resolved.

SR-A22933 · Issue 241566

Check added to resolve Google Chrome-based value localization error

Resolved in Pega Version 7.2.1

A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.

SR-A22933 · Issue 246958

Check added to resolve Google Chrome-based value localization error

Resolved in Pega Version 7.2.1

A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.

INC-192769 · Issue 683001

Removed incorrect role from accessible filter logic

Resolved in Pega Version 8.7

When using JAWS, tabbing out from Close(X) and setting focus on the "filter by" section resulted in JAWS reading out "use arrows to move". This was not an available action, and has been resolved by removing role="listitem" from the RRFilters_logic.

SR-A19814 · Issue 237605

Entropy pool explicitly coded for UNIX/Linux Oracle installations

Resolved in Pega Version 7.2.1

When running a new install on an Oracle database in a UNIX environment, install was failing repeatedly at the same point when attempting to import one of the application bundle components. This issue was traced to the way the newer versions of the Oracle JDBC driver gather entropy by defaulting to the use of /dev/random. When running in an environment where there this is not a lot of noise, the entropy pool will eventually be empty and the connection will be reset. Earlier versions of the Oracle JDBC driver did not see this issue. To resolve this, in the event that a deployment is being performed on a UNIX/Linux platform using an Oracle database, the -Djava.security.egd=file:///dev/urandom will be specified whenever a java utility is started.

SR-D28496 · Issue 499081

Corrected exceptions report appearing on user screen

Resolved in Pega Version 8.1.6

When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.

SR-D28469 · Issue 499089

Corrected exceptions report appearing on user screen

Resolved in Pega Version 8.1.6

When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.

SR-D28480 · Issue 499085

Corrected exceptions report appearing on user screen

Resolved in Pega Version 8.1.6

When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.

SR-D80589 · Issue 544841

Check added before clearing Report definition custom filter section page

Resolved in Pega Version 8.5

When using a Custom Section in the Report Viewer, the Page referred to at the Prefix was getting reset while running the report. Investigation showed the page was being reinitialized in pzCreateCustomFilterPage step 2, and this has been resolved by adding a 'when' rule for clearing the custom filter page.

SR-A16401 · Issue 232956

Design-time email account accepts Data Page for port number

Resolved in Pega Version 7.2.1

When creating an Email Account rule (Integration-Resources), at design-time, the developer was prevented from using a Data Page reference as the Port number for the Sender or Receiver even though the run-time behavior of using a Data Page reference as a port worked. This has been resolved by removing the UI validation when the input starts with 'equal to', allowing Email Account save and connectivity testing to work with non-parameterized Data Page references for the port number in both Sender and Receiver configurations.

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