How often people make wrong decisions? The answer is obvious - often enough and it is part of human nature! However, as a developer or architect - when we designing and implementing a system - do we taking into account that attribute of human being, do we provide a second chance?
One of interesting use case is CAB voting within Change Management process, but it also could be any other process that requires decision making.
People may lack enough information - not enough to make proper decision and therefore their approval/reject will not represent their real vote if they knew enough.
So, let's say we have CAB group containing 5 people and the logic inside Approval activity would look as this:
If change that you need to deliver is critical and there are small risks - you would expect that there would be more "approval" than "rejects". But what if somebody didn't have enough information and decided to reject? And what if you decided to talk and prove to that person that this change is necessary and you may even succeed in it - but system already has "reject" for his voice.
Such cases could be managed through special mechanism of reVote based on UI Action:
for sure - you may want to modify it and make it more comprehensive - add conditions and so on, but the idea is clear - proving second change for voting is possible unless workflow didn't go further.
