You are viewing limited content. For full access, please sign in.

Question

Question

Open document stops workflow

asked on November 8, 2017

We have a process in our office that deals with building applications and building permits. The applications will be submitted and processed which brings it to the permit being issued. The operator will open the application to get the necessary information to create the permit. I am having an occasional issue with my one workflows being terminated when the operator forgets to close the application before saving the permit to Laserfiche, which starts the workflow. The workflow is programmed to move the entire folder that holds all the related documents and the new permit to an archive folder. The workflow terminates with the following message:

Route Entry to Folder "Archive"
(MoveEntry)Multistatus response. [9039]
Another operation on which this operation depends failed. [9054]
Entry locked. [9014]

My question is, is there a method that can be inserted into the workflow that closes the application or pauses the workflow until the application is closed?

Thank you

0 0

Answer

SELECTED ANSWER
replied on November 8, 2017

Here is an example of using the other method, a 'Try-Catch' block.  You set the delay in the catch activity to whatever you want time-wise, and then it will try again.  You can also loop these blocks inside each other if necessary for multiple tries.

 

1 0
replied on November 9, 2017

I like the 'Try-Catch' block for this workflow and will give it a try. I thank you for the reference to both methods. If the 'Try-Catch' does not work for this one, I will be testing the retry time. Thank you for the help.

0 0

Replies

replied on November 8, 2017

Duane,

You can setup a 'Retry time' in the Workflow Admin Console, which will effectively wait a specified amount of time and then retry the activity.  For this error, code #9014, you could set it up like this to wait 5 minutes ( or longer if you set that way), and then retry.  You would go to the console, choose 'Server Configuration', then 'Task Error Handlers'....on the right side of the screen you will see the 'Add..." link.  Click that and you will get a window like the following I have already filled out:

 

You can do this for many similar errors as well.  Another way to handle is is with Try-Catch activities, and a repeat sequence.

 

Rick

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.