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

Question

Question

«Simple Synchronization Sequence» Activity vs. Read-only Accesses to Locked Entries

asked on January 16, 2014 Show version history

Hello,

 

I intend to make use of «Simple Synchronization Sequence» activities in order to decrease latencies caused by accessing locked entries.

 

Do I need to care about read-only activities («Retrieve Field Values» for example)? In other words, do I need to move those in «Simple Synchronization Sequence» activities?

 

Lou

0 0

Answer

SELECTED ANSWER
replied on January 17, 2014

Thank you to remind us yes the performance issue with the activity 

0 0

Replies

replied on January 16, 2014

I think you are misunderstanding the point of the Activity. It will actually not work like how you think. It's only going to add a small delay and if it takes longer than a minute it will go into that sequence of events without care of any other workflow running using the same ID on it's Simple Synchronization Sequence. You will need to be very careful about what you are doing when using this activity.

 

In terms of the original question, I do not believe that the Retrieve Field Values activity locks the file, so you should not have to worry about that. 

 

If you are worried about activities failing because of a lock, you might want to introduce a Try-Catch activity and then use it within a Repeat activity and using tokens to control if an activity repeats. This will allow you to catch when an error occurs when you try to access a locked document. 

 

It likely does not increase any speed but it does allow you to handle the errors you are likely encountering.

0 0
replied on January 16, 2014

Hello Kenneth,

 

The behavior described in your response's first paragraph is not consistent with Laserfiche's Web Help Page.

 

The Try-Catch activity is effectively usefull if the task handler for locked entries (that is, error code 9045) exceeds tasks' retry timeout period as defined in Workflow Administration Console. In case of competing workflows (either instances of distinct), someone may assume that delay will never be exceeded if workflows are architected to prevent such a situation to occur.

 

I will be happy you and other people contribute further to this post given the importance of the issue in complex workflow environements.

0 0
replied on January 17, 2014

Retrieve Field Values does not need to be in a synchronization sequence. Only activities that would potentially lock the document, like Assign Field Values would need it.

 

I would also only add the Simple Synchronization Sequence in just the places where you have noticed "entry locked" warnings in the past, not to all activities. It is an in-memory lock, so it could affect the performance of the workflow if used excessively.

0 0
SELECTED ANSWER
replied on January 17, 2014

Thank you to remind us yes the performance issue with the activity 

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

Sign in to reply to this post.