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; } } }

Edit of locked files?

RonaldV

Hi,

TS552 & Win2k

From the TS manuals & this support item (https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=1471) I understand that "Locks under TeamSite are associated with a workarea,not a user." So I would think that a file locked by somebody else but __in the same workarea__ is editable by me.

However when I try this I get the error "Error: file 'x' is already locked by or addigned to 'id'in workarea 'Y'. Cannot edit the file". Also the file-icon in front of the file show a 'lock' NOT a 'key' (signalling "locked in other WA')

What is going wrong here?

Thanks, Ronald

Find more posts tagged with

Comments

Dwayne

Unless I've got a fundamental misunderstanding going on here, then that article is just plain wrong. to the best of my knowledge, locks are associated with a workarea and a user.

--

Current project: TS 5.5.2/6.1 W2K

Migrateduser

I first noticed this behaviour in 5.0.1, but Adam says it's been like that since the beginning. I think Dwayne's correct - it's a documentation bug. The reasoning behind it makes sense, though - there would be no way to preserve the versioning if they aren't in different workareas.

Adam Stoller

Hmm - this is interesting - and I'm suspicious of it being a documentation bug backed up by a piece-of-fluff KB article (which seems to be pretty much word-for-word from the documentation).

To the best of my knowledge - locks are specified both in terms of workarea *and* userid.

If you are interacting with the files from the file system interface - the locks don't really mean anything and you can make changes to the file even if you don't hold the lock on it.

If you are interacting with the file through the GUI, then both the location and owner of the lock has some bearing (or perhaps this is only when one has only_lock_owner_creator_submit=yes in their iw.cfg file?)

There are also some differences of behavior when the file being locked is a templated asset versus a non-templated asset (or at least there used to be) DCRs tended to be very restrictive of multiple editors whereas non-templated files would usually allow another user to modify the file with a warning that they'd be running into a conflict (this of course was in different workareas).

Frankly, I think the behavior you are seeing is correct and the documentation is probably in error.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

RonaldV

Thanks all,

I'll contact support to see what they say.

In my opinion a lock should prevent users working on a file that is out-of-date since it's modified in another workarea.

But users that modify the latest version of a file should be free to do so even if the file is modified but not submitted by someone else. Specially since users can get sick and then a collegue of them should be able to take over there work.

Any way, let's see what support has got to say.

Ronald