Skip to content

POST,PATCH /tms/transloads/form

TMS > tms.transload

What it does

/tms/transloads/form accepts POST,PATCH and is declared in app/systems/TMS/transload/api_routes.php:252 as a path.

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

Call chain:

  1. → tmsTransloadApiFormMutation() — app/systems/TMS/transload/form_mutation_api_helper.php:295
  2. ↳ tmsTransloadApiNormalizeFormBody() — app/systems/TMS/transload/form_mutation_api_helper.php:198

Who calls it

Called from:

  • public/assets/js/modules/shared/inbound-completed-modal.js
  • public/assets/js/modules/shared/popup.core.js
  • public/assets/js/modules/tms/export-transload-create-modal.js
  • public/assets/js/modules/tms/transload-edit-modal.js

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

Input

Where Key
query mode

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

Output

Key
T_TRANSLOAD

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

SQL executed

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

Data

Tables reached from the owner function:

  • T_TRANSLOAD

Access

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

Validation and failure messages

  • Completed loads cannot be rescheduled.
  • Reschedule a no-show load through the reschedule action.

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.