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.