Let's Reconnect, thank you for making 2022 our best year yet.

Look Back
Parallel Approval notifications behave differently for different processes — 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

Parallel Approval notifications behave differently for different processes

Accepted answer
31
Views
3
Comments
in Human Resources 3 comments

Summary:

How can we ensure consistent behavior of approval notifications? 

Content (required):

For a few processes, we have configured approval by HR Representatives (include all) where we use approval type Parallel and first responder wins. We have noticed different behavior for different processes. 

For Global Absence Recording - Single Assignment (AbsencesApprovalsTask), when one of the HR Representatives has approved the transaction, the approval is completed. The HR Representatives that were not the first to respond, receive a Withdrawn notification to indicate that the approval is completed. This provides clarity and works really well.

For Resignation (ResignationApproval), when one of the HR Representatives has approved the transaction, the approval is completed. The HR Representatives that were not the first to respond, unfortunately do NOT receive a Withdrawn notification to indicate that the approval is completed.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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