Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-522

Document locking / unlocking should be taken into account by Drive

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.120
    • Component/s: Synchronizer
    • Sprint:
      drive-8.1-3

      Description

      Just like when denying / granting the Write permission, locking / unlocking should set / unset the readonly flag.

      This requires the "documentLocked" and "documentUnlocked" audit events to be sent by GetChangeSummary, see NXP-18732.

        Attachments

          Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. NXP-18732 Lock / unlock events are not detected by GetChangeSummary

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. NXDRIVE-470 Locked document are overwritten if modified locally

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is required by

          Bug - A problem which impairs or prevents the functions of the product. NXP-11165 Locking a document server-side should prevent another user from updating it client side

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. NXDRIVE-248 Editing a locked or a readonly document: should display feedback

          • Major - Major loss of function.
          • Resolved

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: