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

Question

Question

Configure folder to not allow locking? Or allow WF to move a locked entry?

asked on October 30, 2020 Show version history

Hi! I'm on version 10 of on-prem Rio.

Is there a way that I can configure a folder to not allow entries within to never have a Lock on them?

If not, is there a way that I can allow locked entries to be moved into other folders via workflow?

 

I have a workflow terminating because it's trying to move an entry into a folder but it can't because the entry has a lock on it. So I guess I just want the entry to be able to move even if it has a lock on it.

 

IDK. HELP?!

0 0

Replies

replied on October 30, 2020

The Laserfiche server is the one handling locking and some actions are not possible without locking. However, Workflow retries on "entry locked" errors. Can you give us more info on what you're actually seeing?

 

0 0
replied on October 30, 2020 Show version history

The workflow only fails once it gets to my "Move Entry" activity, and the warning message says that the entry is locked (see screenshots), thing is, though, this only happens sporadically with this workflow, and I can't figure out why it only terminates like this sometimes.

Also, something else that's confusing, you'll see that an error is occurring on, what it says, is the activity "ISBidRequest", but that's not even an activity in the workflow . . .
Not sure if that's just saying the whole workflow itself is terminating? The name of the workflow is "IS - Bid Request"

 

0 0
replied on October 30, 2020 Show version history

Hi Addison,

I've sometimes run into this when documents are coming into Laserfiche from Import Agent or QF Agent. I don't know if Laserfiche is working on OCR, generating pages, or just isn't finished importing the document, but Workflow will try to act on it while the entry is still locked by the service account running Import Agent or QF Agent.

Without exploring how your documents are coming into Laserfiche to see if something is weird there, one thing you could try is adding a Try Catch activity to your workflow and put your Move Entry activity in the Try branch. If it fails, the workflow will move to the Catch branch, and what I've done in the past is put a Delay activity there to let Laserfiche finish up importing the document, and then a copy of the original Move Entry activity after the Delay. It's definitely just a workaround, and I'd recommend trying to find out why exactly these entries are being locked, but if you can't nail down why this is happening, this has worked for me in the past.

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

Sign in to reply to this post.