One of our clients decided to have the template automatically generate the page via FormAPI every time the DCR is saved (including the first time - so they are suppressing the regen prompt and running a server call to do the generate). I pointed out to them that if they do that, they really need to lock the page they are generating, otherwise they are going to run into conflicts where a second person could attempt to edit the generated page, since it won't be locked until the workflow task that regenerates the file attaches it to the workflow. Their developers added the locking, but now the externaltask in their workflow that generates pages for attached DCRs fails to attach the generated file because of that lock. I'm not undersanding why, because the lock is held by the owner of the externaltask and it isn't a workflow lock.[...]Any thoughts?
