Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Creating a flow in Flow Designer with field values and tasks

rdskn023ET
Tera Contributor

Hi,

 

I am looking to get some assistance in Flow Designer when using a field value and completion of demand tasks to perform specific steps. Below is an example. Any assistance you can provide would be appreciated!

 

Field A has the values 1, 2 and 3. 

When Field A is selected with value 1, I need to create two specific demand tasks. Upon completion of those two demand tasks, I need to automatically set Field A to 2, which then creates two new specific demand tasks. The same will happen for Field A value 3. 

 

That part is easy when it is linear, but the complexity comes when we open up Field A to be selected in any order. Therefore, someone could select 2 in Field A first, which would create the two demand tasks. Once those two demand tasks gets closed out, it would set Field A to 3 and create two new demand tasks. I need to ensure that this functionality works in any order without duplicate demand tasks being created. So a user could select 3 in Field A, then 2 in Field A and then 3 in Field A again, but only have total of four demand tasks created, two for Field A's 2 value and two for Field A's 3 value. Then, at any point they could select Field A's 1 value and have those demand tasks created, again, without any duplication if they were to select a different value and go back and select 1 again. Therefore, regardless of the number of times they selected a different number from the field, there would only be a total of six demand tasks created in any scenario.

 

I hope this makes sense. Basically, the overall picture is to create a flow where a group of actions/tasks could be created in any order without duplicates based on a field's value and/or the completion of those tasks that were created. 

 

Thanks in advance for any assistance. 

6 REPLIES 6

I took a different approach in the automation portion. I used the run once like you mentioned, but created several business rules to change Field A to the appropriate value based on when the specific demand tasks were closed. 

 

Appreciate your insight and help!

Thank you. "Run Once" question was only for my understanding of how your flow was designed. I am glad your problem is solved. Looked like a complex statement.