Skip to content

PATCH /tms/staff-time/manager-events/(?P[0-9]+)

TMS > tms.transload

What it does

#^/tms/staff-time/manager-events/(?P<id>[0-9]+)$# accepts PATCH and is declared in app/systems/TMS/staff-time/api_routes.php:638 as a regex pattern.

The route handler delegates to tmsStaffTimeManagerUpdateEvent(). That function is the owner of this behaviour; the route entry is only dispatch.

Call chain:

  1. → tmsStaffTimeManagerUpdateEvent() — app/systems/TMS/staff-time/api_routes.php:462
  2. ↳ staff_time_assert_can_manage() — app/systems/TMS/staff-time/staff_time_helper.php:220
  3. ↳ staff_time_can_manage() — app/systems/TMS/staff-time/staff_time_helper.php:212

Who calls it

No literal caller path was found in frontend/, public/ or new-system/. The endpoint may be called through a constructed path, a helper wrapper, or only by an external client. Treat the route table and owner function as the authority.

Input

Where Key
path id
query (required) id

Request bodies must not use TYPE, ACTION or USERNAME as contract fields.

Output

Key
CREATED_BY
EVENT_TIME
EVENT_TYPE
ID
NOTE
SOURCE

Success is { "data": …, "requestId": "…" }. Failure is { "error": { "code", "message" }, "requestId": "…" }.

SQL executed

UPDATE T_STAFF_TIME_EVENT

Data

Tables reached from the owner function:

  • T_STAFF_TIME_EVENT

Access

  • module-gated on tms.transload, so tenant module access applies

Validation and failure messages

  • Only clock and break events can be adjusted.
  • Staff time event was not found or cannot be adjusted.
  • Manager permission is required.

These strings come from the owner function and are the messages a client can receive. They are also the cheapest way to tell a rejected request from a broken one.