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

Question

Question

How can one make a workflow work across multiple Forms processes?

Forms Workflow Version 10
Updated May 13, 2019
asked on May 13, 2019

I'd like to re-use a workflow in multiple processes without having to duplicate it. Is there any way to configure the Set/Retrieve Business Process Variables activities so that they'd work with any process with the same variable names?

Laserfiche Forms Professional Version 10.3.1.635

0 0

Replies

replied on May 13, 2019

We had the same situation here and we managed to do it by having the different Forms calling the same Workflow in their process.

Each Forms have a unique ID in the input parameters (Form ID) so you could have a routing decision with a branch for each Forms ID in the Workflow and then configure a Retrieve Business Process Variables in each branch for the specific Form.

Hope my explainations were clear.

Regards

 

1 0
replied on May 13, 2019

To add to this, if you have any tasks that need to be dynamic (i.e., routing a document based on information included on the form) then you'll want to create Tokens, assign form values to the tokens in the branches, then use the tokens in the shared/dynamic activities.

Basically, instead of creating duplicate activities, you can use tokens for dynamic values and reuse some activities regardless of which form started the process.

0 0
replied on May 13, 2019

Thanks, guys--I was just hoping for a solution that didn't require modifying the workflow for every process.

I'm sure it's using the attribute id under the hood, but it'd be nice to not have to repeat "if ProcessA, set FieldX =1; if ProcessB, set FieldX = 1; if ProcessC, set FieldX = 1..."

0 0
replied on May 13, 2019

The best you'll ever be able to do is have 1 workflow with branches for each Forms process.

You have a token, for example "FieldValue"

Within each branch (based on the BP ID or BP Name) you get the appropriate value(s) from the form, and assign it to your FieldValue token(s).

Then at the end of the Workflow after the branches, you set FieldX = FieldValue

 

Although you have to modify it each time you add a new form process, all you would do is add another branch that does the same thing.

Keep in mind Workflow needs to register these variables so you'd have to republish even if you renamed a variable on an existing form, and it would have no way to identify values on a new process it had not yet registered.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...