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

Question

Question

Field Change Triggers Workflow

asked on September 18, 2014 Show version history

I have a template with multiple fields, one of those fields is named "Closed" with a list of "No" "Yes"

 

Those with a closed "Yes" field have a document destruction date applied via another field.

 

If that field changes back to "No" by someone changing the field manually on a document in a specific folder, the destruction date needs to be cleared out.

 

How can I trigger workflow to kick off and do this?
 

1 0

Replies

replied on September 18, 2014 Show version history

This would just be a standard condition for an Entry Changed where Entry Field "Closed" equals No and Entry Field "Destruction Date" is not empty.

 

Don't forget to add a condition for User does not equal Workflow User

1 0
replied on September 18, 2014

Nevermind, I've figured this one out.

 

 

replied on September 18, 2014

Sorry I'm new to workflow - What would the purpose be for "User does not equal Workflow User"

 

I actually set it up like this

 

Starting Rule with 3 conditions:

Entry Changes: Include Template Field Set

Entry : Field equals NO

Entry Path equals \path to documents\

 

The workflow is very basic as well

Wait for Entry Change

Assign Field Values  (clears destruction date field)

0 0
replied on September 18, 2014 Show version history

That should work but you may want to verify the entry destruction date is set to prevent unnecessary runs.

Excluding the Workflow user prevents endless loops. With your current logic the workflow will see the entry fields were changed, clear a field, see the entry fields were changed, clear a field, see the entry fields were changed, well you get the idea. It will do this 10k times before reaching the limit specified in the administration console. 

It is best practice to exclude the workflow user on any Entry Changed event even if your not sure.

 

Oh, also remove the Wait for Entry Change activity, otherwise your workflow will wait for an entry change AFTER the entry change that met the starting conditions. Instead you can put a conditional sequence with another condition just to confirm the field is set to NO.

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

Sign in to reply to this post.