Replace poorly designed Workflow( needs delay/onhold) with azure queue /Power app /flow

%3CLINGO-SUB%20id%3D%22lingo-sub-56021%22%20slang%3D%22en-US%22%3EReplace%20poorly%20designed%20Workflow(%20needs%20delay%2Fonhold)%20with%20azure%20queue%20%2FPower%20app%20%2Fflow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56021%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20nintex%20workflow%20on%20sharepoint%20online%2CThis%20workflow%20is%20used%20for%20employee%20time%20management%2C%20so%20for%20every%20employee%20at%20start%20of%20his%20shift%20a%20workflow%20starts%20running%20and%20it%20loops%20through%20employee%20information%20and%20checks%20compliance%20conditions%20and%20send%20perodic%20notifications%20to%20each%20employee.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProblem%20%3A%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20poorly%20designed%2C%20Workflow%20runs%20when%20each%20employee%20starts%20its%20shift%20and%20then%20there%20is%20lot%20of%20looping%20%2C%20hold%2Fdelay%20option%20used%20to%20send%20notification%20every%20hour%20based%20on%20the%20condition%20is%20either%20met%20or%20not%20met.%20What%20it%20does%20is%20when%20that%20same%20thing%20is%20done%20for%20each%20employee%20it%20loops%20more%20than%205000%20items%20and%20so%20many%20delay%20tasks%20and%20multiple%20threads%20which%20causes%20the%20workflow%20to%20break.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20operation%20requires%20hourly%20notification%20and%20check%20complaince.%20Now%20i%20am%20thinking%20to%20provide%20suggestion%20to%20redesign%20this%20workflow.%20So%20was%20trying%20to%20explore%20other%20options%20which%20we%20can%20use.%3C%2FP%3E%3CP%3EWould%20it%20be%20better%20to%20do%20this%20task%20from%20a%20webjob%20with%20azure%20queue%20to%20place%20data%20on%20the%20queue%20and%20pick%20after%20every%20one%20hour%20for%20each%20employee%20would%20this%20be%20the%20right%20way%20to%20do%20this%20kind%20of%20task.%20any%20example%20would%20be%20helpful.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPower%20app%2Fflow%20do%20they%20have%20some%20new%20feature%20to%20do%20this%20more%20effectively.%20I%20am%20open%20to%20other%20options%20also%20Please%20suggest%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

We have a nintex workflow on sharepoint online,This workflow is used for employee time management, so for every employee at start of his shift a workflow starts running and it loops through employee information and checks compliance conditions and send perodic notifications to each employee.

 

Problem : 

It is poorly designed, Workflow runs when each employee starts its shift and then there is lot of looping , hold/delay option used to send notification every hour based on the condition is either met or not met. What it does is when that same thing is done for each employee it loops more than 5000 items and so many delay tasks and multiple threads which causes the workflow to break.

 

This operation requires hourly notification and check complaince. Now i am thinking to provide suggestion to redesign this workflow. So was trying to explore other options which we can use.

Would it be better to do this task from a webjob with azure queue to place data on the queue and pick after every one hour for each employee would this be the right way to do this kind of task. any example would be helpful.

 

Power app/flow do they have some new feature to do this more effectively. I am open to other options also Please suggest

 

Thanks 

 

0 Replies