DCR retains lock after associated file is deployed

I am using templates to maintain several files that change frequently. The problem I am having is that when a users modifies say the index.shtml file, this in turn opens the associated datacapture.cfg file for that page and a lock is placed on the .shtml and the associated templatedata (DCR) file.

The problem is that once the user regenerates the new index.shtml file and deploys it to production, the DCR retains the lock by that user so future users cannot access or modify the index.shtml unless an administrator manually unlocks the file.

I was under the assumpition that the deployment would unlock all associated files, does anyone know that to be the case or must I do something special to force this to occur?

Thanks,

Silvano

Find more posts tagged with

Comments

nipper

no a properly written workflow will do that, and a poor one will not.

kshitiz

I was under the assumpition that the deployment would unlock all associated files, does anyone know that to be the case or must I do something special to force this to occur?

There is no automatic unlocking of files in workflows. You have to explicitly include a task to unlock those files. Haven't you included Submit task in your workflow?

wfd_12508001094a8db1ed968d9--extendtabletofitpage.rptdesign

sumitk

no a properly written workflow will do that, and a poor one will not.

I completely agree with Andy.
You need to have an external task after the successful deployment to unlock files. Basically a script to unlock files. This will ensure that locks are not preserved after the workflow completes.

Sumit.

Adam Stoller

There is no automatic unlocking of files in workflows. You have to explicitly include a task to unlock those files. Haven't you included Submit task in your workflow?

That is not completely true - submittask's have an attribute for allowing all files that were submitted to be unlocked afterwards - it is unclear though whether (from a process standpoint) you want the files unlocked after the submit operation or after a later deployment operation. If the latter - then you need to include your own task for performing the unlocking, which is pretty trivial and IWOV even provides a script in IWHOME/local/bin for doing it (no customizations required - assuming you got all the correct files associated with the workflow)

kaalraa

I am using templates to maintain several files that change frequently. The problem I am having is that when a users modifies say the index.shtml file, this in turn opens the associated datacapture.cfg file for that page and a lock is placed on the .shtml and the associated templatedata (DCR) file.

The problem is that once the user regenerates the new index.shtml file and deploys it to production, the DCR retains the lock by that user so future users cannot access or modify the index.shtml unless an administrator manually unlocks the file.

I was under the assumpition that the deployment would unlock all associated files, does anyone know that to be the case or must I do something special to force this to occur?

Thanks,

Silvano

A Basic question - Are all your files get attached with the running job like DCR as well as .shtml file? Apart from that if deployment is being done by an external task, you need to include iwunlock within.