Multi-level approval workflow

When a time off request is subject to multiple levels of approval, the request is first routed to the user(s) at level 1 satisfying the specified role(s) on the employee's team as of the time off day. If a level 1 user approves the request, the request is then routed to the user(s) at level 2. If a level 1 user denies the request, the request is moved to a denied state, ending the workflow. The employee who submitted the request is notified that the request has been denied.

If a request routed to level 2 is approved by a level 2 user, the request is then routed to the user(s) at level 3, if configured. If a level 3 user approves the request, the request is moved to an approved state. If a level 3 user denies the request, the request is moved to a denied state. In both cases, the workflow is ended and the employee who submitted the request is notified that the request has been approved (or denied).

In this workflow, a time off request remains pending until an approver at the highest level approves the request or the request is denied. The employee who submitted the request is notified when a final action is taken on the request.

If an approver who is not at the highest level partially approves a time off request, the approved days are routed to the next level approver. The remaining days remain the responsibility of the current approver to act upon. The employee who submitted the request is notified when a final action is taken on at least one of the days of the request.

If an employee cancels an approved time off request, only one approval at any level is required. For example, if a user at level 1 approves the cancellation request, the request is moved to a cancelled state, bypassing the next level approver. The employee who submitted the cancellation request is notified that the request has been approved for cancellation.

The system maintains an audit trail of all the actions taken by all of the approvers over the course of a request's approval (or denial) process.