OnGenerate wanted to clear the lock on the output file

Anil Kumar

Hi,

 

I've implemented a DCT with a presentation template which generates a HTML out of each DCR of that DCT type. Everything works well.

And User-A open test.xml(DCR) and updates content and generates output to WORKAREA/DCT/test.html

next time When User-B opens test.xml(DCR) and updates content and tries to generates output to WORKAREA/DCT/test.html and it throws a warning that the file is locked.

 

Is there a way to unlock the file after generation or can we do submit on that output file.

 

Using Formpublisher 7.3.1

 

Regards, Aneel

Adam Stoller

There are at least three ways to unlock the generated file:

1. Navigate to where the file is, select it and choose Actions > Unlock
2. Navigate to where the file is, select it and choose Submit - though you may have to decide what workflow to use when you do so, if there's more than one choice.
3. Submit the DCR - assuming you have a reasonable architecture and workflow that knows to include the generated file (or regenerate it as part of the process flow and attach the generated file to the workflow) - when the workflow completes, the file should be unlocked.

 

A lot depends on whether the first person's changes were supposed to get published before the second person's changes.

 

You might be able to put an iwat trigger on the generate process (not looking at a server right now to determine if there is an event to latch onto), in which case you wouldn't have to worry about it.  You can read more about iwat in the CLT manual (if you don't have the CLT manual you should get it downloaded from the Support site - but you may have to go through several different version directories to find it [sigh])