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

Question

Question

Efficient way to do branches in workflow

asked on November 26, 2014

I have a workflow where I have a routing decision activity. I have multiple branches where depending on some conditions, I am routing the entry. Is it possible to replace the routing decision with a for each activity or something so that I dont have to add 20 different branches in my workflow please? Thanks.

 

Priya

0 0

Replies

replied on November 26, 2014

Any place where you have repetitive actions based on field values.

For example, say you have a Document Type field that says "Invoice", "Purchase Order", etc. and you route these documents to a folder corresponding to the type: \Some Path\Invoices, \Same Path as before\Purchase Orders, etc. In that case a single Route to Folder activity using the field token ("\Some Path\%(Fields.[Document Type])s") would eliminate the need for "if invoice, route to invoices folder"-type branches.

The same would apply if you want to send a document to a user that is picked by the workflow initiator through a field value in the Laserfiche Client.

1 0
replied on December 1, 2014

Thanks.

0 0
replied on November 26, 2014

A routing decision is the more efficient way to send your workflow through different paths based on conditions because branches will be checked until a match is found. A For Each activity will execute all iterations regardless of whether it already found a match.

There is no one size fits all approach, it depends on the conditions. You could break them into individual workflows and set them up with their own starting rules. Or you could group them into smaller workflows. Or you could nest them if not all are applicable at the same time. Or maybe tokens could be used to reduce the number of branches.

0 0
replied on November 26, 2014

Thanks. Can you please provide an example where I can use tokens to reduce the number of branches please.

 

Priya

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

Sign in to reply to this post.