We have a client with a large and complex set of workflows. They are having occasional issues where routing of a folder won't occur because a document inside the routing folder is open; causing a record lock error in the workflow. Does anyone know a way to stop or qualify a starting rule, or otherwise let the initiator know; that they have a document open inside the target folder and they need to close it before triggering the workflow? Is there a Search attribute that tells if a document is open or not?
Question
Question
Replies
I am surprised it produces an error in your workflow. I thought that when something is locked, workflow will halt until it is unlocked.
If it is actually throwing an error, you would want to use a Try Catch around the routing object, the catch branch will run, on error, where you can perform some action, like updating the Business Process pane with information letting the user know what they need to do.
Workflow automatically retries if a document is locked. Is there a reason why this behavior is not sufficient?
The customer is wondering If there is a way for his operators to realize they have docs open inside a routing folder before they approve it for further routing. Not sure why it isn't picking up when the doc is closed except it may be an electronic document and they close the Laserfiche interface before they save the doc and it leaves it locked.
The best way to communicate with the users, when a workflow is running, is by publishing the workflow as a business process and updating the business process status. This way they can use the Business Process pane in the client to always know what is happening with their workflows.
Thanks, I'll give that a try.
A good idea that I would have used a lot over the years is for there to be a workflow item that sent the initiator through a pop up window (or something) a message. We could do it through email, but it would be better to have it jump up in front of them after they are expecting a workflow to do something. We could build that into a workflow when we needed either input from the user or just to notify him/her of either an issue or a status. The BP is useful, but it requires the user to actively go looking. In my experience that may be too much to ask.