Question

Starting Rules based on Specific Field

Workflow Version 9

Updated October 13, 2016

asked on October 12, 2016

I have seen a number of posts asking about workflow conditional starting rules and if they can be based on a specific field. All the posts were at least a year old.

Does anyone know if there have been updates to starting rules or a "trick" around it to recognize just a specific field? It is not a case of empty or not empty so I can't base the rule on that or put anything in the workflow to check that first. I am currently using Workflow 9.1 and we are about 4 months away from being able to upgrade to 10.1.

Specific case use: I have a template for information on litigation holds. Many of the fields on this template are changed throughout the course of the hold. One of the fields is a multi-value field of email addresses. Since specific emails need to be sent when emails are added or removed, I would like the workflow to only start when the email field changes.

Thoughts?

Thanks.

0 0

Replies

replied on October 13, 2016

There is one work around i could think of. First create a workflow that includes this starting rule

Next, in your workflow, store a DB Table with Entry ID's and email addresses of multi value token, Next match current retrieved values with what's in DB. If there are any extras send emails to those and update DB.

0 0

replied on October 13, 2016

Thanks but that is not quite what I am looking for. What I am trying to do is trigger the workflow only if the email field is changed. And not trigger it if they change fields like case status or assigned counsel.

0 0

replied on October 13, 2016

Hi Jennifer and if you try this

01 Wait for the filed email full
02 Include a repeat node
03 Retrieve the email
04 Send the email
05 Wait untill an other change

and this workflow starts with your entry untill maybe the status does not equals to "Over" or finish or if you know how many times can change, you can put on the repeat that value

Hopes that work for you.

Regards.

0 0

replied on October 13, 2016

Thanks Junaid and David.

We had a wait in there before and I have 4 instances of the workflow that have been "waiting" for almost 2 years now. That is why I am trying to rework it to get rid of the wait. The email is filled is as soon as the document is created.

I ended up just letting it start with every field change. But put a "stop/go" in the beginning that compares 2 fields. If the comparison shows that the email field is what changed, it goes onto the rest of the workflow. If it shows a different field was changed, it terminates the workflow.

0 0

replied on October 13, 2016

Hi Jennifer I understand your feeling about the wait.

But what if we try the following :

A deadline that have an ending every or week that terminates your workflow and start a new one.

You will have workflow with a week of life time.

its work this option better for you?

But at the end you call a workflow that starts all again.

0 0

You are not allowed to follow up in this post.

Question

Question

Starting Rules based on Specific Field

Replies

Sign in to reply to this post.