Approval Process - End other parallel Flexi Tasks, when one approves first

Hi,

Unfortunately the task ids are not available to the workflow until the Flexi tasks are completed. This means that after one of the tasks is completed a query will need to be done on the task list to find the tasks. The tasks should have a unique description to make them easier to find. Once found they can be rejected using the Nintex web service.
https://help.nintex.com/en-US/sdks/sdk2013/#Reference/SOAP/NW_REF_SOAP_ProcessFlexiTaskResponse2.htm%3FTocPath%3DNintex%2520Software%2520Development%2520Kit%7CNintex%2520Workflow%25202013%2520Software%2520Development%2520Kit%7CNintex%2520Workflow%25202013%2520SDK%2520Reference%7CWeb%2520Service%2520Reference%7CService%2520operations%7C_____30
You can send out any no longer required emails as needed.

@ellie5225 .....Just out of curiosity.....if you don't need approvals from other approvers then why you'll assign them those tasks in first place? I mean in what circumstances you'll need approvals from other approvers? 

 

Also, what if other approvers responds before your first approver?

@beckettj the End workflow action will kill the whole workflow not just the outstanding tasks and if you could do this how would you implement it?

What happens if there is more of the workflow to run? The workflow would just end instead.

Happy Late Thanksgiving to all. I hope everyone had some time off to enjoy some time with family and friends.

 

Thank you to all that replied to my many questions to date. For this particular one the client agreed to accept all reviewers & approvers before proceeding within the parallel workflow. That did eliminate this headache, however I still was interested if this scenario had to play out how would it look like if I still had to finish it that way?

 

I agree, beckettj on starting a separate workflow to complete the remainder of the workflow as that branched off to approved, rejected or needed more discussion.

 

I also started thinking about the outcomes within the assign task action, is there a way to create a few actions beforehand to see if approver responded first by doing a query on the SharePoint field that would update and then cancelling the other reviewers tasks withing the assign flexi task based on the approver outcome? And do they still get the no response necessary notification within the assign flexi task or do I need to do a separate notification afterwards?

 

I always feel the reviewers come first and next approved although this scenario was interesting and wander how that would play out in another scenario. 

 

Thanks for humoring me.