Forum Discussion
Redesign Nintex workflow with azure queue /logic app /flow
- Mar 30, 2017
I figured out the solution, Logic apps give a schedular functionality to trigger a workflow. So i think redesigning the workflow to break it into multiple workflow.
First one to mark the attendance and upadate the other information.
Second one to check for flag periodicaly and send notification, Now to trigger this second workflow perodically use a Logic app to check it and trigger it.
I hope the idea helps.
thanks
I figured out the solution, Logic apps give a schedular functionality to trigger a workflow. So i think redesigning the workflow to break it into multiple workflow.
First one to mark the attendance and upadate the other information.
Second one to check for flag periodicaly and send notification, Now to trigger this second workflow perodically use a Logic app to check it and trigger it.
I hope the idea helps.
thanks
- DeletedNov 23, 2017I am looking at Logic Apps/Flow to provide process automation solution for our business in O365. We have been using Nintex on premise. Can you share your insights on pros and cons, if you had experience with Nintex Online?
- Alex KaziukaNov 24, 2017Brass Contributor@Edua,
Answering your question I can say this is just the matter of taste... and probably the price :). As I stated in one of the topics here (https://techcommunity.microsoft.com/t5/Azure/Can-Flow-amp-Logic-Apps-Replace-Nintex/m-p/130858#M1552) both tools (I mean MS Flow and Nintex Workflow) are roughly the same. Both have hundreds of different actions, tons of adaptors, work and integrated greatly with SharePoint and O365.
Nintex used to shine when everything SharePoint had as an alternative was SPS Workflow, so they were winning every time. I can say that Flow is a game changer. At the same time, I have to admit though, that compared to Microsoft, for Nintex their products like Forms and Workflow are the bread and butter and Flow is still a product under development with no finite version. The only difference that catches the eye is probably the fact MS Flow is only cloud-based, whereas Nintex Workflow has both on-premise and cloud versions.