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.
INC-202878 · Issue 713792
Handling updated for social messaging items with very large embedded images
Resolved in Pega Version 8.6.5
Job scheduler was running out of memory while handling large/multiple files, causing nodes to crash while handling Social Messaging items. Inline images were also not being sent in the ACK email. Investigation traced this to a custom job scheduler and activity used to create PDFs from email communication and send the PDFs to a third-party system. This used the standard Email Triage/PegaSocial functionality for the emails, which were stored as instances of PegaSocial-Message. The custom Job scheduler and activity then leveraged the Data Page D_pxEmailPosts to retrieve the emails in order to harvest the text from the emails. The issue occurred when a number of the emails had multiple or large embedded images in them, meaning the PegaSocial-Message instances are very large. This resulted in the node running out of memory and crashing. To resolve this, code has been added to support inline images in ACK email and the complete message from Pulse will be used instead of the original message as the email body for the ACK email.
INC-211974 · Issue 706616
UpgradeInteractionCase modified to update work page on save
Resolved in Pega Version 8.6.5
After update, service cases were failing to unpend when using a custom data transform that accessed the D_CorrespondenceCase data page. Investigation showed the D_CorrespondenceCase data page was internally using the D_pxGetInteractionCaseDetails data page; this call upgraded and saved and committed the case but this commit released the lock which the custom data transform had acquired. Because this happened before accessing the CorrespondenceCase datapage, it led to an error while committing the service case details. To resolve this, the postprocessing activity "pyUpgradeInteractionCase" of D_pxGetInteractionCaseDetails has been modified to write the update on the work page as soon as a save is performed.