nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

how to lock working copies

vinhqchu

Shouldn't working copies be locked to be editable only to the person who checked it out? I've come to realize that when user A checks out a document and has the working copy created on the same space, that other users can come in and edit the working copy while user A is editing it also. This is all through CIFS. I checked the permission of the working copy and it inherits from the parent space. This seems to be a flaw in the system. Is there a fix for this?

Regards,
Vinh Chu

Find more posts tagged with

Comments

zaizi

In Share if you edit ms office documents online using Share point services, it locks the document while you are editing the working copy.

vinhqchu

thank you for your reply, but what about explorer? shouldn't explorer lock it also? can this be fixed?

fantom18

Hi All,
I have the same problem, please help us.
Thank you

livcg

Same problem here. Any suggestions on content rules or something that we can set up to work around this?

Thanks

livcg

I discovered that in our case a document's creator was able to edit a working copy of the document even if s/he wasn't the one who checked it out. This is because in permissionsDefinitions.xml, ROLE_OWNER has a global permission giving it FullControl. If a document doesn't have an owner property, the creator property is used.

I tried to get around this by restricting the permission for ROLE_OWNER but wasn't successful. In the end, I added a content rule to add the aspect ownable to all content. This adds a blank owner property to content and removes full control from the creator. I believe another way to do it is to add the ownable aspect to the model in configuration, but I haven't tried this. I also have to think about restricting the Take Ownership ability.

Hope this helps someone else.