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

Question

Question

Understanding Starting Rules in Workflow: Created vs Changed

Laserfiche Version 10 Workflow
Updated March 25, 2021
asked on March 25, 2021

Im hoping someone can explain the different starting rule choices:  File Created vs File Changed.

If i am correct, using the File Changed option, can make the workflow run several times.  This is an issue i had with approval of a document.  It was running twice since the file was changed twice.  First time when i was "created" and second time when it was "approved".

This was corrected by changing the Starting rule to File Created.

Anyone else have this experience??? 

0 0

Replies

replied on March 25, 2021

That is exactly right, any change to the document or metadata (including name but not location) is a change event.

Created is only when a document is first imported into the repository.

Also keep in mind that Workflow triggers change events on entries even when it does not make a change, which causes very scary infinite loops that overload your SQL server hard disk. This is why you should always include on change events User != [Workflow Service Account User]

0 0
replied on March 25, 2021

we did have exactly that.  endless loop after dummy me removed the "user not equal workflow"

think i just advanced to intermediate...lol

1 0
replied on March 25, 2021

I think we all run into this once, I thought about the endless loop scenario but didn't realize a Retrieve Field Values would cause a change to the document. The problem is cleaning it up, whatever you do, do not delete the workflow that you ran multiple times or the cleanup of the instances will never happen and your database will be a mess.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...