Skip to content

PATCH /tms/staff-time/current-context

TMS > tms.transload

What it does

/tms/staff-time/current-context accepts PATCH and is declared in app/systems/TMS/staff-time/api_routes.php:620 as a path.

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

Call chain:

  1. → tmsStaffTimeUpdateCurrentContext() — app/systems/TMS/staff-time/api_routes.php:138
  2. ↳ staff_time_resolve_staff_user_id() — app/systems/TMS/staff-time/staff_time_helper.php:341

Who calls it

Called from:

  • frontend/pages/system/TMS/transload/inbound-planning.php

A caller is the strongest available evidence of the intended use.

Input

Where Key
body NOTE
body STAFF_USER_ID
body WORK_CONTEXT
body note
body staffUserId
body workContext

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

Output

The response is produced by a shared helper, so the key set is not visible at the route. Read the owner function to confirm the shape before writing a client.

SQL executed

SELECT ID FROM T_USER WHERE CLIENT_ID=? AND ID=? AND DELETED_AT IS NULL LIMIT 1

Data

No table reference is visible in the owner function body.

Access

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

Validation and failure messages

  • Manager permission is required.
  • Staff user id is required.
  • Staff user was not found.

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.