Workflow to not run based on field changes

asked on October 10, 2016 • Show version history

Is there a way to not run a workflow if there was a change made to a certain field? My situation is that workflow is configured to send an email notification that a case is ready to be worked on based on defined starting rules (status values, user name, doc types, path etc.). Right now it is sending the email notification if there is an update made to a Comments field within the metadata. I want to configure this so that workflow does not run if there is a change made to that Comments field. This should be true whether there is a value in that field or not.

Any ideas would be greatly appreciated. Let me know if you need more information.

0 0

replied on October 10, 2016

You should be able to do this by modifying the starting rules. Can you show a screenshot of what the current starting rules are?

0 0

replied on October 10, 2016

0 0

replied on October 10, 2016

This is a screenshot of our TRAIN environment but has essentially the same starting rules.

0 0

replied on October 10, 2016 • Show version history

Ah, I was wrong, I see what you mean now. Yeah, that's a tricky situation. Unfortunately I don't think it's possible to exclude changes to a particular field in the starting rule.

Here's one idea: instead of this short Workflow that is triggered on an entry change, you could create a more long-term Workflow (perhaps making it a Business Process at this point) that is triggered upon the folder's creation and tracks it throughout it's lifetime. This way, you would be able to use the 'Wait for Entry Change' activity, which has the ability to set conditions of the form "FIELD_NAME has changed". Using that, you'd be able to specify that an email should be sent only when one of the "status" fields changes.

0 0

Question

Question

Workflow to not run based on field changes

Replies

Sign in to reply to this post.