Workflow help. If Status is not x or y then action update record

[phugill]

Hi,

I'm building a Flow in ServiceNow that checks the status of a Task and, if the status is NOT "Closed Complete" or "Resolved", it should update the status to "Closed Aborted". This seams like a simple flow but it isn't behaving the way I expect. 

Here's the logic I was aiming for in the Flow:

If Task Status is not "Closed Complete" OR "Resolved" then Update Status to "Closed Aborted"

The issue I'm running into is that even when the Task is already in a valid end state (like "Closed Complete" or "Resolved"), the Flow still goes ahead and updates it to "Closed Aborted" ...which I don't want.

What I'm trying to achieve:
Only update the status to "Closed Aborted" if the current status is not already one of the acceptable final statuses ("Closed Complete", "Resolved").

Has anyone run into a similar issue?
Am I missing something in how the condition logic is structured in the Flow? Should I be using an AND instead of OR, or a different way of checking multiple values in the condition?

Thanks in advance for any guidance!

[kaushal_snow · Accepted solution]

Hi @phugill ,

** Use a single “Is not one of” condition on the Status field with both Closed Complete and Resolved, this only runs the update if Status is neither of those values. Its availability depends on the field being a choice list. If the UI doesn’t offer “Is not one of” (e.g., on a string field), group two conditions under All (AND):

Status ≠ Closed Complete

Status ≠ Resolved

This correctly checks both mismatches before updating and after that ensure your Update Record  set status = “Closed Aborted” action is placed only on the Yes branch of that condition, if the test fails (i.e. status is already a valid final state), nothing changes.

[kaushal_snow · Accepted solution]

Hi @phugill ,

** Use a single “Is not one of” condition on the Status field with both Closed Complete and Resolved, this only runs the update if Status is neither of those values. Its availability depends on the field being a choice list. If the UI doesn’t offer “Is not one of” (e.g., on a string field), group two conditions under All (AND):

Status ≠ Closed Complete

Status ≠ Resolved

This correctly checks both mismatches before updating and after that ensure your Update Record  set status = “Closed Aborted” action is placed only on the Yes branch of that condition, if the test fails (i.e. status is already a valid final state), nothing changes.

[AndersBGS · Accepted solution]

Hi @phugill,

 the reason is that you’re utilizing am or condition. you should instead utilize is not one of or utilize an and condition. This should resolve your issue.

[DATTA SANSARE]

Please use the AND condition instead of OR, as shown in the screenshot below.
If Task Status is not "Closed Complete" AND" Resolved" then Update Status to "Closed Aborted"