The lock propagation feature allows you to configure if lock status for files on the source will transfer to the destination with the same setting; assuming the destination platform supports it.
Lock Propagation (ignore)
- Lock status for files on the source will not propagate to the destination
Lock Propagation (mirror_lock)
- Lock status for files on the souce will propagate to the destination
Lock Propagation (mirror_owner)
- Lock owners on the source will propagate to the destination
Only Box has full support for Lock Propagation (mirror_owner)
Office 365, SharePoint 2010-2016, OneDrive for Business support reads but not writes which means only when these connectors are the source and Box is the destination, is Lock Propagation (mirror_owner) fully supported.
Supported Platforms
- Box
- Office 365
- SharePoint 2010-2016
- OneDrive for Business
- Documentum
- Huddle
- OpenText
Example Scenario
Create a connector for Box and Office 365
Create a new job with the specified lock propagation setting
On the source connector (i.e. Box), create a folder with one or more files and lock them
- Right click the file on Box and select option "Lock"
- Folders cannot be locked on Box
Execute the job (i.e. Box to Office 365) and verify that the files are copied and the file is locked on the destination side
Expected Results:
- If the setting is Ignore, no locks will propagate
- Office 365 - No green arrow on the file icon
- If the lock setting is mirror, the lock will propagate
- Office 365 - A green arrow will be present on the file icon indicating it is "checked-out" or locked
- If the lock setting is mirror_owner, the lock will propagate and the lock will be under the ownership of the account mapped from the source
"mirror_owner" option requires Account Mapping through User-Drive Mapping
Example JSON
"lock_propagation" : "ignore"
Value Options:
ignore (default), mirror_owner, mirror_lock
|