Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
Understanding Vote outcome workflow in BPM — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Understanding Vote outcome workflow in BPM

Received Response
37
Views
7
Comments

Summary:


Content (required):

There is a scenario where 4 approvers are in a group and vote outcome is set to 50%. System will wait for all approvers action before triggering the outcome. Setting is done as below:

When I submitted requisition, approve1 approves, then approver2 rejected, then approver3 rejected and approver4 approved. Outcome was approved for the requisition. I expected that approver3 action may determine the outcome based on sequence. Since he rejected, outcome should have been reject as its criteria of vote met first. But that's not what had happened.

Can anyone help me understand how this is happening? Any setup that controls this?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!