Skip to main content

So I have an approval list that has 12 defect fields on it. Each defect field has a defect owner field (can be multiple users) tied to it.I have a workflow that triggers a flexi task to each of these defect owners listed. The problem I am running into is that, there may be different people assigned to each defect and I don't want to notify the initiator that the task has been complete if not all defects were addressed. I tried Majority Decides but that didn't work because they could assign multiple defect owners to one defect but only one person needs to respond. In this case, defect 1 had 2 people, defect 2 had 2 people and defect 1 had 1 person assigned. 1 person completed out all 3 defects. Anyone have a super cool suggestion around this??

190395_pastedImage_0.png

How about you Cassy Freeman​?

Hi Josh Shutts​,

To understand your situation better: Do you have one flexitask or do you have one flexitask for every defect?

Greetings,

Rick


Hi Rick

I only have the one flexi task. Funny you should ask though because adding a separate flexi task for each defect was my next idea.


Hi Josh Shutts​,

I asked because I already thought you used only one flexitask and because I think your situation needs one flexitask per loan happy.png

You mentioned that you do not want to inform the initiator until all tasks are done (all defects are addressed). A possible solution for this is:

  1. the action: Run parallel actions.
  2. In every branch, put a 'Run if' action where you check if the related people picker field is not empty.
    1. Example, Branch one if for loan 1. So here you check is the people picker field for loan 1 is not empty.

When all tasks are done, it will go to the next action. I visualized it below.

190421_pastedImage_4.png

There are other solutions possible which could be better for your situation but above description should give you an idea.

Have fun! Cheers,

Rick

Please mark this reply as a correct answer if it answers your question.


This should work. I had to do something similar....but my situation was if all approved move on, if any did not go back to start.


Thanks Rick. Trying to figure out how to do this when I have 12 defects to look at though. I can do separate workflows for each task but I am trying to alleviate the emails.


You should just need 12 branches in the one workflow.


how did you get on with these suggestions ‌?


Hi Cassy

I haven't been able to figure it out yet. So I have created separate workflows for each defect for now as a workaround.


Right it's not pretty but you can do this with nested Run parallel actions as follows:

Make sure you wrap your flexi tasks with a Run if to check that the defect unit lead is not empty as mentioned earlier in this thread.

I will email you my list template and workflow if you can't see what I mean in the above image.

Sorry for the delay.


Reply