We are having a workflow issue that I suspect may be around document composition.
Our scenario is this:
User clicks an Ad Hoc Task Button, this then calls the Compose Document action to create it via Synchronous Processing. The next workflow action after that is to print the document. So, the next workflow step should not occur until the document completes since it is set to synchronous processing.
This all worked perfectly fine.
We then needed to set the template to "Always show Preview before archiving" as users needed to add some variable information before saving it. Once we did that, whenever users would enter the data into the prompted template and click "Accept," we would frequently see that nothing was sent to the printer. Almost a 50% chance.
What I've seen when we have this preview before creating the document, upon clicking Accept, it switches back to the OnBase client with the upload dialog box. The workflow action is still set to Synchronous Processing even though we are allowing them to make changes before accepting.
My question is, is it still guaranteed that the workflow actions will not continue until that upload is complete? My theory is if it doesn't wait until that upload is done when doing it through this scenario, that the workflow action is continuing on to the print step, but if the upload didn't complete, it would be trying to print nothing -- which would result in nothing in the printer queue.
Any ideas?
