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.

INC-168254 · Issue 659299

Documentation updated for accents and special characters used in search

Resolved in Pega Version 8.5.5

The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character.

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 property in 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-B65434 · Issue 334578

Oracle table metadata performance improvements

Resolved in Pega Version 7.4

Performance improvements have been added for Oracle table metadata queries.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us