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

Allow multiple "Optional" workflow task assignees

Allow multiple "Optional" workflow task assignees

Today most out of the box workflows include a reviewer/approver and an observer task.

The observer task usually is set to a non-required participant.

However if you have multiple users in this role it will close out on the first completion, leaving the others with no ability to respond.

task1.png

If the vote is required, you can set it to complete on All, Any, or Number. However this is not possible for optional.

task2.png

I'm proposing the any, all, number selection be independent of the required check-box allowing multiple optional observers.

2 Comments
Alexandrite

Most observe tasks end in a ground anyways, so it can be made required and probably won't cause an issue unless you report on required tasks.

We also have a bit of code to close out open tasks at the end of the process, otherwise they seem to be stay open when we'd rather they be closed at end of workflow.

Regular Member

I have implemented the ability to do something similar with OOTB workflow tools.  Basically there are 2 tasks that go out in parallel:  one is optional to any number of assignees, and the other goes out to a role that is the "final" decision to a specific role.  The "optional" one essentially remains open for whoever wants to vote a choice, but the ultimate choice is driven by that "final" voter, given the votes of everyone who had voted in the optional task up to that point (which will show in the process history).  Once the final vote is made, the optional task closes up and is removed from anyone's task list who did not respond, while keeping the responses that WERE made, whether it be 2, 20, 200, etc responses.

I'd be happy to discuss this further with you, or any other Windchill questions you may have.  Feel free to write me here or e-mail me if you are interested.