The business case is as follows:
A projects responsible (activity requestor, project owner...) requests feedback for an asset/attachment (e.g. proposal received from the agency) and involves for that multiple colleagues in a review task. At the end, it is the responsible who has the final saying (approve/reject), but in making that decision, this person takes into account the feedback (vote/comment/annotations) provided by the reviewers. Also, this person does not necessary waits for everybody to respond (e.g. vacation, illness) or might already come to a conclusion, based on partial feedback.
As we envisioned it , this could be a normal review task with a new kind of voting style. The review task would have two roles involved: feedback reviewers & decision takers. The workflow engine should not wait for the feedback reviewers to vote before closing the task. But the task should however wait until all assignees in the decision taker role have casted a vote (within that group, normal voting styles could drive the final outcome of the task: majority, first vote,...)
Customer support service by UserEcho