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-116508 · Issue 170253
Large flow handling improved for IE8
Resolved in Pega Version 7.1.7
When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.
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-116818 · Issue 167121
Corrected swim lane routing with shapes
Resolved in Pega Version 7.1.7
While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, 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-117228 · Issue 168249
Resolved issues with Flow shapes distributed across Swim Lanes
Resolved in Pega Version 7.1.7
Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.