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-B35799 · Issue 277230

Alerts modified to correct logged interaction totals

Resolved in Pega Version 7.3

The PEGA0069 alert identifies when a client load of a screen takes longer than the threshold for the alert. A client load can contain multiple server interactions and the PAL for the alert should be the aggregate of all these interactions. However, the calculations for pxTotalReqTime were duplicated in the code for the PEGA0046 and PEGA0069 Alerts, causing incorrect data. This has been fixed.

SR-B35931 · Issue 293471

prpcUtils readme updated for importing to Oracle

Resolved in Pega Version 7.3

The readme regarding importing to an Oracle database has been updated to reflect the current state of prpcUtils.

SR-B36418 · Issue 293162

More descriptive error message for RAP import

Resolved in Pega Version 7.3

In order to clarify that Schema migration does not support importing a table with the same name as an existing view or a view with the same name as an existing table, the code has been updated to throw a more descriptive exception.

SR-B36743 · Issue 293937

BLOB data save performance improved

Resolved in Pega Version 7.3

In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.

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-B39528 · Issue 303228

Node startup modified to support very large clusters

Resolved in Pega Version 7.3

Node startup was failing if the cluster had more than 50 nodes. This issue was caused by the query to the "pr_sys_statusnodes" table only returning 50 records; this limitation has been removed.

SR-B40657 · Issue 298764

Clarified database privileges to start Pega

Resolved in Pega Version 7.3

The documentation has been updated for clarity regarding database privileges for start up. The text "Pegasystems recommends that you create an Admin user separate from the Base user; however, if you opt for a single Base user, grant these permissions to the Base user" has been modified to read: "Pegasystems recommends that you create an Admin user separate from the Base user; however, if you opt for a single Base user, grant the Base user both sets of privileges listed above."

SR-B41874 · Issue 301766

View parsing regex fixed for union statements

Resolved in Pega Version 7.3

While importing jar file through import out-of-the-box, generated SQL Scripts from the manual option system had scripts which were already present in the Database. This was caused by the view parsing regex not handling UNION statements, and has been corrected.

SR-B42911 · Issue 301591

Tomcat config documentation clarification

Resolved in Pega Version 7.3

The documentation for using Tomcat has been updated for clarity. Step 2b of 'Configuring Tomcat by editing the context.xml file' indicates that configuration of the Admin datasource is optional (which it is), but steps 3 and 4, which use this datasource, were not labeled as conditional on 2b. As a result, those opting not to use the admin datasource believed those settings needed to be added. In the new text for steps 3 and 4, the clarification "For dual-user configurations only, insert..." has been added.

SR-B43415 · Issue 299493

Upgrade does not exit when encountering corrupt ruleset name

Resolved in Pega Version 7.3

In order to avoid upgrade failures caused by an application rule existing without a version (corrupted data), handling has been added so that the upgrade will not fail if it encounters an application rule without either a name or version.

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