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.

SR-113714 · Issue 173122

Added tenantID checking for multi-tenant import of access groups

Resolved in Pega Version 7.1.7

When attempting to overwrite an existing access group by importing the Client Access groups in the tenant layer, an error was generated and the access groups were not overwritten. This occurred when the SQLs were not Tenant-qualifying for operator records but were being imported into a tenant; as a result, operator record updates were marked as inserts. To correct this, the behavior has been updated to query for current tenantId and always tenant-qualify the query if it's an overridable instance and not in a shared context.

SR-114353 · Issue 166997

System scanner performance enhanced

Resolved in Pega Version 7.1.7

When working with a large number of hotfixes, the system scanner can become very slow. Performance enhancements have been incorporated to increase speed by changing how ID and key comparisons are performed.

SR-116041 · Issue 165468

Update Manager performs version checking before installation

Resolved in Pega Version 7.1.7

An enhancement has been added to Update Manager to prevent installation of a HFIX meant for a different release of PRPC.

SR-116439 · Issue 166256

Update Manager performs version checking before installation

Resolved in Pega Version 7.1.7

An enhancement has been added to Update Manager to prevent installation of a HFIX meant for a different release of PRPC.

SR-116510 · Issue 171699

Handling corrected for testing rulesets with multiple versions

Resolved in Pega Version 7.1.7

If two rulesets with multiple versions were moved to a test environment, when the product rule was created only one of the version's instances was in the .jar file. This issue was caused by incomplete clearing of the ruleset spec after collecting the rules, and has been corrected.

SR-116941 · Issue 168143

Improved performance for sending queued messages

Resolved in Pega Version 7.1.7

LogToSpecifiedAppender was experiencing poor performance in some situations caused by duplicating locking attempts while processing an appender to send queued messages. To improve this, code changes have been made to smooth locking and avoid searching appenders when dynamic appenders are configured.

SR-117131 · Issue 167711

Corrected Rule cleanup utility

Resolved in Pega Version 7.1.7

The Rule Cleanup utility deletes instances from pr4_rule_ruleset that contain old ruleset versions. Some Rule-RuleSet-Name instances have rulesets and were deleted incorrectly. To correct this, the utility has been modified with an additional 'where' clause to restrict deleting Rule-RuleSet-Name instances.

SR-117847 · Issue 172996

Handling enhanced for custom system names

Resolved in Pega Version 7.1.7

If the system.name property in setupDatabase.properties was updated to reflect a custom System Name during ruleset migration, the value was not being used by the software update process and the resulting error caused a batch failure. There was a workaround of explicitly setting the system name in the field env name="Identification/SystemName" value=, but this has been updated to fetch the name from the db. In addition, the query that fetches the system name has been modified with a check to make sure that there is at least one requestor for the name it fetches.

SR-128961 · Issue 208349

Added check for naming conflicts when upgrading Oracle

Resolved in Pega Version 7.2

When attempting to upgrade a single schema on Oracle database, running the generateddl script failed with a NullPointerException. This was caused by database tables which had a column name called 'SYS_ID' as part of the primary key. Since Oracle uses system-generated names beginning with "SYS_" for implicitly generated schema objects and subobjects, Oracle discourages the use of this prefix in the names explicitly provided to the schema objects and subobjects in order to avoid possible conflicts in name resolution. To resolve this, a tester has been added to the system to check for this naming use and issue a warning.

SR-A2239 · Issue 205811

Documentation added on adding Tomcat-on-Oracle Rules resource

Resolved in Pega Version 7.2

The Tomcat-on-Oracle installation guides for Pega ML7 and ML8 did not contain instructions for adding a for jdbc/AdminPegaRULES. As such if the installer prepared a two-user (Base + Admin) setup in the database and allocated the Base user to jdbc/PegaRULES, the Pega platform was unable to run DDL to create new tables for new work types and new data types, as the installer has not configured the additional datasource to use the Admin user. The documentation has been updated to add the necessary step between Steps 1 and 2 of the "Create a JDBC Datasource" chapter (page 41 from the ML7 installation guide).

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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