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-B36948 · Issue 298094

Dynamic UI supports repeating grid sourced from Page List

Resolved in Pega Version 7.3

After creating and running a case, clicking on the "Edit Details" option from Other Actions Menu did not display the section containing a repeating grid sourced from a Page List. This was due to the final rule activity "pzdynamicuisetupfields" not considering the case of Page List while configuring the dynamic UI, and it has been updated to properly propagate the values.

SR-B36974 · Issue 293707

VBD improvements and fixes

Resolved in Pega Version 7.3

The following issues have been addressed: 1) VBD was generating the message "Error converting DB record to VBDRecord" when IH contained 'timestamp with time zone' fields and the backend was Oracle. This has been resolved by modifying the Partition loading logic to support Oracle Timestamp type fields. 2) VBD was loading data from all columns in the IH tables, including those not needed in VBD. To improve performance, the Partition loading logic will filter out IH DB fields that are not set up in IHConfig. 3) The logic for unpacking Cassandra (for access to diagnostic tools) into the app server directory would fail without proper permissions. To avoid this Cassandra will be unpacked into the Pega Platform work directory instead of the app server directory. Work will not need to be cleared as this Cassandra directory is for access to diagnostic tools only. 4) Eager loading will indicate in the logs when the load is finished with the message "Eager mode loading of partitions completed. X partitions(Y rows) loaded." 5) DB check using min/max query could be slow when given a large fact table, leading to data flow timeouts. To fix this, DB check will no longer occur on the same thread that processes Data Flow inserts. Additionally, the DB check will only scan for min instead of min/max. Operations that do require min and max have been split into two queries (one for min, one for max). 6) Previously, if a VBD Client node was disconnected from the cluster due to Pulse not finding any VBD server nodes, only a VBD server node restart or VBD Client node restart would get them reconnected. To make this process easier, VBD Pulse will reconnect the client if it is found to be disconnected while the VBD cluster is up.

SR-B37039 · Issue 293524

Security upgrade for Struts2

Resolved in Pega Version 7.3

To improve security, Apache Struts2 has been upgraded to version 2.3.32 .

SR-B3704 · Issue 276504

Added check for cancel modal in expand-pane grid

Resolved in Pega Version 7.3

A modal window would not close if the modal dialog was launched after a row of an expand-pane grid was expanded. The issue was caused by a call to an incorrect version of the cancel modal for this configuration, and a check has been added to ensure the proper version is used.

SR-B37115 · Issue 293959

PegaUnits bulk testing updated

Resolved in Pega Version 7.3

AUT test cases were failing while running in bulk, though running a single unit worked as expected. This was found to be a conflict with the way a test case uses a current parameter page from the start of execution to end of execution and then passes it to the next test; if there are two data page test cases where one is configured to have a non-blank value for a given parameter while the second one has a blank value for same parameter, the second test unexpectedly encounters the non-blank value. To resolve this, the code has been modified to reset the value of only RUT params before set up is called, so that every test case behaves truly independently.

SR-B37115 · Issue 286705

PegaUnits bulk testing updated

Resolved in Pega Version 7.3

AUT test cases were failing while running in bulk, though running a single unit worked as expected. This was found to be a conflict with the way a test case uses a current parameter page from the start of execution to end of execution and then passes it to the next test; if there are two data page test cases where one is configured to have a non-blank value for a given parameter while the second one has a blank value for same parameter, the second test unexpectedly encounters the non-blank value. To resolve this, the code has been modified to reset the value of only RUT params before set up is called, so that every test case behaves truly independently.

SR-B37139 · Issue 294520

Installation guide updated to reflect that ADM is supported on MS SQL.

Resolved in Pega Version 7.3

The installation guide has been updated to reflect that ADM is now supported on MS SQL server.

SR-B37301 · Issue 295750

Repaired REST Connections with proxy

Resolved in Pega Version 7.3

After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.

SR-B37306 · Issue 293862

Security upgrade for Struts2

Resolved in Pega Version 7.3

To improve security, Apache Struts2 has been upgraded to version 2.3.32 .

SR-B37351 · Issue 296014

FTP connection test loads authentication profile

Resolved in Pega Version 7.3

The FTP Server Test connectivity button was not working if the server did not allow anonymous connections. This was due to tests not loading the Authentication Profile, and the system has been updated to load the profile during the connection build process.

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