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-A21111 · Issue 268559

Performance improvements for embedded page reference checks

Resolved in Pega Version 7.3

Significant performance differences were seen between opening custom rules in the developer portal and opening the same rules in an embedded page. This was traced to each embedded page in the stream checking to see if reference properties are present. To resolve this, DirectStream has been modified to cache the value of containsAnyReferenceProperties if it has already been checked so that it is not repeatedly checked when it is not necessary.

SR-A92512 · Issue 270130

WebLogic tool generation updated for complexType schema

Resolved in Pega Version 7.3

A red X error was seen for PRAsync MDB modules on the Resource Dependencies screen in the WebLogic console in deployments with WebLogic 11i or 12c. This was due to the EJB component (prbeans.jar) not being implemented to support complexType schema, and has been resolved by updating the Pega Platform WebLogic components to support complexType schema in the WebLogic tool generation.

SR-B10345 · Issue 281585

Command line jar import handling improved

Resolved in Pega Version 7.3

When installing Smart Dispute and related strategic applications, exceptions occurred when generating a DDL via prpcUtils (e.g. prpcUtils.bat generateDDL) if any of the files listed in schema.archive.input did not contain schema changes or did not have a delta. This has been resolved by updating the system to better handle files that do not require a DDL to be generated.

SR-B12581 · Issue 282710

Documentation correction for setupDatabase.properties naming

Resolved in Pega Version 7.3

The install, upgrade, and update guides on the PDN referring to the setupDatabase.properties file properties gave erroneous name formats for the schema name properties. All instances in the documentation referring to pega.rules.schema have been changed to the correct format of rules.schema.name, and all instances of pega.data.schema have been changed to the correct format of data.schema.name.

SR-B12850 · Issue 283836

SMA Garbage Collector landing page updated to work with updated browsers

Resolved in Pega Version 7.3

SMA's Garbage Collector landing page was not working correctly on the latest versions of Chrome and other browsers due to the document.all JavaScript function being deprecated. The code has been updated to correct this.

SR-B13020 · Issue 283559

Upgrade App Schema generates unique index name IDs

Resolved in Pega Version 7.3

Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.

SR-B13020 · Issue 283078

Upgrade App Schema generates unique index name IDs

Resolved in Pega Version 7.3

Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.

SR-B15143 · Issue 285148

Garbage Collector access fixed in Logging screen

Resolved in Pega Version 7.3

SMA Garbage Collector information was not available under Logging and Tracing due to a naming error; this has been fixed.

SR-B15499 · Issue 294497

SMA Remote Tracing works with URL encryption

Resolved in Pega Version 7.3

When URL encryption is enabled, Remote Tracing was not working from SMA. This occurred because the handling for the trace request coming from SMA was not triggering the URL encryption as needed, and has been fixed.

SR-B16328 · Issue 286668

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.

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