Uploaded image for project: 'Alfresco One Platform'
  1. Alfresco One Platform
  2. ACE-5149

Need a dialog when deleting folders containing synchronized content

    Details

      Description

      Story
      As a user of hybrid sync between Alfresco on-premise and Alfresco in the cloud, If I delete a folder that contains synchronized content, I should be asked whether that content should be removed from Alfresco in the cloud. If I am in Alfresco in the cloud, and delete a folder that contains synchronized content, I should be notified that the content that is going to be deleted is synchronized from on-premise, but I should not be given the option to delete on-premise. In no case should deleting content result in an invalid synchronization being left.

      Acceptance Criteria

      • When deleting a folder that contains synchronized content on-premise, a dialog should appear notifying the user that the folder contains synchronized content. The paths to the folders containing synchronized content should be displayed. The user should be given the option to delete the content locally, delete the content locally and in the cloud, or to cancel.
      • When deleting a folder that contains synchronized content on-premise, a dialog should appear notifying the user that the folder contains synchronized content. The paths to the folders containing synchronized content should be displayed. The dialog should explain "This action will not delete content in the synchronized repository." The user should be given the option to proceed with the deletion, or to cancel.

      Notes

      • This scenario is exactly the same as that described in MNT-15624 except that the folder being deleted is not synced to the cloud, rather that folder may contain 0..n descendent files or folders which have been synced to the cloud.

      Questions

      • How should we perform a pre-check to determine how many such synced files or folders there are?
        • A naive implementation would be to walk the file and folder tree and count the numbers of synced nodes, but this would be potentially very expensive due to the unbounded depth.
        • Another approach: when a synchronization is configured, label all the content in the affected folder tree with a property indicating that it is synchronized. This makes the initialization of a synchronization expensive, but it is asynchronous to the user. Resulting operations can update whether it is synchronized just by looking at the parent folder.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedissues Closed Issues
                  Reporter:
                  nmcerlean Neil McErlean [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel