cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Best actions to create an O365 Nintex workflow that interacts back and forth between users.

I have seen many demos and tutorials showing the basic linear steps of creating a workflow. Unfortunately most are the same example (Time Off Request, Approved/Rejected etc.)

I'm able to successfully recreate these however, I'm getting stuck on how to build out a workflow that instead of just goes from the linear customer-performer process steps; requires actions to pass back and forth between them.

Essentially, what I'm looking to do is create Travel Booking Request workflow that would have a user submit a request with their travel dates and destinations for a trip that would assign a task to a travel coordinator that would then look at available flights options,then provide them back to the Traveler (initiator) for selection.

Once the users picks from the options that would go back to the travel coordinator who would then book the flights and send a confirmation back tot he Traveler.

I think I can accomplish the data inputs in a form but where I'm stuck is how or what actions do I use to do this in the most effective way?

It seems like I would want each task/hand off to have a separate from with functions etc. but I can't seem to figure it out.

Me sense is it's not too different from using something similar to the Approved/Rejected actions and routing but I can't seem to get to work.

What am I missing and/or is there a tutorial out there someone can suggest with a similar business case I can look at for help?

Tags (1)
0 Kudos
Reply
2 Replies
Workflow Hero

Re: Best actions to create an O365 Nintex workflow that interacts back and forth between users.

You could use tabs on the form for the different sections, or panels under each other

Have a status column in the list which could determine which Tab or Panel is active as a certain point in time.

If there isn't an approval required just input on the form I usually just add a wait action and wait for a column in the list to be populated before moving forwards. Updating the forms and then going to approve another form isn't required most of the time.

There is a good example on a users blog on how to add a loop with an exit clause and it will keep sending emails until a column is updated on. Task Actions and Request for Details are so on-premises ( they still rare useful sometimes)

Good luck, keep asking questions!

Accept as Solution Reply
Not applicable

Re: Best actions to create an O365 Nintex workflow that interacts back and forth between users.

Thanks so much for the response!

I'll start digging in with this info and see how far I can get!!

0 Kudos
Accept as Solution Reply