TeamSite: Saving a DCR or .Page - Unlock File Automatically

Hello, when saving a DCR or .page, is there a way to unlock the content automatically? If so, this would display the content as modified and version as X+. I know that you have the ability to unlock and lock files manually; however, often my users leave the files unlocked and don't publish immediately (sometimes for days). Please let me know if this is possible. We currently are using the Submit locking model.

Find more posts tagged with

Comments

jleahy77

Also should mention we are on Version 7.3.2.0.0

Rick Poulin

I'd reconsider that use case. If a user keeps the lock on a file, one could assume that they're "not done" making changes. If you unlock something, it becomes a little too easy for another user to come along, make and publish changes, and accidentally publish unapproved or otherwise unfinished changes to the public.

That said, if you still want to go ahead, you have three options:

1) FormsPublisher allows you to hook into the onSaveDone event, which you could use to trigger a process that unlocks that DCR. This won't work for .page files though.

2) Use iwat to hook on the ModifyFSE event. This would apply to all files in all of TeamSite, not just what you strictly consider "business content". Read up on this in the guides first -- there's also performance considerations.

3) [my recommendation] spawn a Java thread via the Spring lifecycle and have it run every [some configurable time interval], looking for files that have been locked for longer than [some other interval]. For example, you could have this run nightly, thus guaranteeing that files are never locked for more than one day and limiting the potential weirdness of unlocking something while the user still has it open.

jleahy77

Hello, thanks for your response! We have a limited author base and it's a requirement for them to have the unlock feature. I understand the risk of overwriting content and it concerns me that the unlock feature is available to them. Typically no user leaves a DCR or .page open. What they do is edit, save, and don't publish. As a result, the content remains locked. To build the functionality into the the save would limit the risk and would be much to the delight of my users. You did mention the option of the ModifyFSE event. Where can I read up on this?

Google mapWorking.rptdesign

Ramji_bangladesh.csv

nipper

Look up the iwat triggers, you will need to extend them for the ModifyFSE (file system element) action. There is one for CreateFSE and that would be a good template to use.

I would probably go with the FormAPI to unlock, that would be the easiest. I am not certain that Rick's concern about SitePublisher is valid (other than inline editing).

You can also use the tool the way it was designed. On save, initiate a workflow that will unlock, submit and/or deploy.

Rick Poulin

nipper wrote:
I would probably go with the FormAPI to unlock, that would be the easiest. I am not certain that Rick's concern about SitePublisher is valid (other than inline editing).

I'm just saying there's no FormAPI in SitePublisher page editing, so this option only helps you with DCR locks and not .page locks.

nipper

rpoulin wrote:
nipper wrote:
I would probably go with the FormAPI to unlock, that would be the easiest. I am not certain that Rick's concern about SitePublisher is valid (other than inline editing).
I'm just saying there's no FormAPI in SitePublisher page editing, so this option only helps you with DCR locks and not .page locks.

My bad, I read the DCR part but not the .page

AUtostarting of a WF to unlock would not work for SP pages either, only DCRs.

jleahy77

Thanks... I would like to clarify that we are creating DCRs, publishing, and then deploying to a .page that gets published. I need to determine the easiest way to envoke the unlock upon saving and closing out of each. Being that the authors don't publish immediately the lock is rather frustrating and creates havoc, as the users are unlocking the content manually. I understand that the submit workflow and even the manual unlock performs this task; however, there has to be a way to build a custom button that handles the unlock (ie save and close button). If this cannot be done easily, I would like to investigate the other Java option via Spring that was mentioned.

Ticket_2717 -int0.pdf

Adam Stoller

One option that hasn't been presented here is that you create a custom role - based on Author, but with the added ability for the users to unlock files locked by others - and then you change all your role assignments from "Author" to this custom role (e.g.: "PowerAuthors").

If you do that, you don't need to worry about iwat trigger scripts, nightly process runs or the like - you just need to train your users that when they come across a file locked by someone else they should (a) first try to contact the individual who holds the lock, to see if they're still working on the file and then (b) assuming the file is not being actively worked on or they are unable to get in touch with the lock holder - select the file and use Actions > Unlock.

jleahy77

Thanks, but our authors already have the ability to unlock each others content. I am trying to find a way that automatically unlocks the files upon save without the author having to do anything but save and close.

Ticket_2707- extrem Problem.pdf

Adam Stoller

jleahy77 wrote:
Thanks, but our authors already have the ability to unlock each others content. I am trying to find a way that automatically unlocks the files upon save without the author having to do anything but save and close.

Okay - then the two mechanisms already mentioned (iwat and nightly daemon) are probably your best bets. iwat would be automatic, but could be a performance issue; nightly daemon should be less of a performance issue, but it wouldn't be automatic.

Nitish

The file locking mechanism that we have in Teamsite. Can you please tell me where is it ? I am facing one issue, where if some one edits a file, that file wont be in lock unless it is saved. I am using TS 7.4

Thanks

Nitish