Question

Overhead for Invoke Workflow

Workflow

Updated March 21, 2016

asked on March 20, 2016 • Show version history

We have a situation similar to the one discussed in this thread:

http://answers.laserfiche.com/questions/61435/Feature-Request-Subroutines-in-Workflow-

To summarize, the request was to create a sub routine structure, vs. using the Invoke Workflow task. For me, Invoke Workflow does act nicely as either a sub or a function.

We have a very simple task that has two steps. I'd rather create it once and call it many times, than to embed it into multiple workflows. The question is, what is the overhead of Invoke Workflow, vs. adding two steps to an existing rule?

Here are the steps - note that we do not need and will remove the first one, Find the Parent Folder. Search Entry does that all by itself.

0 0

Answer

SELECTED ANSWER

replied on March 21, 2016

In general, using Invoke Workflow will increasing processing speed, since it allows you to take advantage of multiple CPU threads. In this case it seems like you're running the same exact process slots of times, so it seems like it would be very helpful.

This approach will have more workflows running, so there will be a bit more database bloat. You can solve this issue by setting your workflows to be automatically deleted after a period of time in the Workflow Administration Console.

2 0

Replies

replied on March 21, 2016

Thanks, Kevin, for the background and the adjustment we'll want to make on the DB side.

0 0

You are not allowed to follow up in this post.

Question

Question

Overhead for Invoke Workflow

Answer

Replies

Sign in to reply to this post.