SR-123717 · Issue 192182
Purging of covered objects improved
Resolved in Pega Version 7.1.8
When purging a Cover item, the history of certain covered objects was not purged. This happened when the Cover and Covered classes belonged to different class groups. This happened because the 'getHistoryKeys' function tries to fetch the history details of a given key by looking into its history table. This was using the class group information from the archive configuration, which was not always the same for covered objects. To resolve this, the classgroup info will be fetched from its key - looking up Class map using the constructed class name will give the actual History Class name.
SR-124198 · Issue 184897
Clarified messages for attachment deletion failure
Resolved in Pega Version 7.1.8
When trying to delete an attachment on the work item without proper authorization, the tracer shows a message being added on TempAttachmentPage in Work- DeleteAttachment activity reading "You are not authorized to delete instance DATA-WORKATTACH-FILE ATPEGA-TASK ". However, this message was not being propagated to the screen and the screen was refreshing as if it worked despite the failure. To clarify the actual results, the DeleteAttachment Activity has been modified to present any messages and to avoid page removal of the TempAttachmentPage and TempLinkPage if there is a message.
SR-124206 · Issue 186503
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
SR-124232 · Issue 185697
Addressed issue with Advanced Notes attachments reopening the work object
Resolved in Pega Version 7.1.8
When a user attaches a note using the "Advanced" option, as part of the out-of-the-box activity it is recreating/retrieving the work object back from the database and causing any changes to the work object done prior to attachment to be lost. The issue was that the SaveNote activity InsHandle parameter was set but the PageName parameter was not, and the system would reopen the workobject assuming it was not in the workobject context. To solve this, the PageName parameter is now set in the SaveNote activity so that the AttachNote does not do an open of the workpage.
SR-124242 · Issue 186908
Resolved deletions issues for tables mapped to shared classes
Resolved in Pega Version 7.1.8
When a class in a tenant was mapped to an external table and the tenant was deleted, the tenant deletion caused the external table to be dropped/deleted as well even though there was a class in the shared layer that was mapped to the same external table. To correct this, tables mapped to shared classes are not deleted during tenant deletion if there is a tenant class mapped to the same table.
SR-124245 · Issue 188290
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
SR-124313 · Issue 190024
FCM remote case type function restored
Resolved in Pega Version 7.1.8
FCM (Federated Case Management) has a button to discover remote case type, but attempting to use it out-of-the-box generated the error "Remote System is not available. Please check the settings". This was due to a lack of authentication in the Service HTTP rules CaseManagement, and the authentication requirement has been removed.
SR-124385 · Issue 187273
Clicking checkboxes smoothed for Bulk Processing
Resolved in Pega Version 7.1.8
While performing Bulk Processing, if the checkboxes used to select items for processing were marked in rapid succession, not all of the selected items were processed by the bulk action. This was due to the timing of the refresh on the boxes, and this has been adjusted so all boxes are refreshed by a refresh list instead of post value process.
SR-124385 · Issue 193689
Clicking checkboxes smoothed for Bulk Processing
Resolved in Pega Version 7.1.8
While performing Bulk Processing, if the checkboxes used to select items for processing were marked in rapid succession, not all of the selected items were processed by the bulk action. This was due to the timing of the refresh on the boxes, and this has been adjusted so all boxes are refreshed by a refresh list instead of post value process.
SR-124477 · Issue 187138
Logic updated for Ruleset Refactor - Merging Ruleset
Resolved in Pega Version 7.1.8
When using the rule set refactor wizard to merge the rule set from lower version to higher version, the wizard did not show the rules in the source rule set on the second screen (Rules Impacted are "0") which had a number of rule conflicts. In addition, the error "StringIndexOutOfBoundsException" was logged. This was caused by the RuleSetMaintImpl buildRuleSetInventory method not filtering out data instances correctly, causing errors when trying to validate a Data instance as a rule. This has been corrected.