Versions - Lock or not to lock that is the question

[quartusconsult]

Good day all,

As part of our document control process we lock versions of documents once they have been approved and published. Although this has been great to ensure versions of document are never lost, we just noticed that locked documents can only be unlocked by the user who locked them. This concerns us as if one of us leaves the organization all the files we locked will need to be unlocked by an admin.

Do any of you make it part of your document control process to lock versions of documents? If so, how were you able to get around this issue?

Thanks for all your input.

We are using Livelink 9.7.1

 

[appnair]

You can create a "Generation" from a version if it is to prevent accidental deletion.Although most operations in livelink can be overridden by System administrators and EP (Edit Permission) holding others,some dangerous operations in RM.Locks and hidden only go upto a certain level of accidental erasure.I use Locked versions when I m doing something that I regard as stable.Say I am creating a customview.The Lock to me will say that while I was developing that version 43 that I locked is a stable version so when I do purge versions all unwanted things will go so if I find version2,version12,version 12345 is a visual cue to me that says my stable versions progrssed over time....
Pls give your opinion even if it is to differ from my view.This forum is fast becoming a place where people will seek advice and then run with it without even bothering to so as to say if the advice helped or messed it up.I saw your post as soon as it came was contemplating whether to post or not


Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in