Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTeam
Device

Edit Vacation Block

Update an existing vacation blackout when dates, reason, affected scope, staff roles, staff members, or recurrence need to change. This edits an existing `vacation_blackout` calendar event; it does not delete the block or convert it into another event type.

In this article

Use this guide when a location manager needs to adjust an existing blackout such as Harbor Soho's `Peak season blackout` from the Vacations calendar.

Vacation blocks are saved as all-day calendar events. They can apply to the whole location, selected roles, or selected staff members, and the Repeat tab can update recurrence when the block should repeat.

Before you start

  • The vacation block already exists in the current location.
  • The operator is working inside the correct organisation and location route for Harbor Demo Group and Harbor Soho.
  • The operator has `vacation-blackout:view` to open the screen and `vacation-blackout:manage` to save changes.
  • Staff roles are available before using Role scope, and staff members such as Olivia Hart, Mason Reed, Noah Stone, or Ava Price are available before using Staff scope.
  • The edit route includes an existing event id and `kind=vacation_blackout`.

Instructions

  1. 1.

    Open the blackout

    Open the Vacations calendar and select the existing vacation block, or open the edit link directly with `kind=vacation_blackout`. The app must resolve the organisation, location, event id, and view permission before showing the form.

  2. 2.

    Review the Info tab

    Check Start date, End date, Scope, and Reason before changing anything. Vacation blocks are all-day events, so the selected dates define the full operational blackout period.

  3. 3.

    Choose the affected scope

    Use Total for the whole location, Role for selected staff roles, or Staff for selected staff members. Changing scope clears selections that no longer apply so role ids and staff ids are not mixed.

  4. 4.

    Update the reason

    Enter a clear operational reason, such as `Peak season blackout`, so managers and staff understand why holiday requests are blocked during that period.

  5. 5.

    Adjust recurrence when needed

    Open Repeat only when the block should repeat. Choose Daily, Weekly, Monthly, or Yearly and set the interval and ending rule. Do not document `Does not repeat` as deleting a previous recurrence, because that deletion flow was not verified.

  6. 6.

    Save changes

    Select Save. The button is disabled while saving, when the form is invalid, or when nothing changed from the loaded event. On success, the app shows `Event updated successfully.` and returns to the calendar or source screen.

Validations and limits

  • Start date and end date are required, and the start must be before the end.
  • Reason is required after trimming empty spaces.
  • Role scope requires at least one staff role.
  • Staff scope requires at least one staff member.
  • Saving requires `vacation-blackout:manage`; view-only access cannot update the block.
  • The backend rejects attempts to change the event kind away from `vacation_blackout`.
  • The payload can include staff role ids only for Role scope and staff ids only for Staff scope.
  • Recurrence is supported for `vacation_blackout`, but only daily, weekly, monthly, and yearly frequencies are valid when recurrence is sent.

Expected result

The existing vacation blackout remains a `vacation_blackout` event with updated dates, reason, scope, affected roles or staff, and optional recurrence. Calendar event caches refresh and the operator returns to the calendar or source surface.

Related articles