Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTeam
Device

Reject a Holiday Request

Decline a pending staff holiday request without deleting it. Antylogic keeps the same `calendar_event` and marks the staff vacation request as `rejected`.

In this article

Use this guide when a location manager needs to turn down a pending holiday request after reviewing the employee, dates and notes.

The documented path opens the request detail before the decision, then uses the confirmation dialog so the manager can check the employee and holiday dates before submitting the rejection.

Before you start

  • You are signed in with Harbor Demo Group and Harbor Soho selected for the GB en-GB demo.
  • Your role can view holiday requests with `vacation:view` and reject them with `vacation:manage`.
  • A pending `staff_vacation` request exists in the visible date range, normally the current calendar year.
  • For the GB demo capture, use Olivia Hart when her seeded pending request is still available in the documentation runtime.

Instructions

  1. 1.

    Open the pending holiday request queue

    Go to `calendars/vacations/requests?pending_only=true`. The page focuses the list on requests that still need a manager decision.

  2. 2.

    Find the pending request

    Locate the employee row and check that it shows a pending status, requested dates and any existing note attached to the request.

  3. 3.

    Open the request detail

    Open the pending row before deciding. If the loaded event is still a pending `staff_vacation`, the detail screen shows the `Reject` and `Approve` actions.

  4. 4.

    Start the rejection

    Select `Reject`. Antylogic opens a confirmation dialog with the employee and holiday dates so the manager can verify the decision before it is submitted.

  5. 5.

    Confirm the rejection

    Confirm with `Reject` in the dialog. The app updates the existing holiday request to `rejected` through the calendar event update flow.

  6. 6.

    Check the final state

    Return to the request list. In the pending-only view, the request no longer appears; in the all-requests view, the same request is visible with the `Rejected` status.

Validations and limits

  • An active organisation and location are required before the queue can load.
  • Users with `vacation:view` can see the queue, but `vacation:manage` is required to reject a request.
  • Only pending requests are actionable from the manager review flow.
  • Cancelling the confirmation dialog leaves the request unchanged.
  • The rejection updates the existing `calendar_event` with `payload.status = "rejected"`; it does not delete or recreate the event.
  • This action does not add a new rejection-reason field. Any existing note is retained when present.
  • If permissions, validation, blackout checks or another API error blocks the update, the request remains unresolved and the UI shows the error.
  • Rejected holiday requests do not count towards requested or accepted holiday totals.

Expected result

The staff holiday request remains on record as the same calendar event, is labelled `Rejected`, and no longer appears as a pending decision for the manager.

Related articles