Skip to content

POST,PATCH /tms/loading-planner/form

TMS > tms.transload

What it does

/tms/loading-planner/form accepts POST,PATCH and is declared in app/systems/TMS/transload/api_routes.php:352 as a path.

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

Call chain:

  1. → tmsTransloadApiLoadingPlannerFormMutation() — app/systems/TMS/transload/form_mutation_api_helper.php:449
  2. ↳ apiTableMutationNormalize() — app/shared/api/table_mutation_helper.php:6
  3. ↳ array_uppercase() — app/shared/controller/common_post_helper.php:177

Who calls it

Called from:

  • public/assets/js/modules/shared/popup.core.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_LOADING_PLANNER

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

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

  • Bale source fields must use the loading planner API.

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.