question Flow Trigger Based on Specific State Transitions in Change Request in Community Central forum

Flow Trigger Based on Specific State Transitions in Change Request

ThanigaivelS363 — Thu, 21 Nov 2024 03:37:25 GMT

I am working on a flow that should trigger only when the State field of a Change Request transitions between the following values:

New

Scheduled

Implement

Review

To achieve this, I set the flow trigger to Record Created or Updated and configured it as follows:

State is New

State changes to Scheduled

State changes to Implement

State changes to Review

Run Trigger: For every update, Only if not currently running, For every unique change

However, I am encountering an issue:

The flow gets triggered on updates to other fields on the form (e.g., Description), which is not my requirement.

Requirement:

The flow should trigger only when the State field changes, and not on updates to other fields.

Is there a way to configure the flow or add conditions to ensure it only triggers on State field changes?

Re: Flow Trigger Based on Specific State Transitions in Change Request

Community Alums — Thu, 21 Nov 2024 04:54:09 GMT

hmm based on your flow trigger that shouldn't be happening. Is there anything with the change request fields that triggers a state change when updated?

Re: Flow Trigger Based on Specific State Transitions in Change Request

Ravi Chandra_K — Thu, 21 Nov 2024 05:15:32 GMT

Hello @ThanigaivelS363

Go to audit of the Change request and See if State values are getting changed along with other values.

Please mark the answer as helpful and correct if helped.

Kind Regards,

Ravi Chandra

Re: Flow Trigger Based on Specific State Transitions in Change Request

Runjay Patel — Thu, 21 Nov 2024 06:14:55 GMT

Hi @ThanigaivelS363 ,

If you have properly configured the trigger then it should not happen, may be state is changing and again setting back to original state. Share the screen short of your trigger condition.

Do check audit history of state for the record which you thing flow should not trigger but it was triggered.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------