Question

Invoke workflow through scripting

Workflow

Updated October 7, 2014

asked on September 29, 2014

Hi,

I wanted to create a generic workflow that calls other workflows to do work. I was thinking about creating a lookup table in SQL and pass in the Workflow Name and any parameters that are needed. The invoke workflow component doesn't seem to allow me to instantiate workflow names dynamically. Is there a way to do it through scripting?

Thank you in advance for any advice.

Derek

0 0

Replies

replied on September 29, 2014

Is there a gargantuan number of them or something?

Setting a token and using a conditional decision is not a high cpu hit since it's just "does it match X?", "does it match Y?", "does it match Z?", etc. It's tedious to add quite a bit but it's not a high cpu task.

0 0

replied on September 30, 2014

I agree, The easiest way to do this is to use conditionals. That is unless this would require an unreasonable number of branches to be created within Workflow. Here is what the workflow could look like:

0 0

replied on September 30, 2014

Invoking workflows through scripts is not supported. Due to the architecture of the Windows Workflow Foundation and the Workflow Server, starting workflows could actually end up being throttled under load as well as creating unnecessary overhead in the server.

0 0

replied on October 7, 2014

Thank you Miruna. That is what I needed to know.

At the moment there isn't a huge numbers of invokable workflows but I am also building this generic workflow to scale in capacity.

What we want to build is a dynamic document classifier. Figure out what the document is, lookup any relevant changes needed for the Identified document through SQL. (i.e. template changes, workflow, etc..) then fire off the relevant business process.

Now we have to rethink our process a little. Thank you guys for your help.

Derek

0 0

You are not allowed to follow up in this post.

Question

Question

Invoke workflow through scripting

Replies

Sign in to reply to this post.