Transport module

The transport module is meant for a passenger transport company to keep its vehicles’ journey forms, routes and charter jobs. The module is shown to the company’s administrators. Drivers see their journey forms in the mobile app, enter the odometer readings there and report vehicle faults.

• Journey forms: the vehicles’ journey forms and their rows (work, regular trip or charter trip). The time and planned mileage of a journey form are calculated from its rows.
• Routes: the list of routes with number, name and length; the route length gives the mileage of a regular trip row.
• Charter jobs: the time, origin and destination of ordered trips. Each charter job can be added to one journey form row.
• Faults and problems: registering and closing faults of vehicles and work objects.

When you open the module, you first see the list of journey forms. Add the routes and charter jobs before filling in journey forms, because a journey form row selects them from the existing ones.

API calls on this page

For integrations and AI assistants: this page uses the following Terake API calls. The full description is in the API reference.

Other calls from this screen’s dialogs and actions (from the web client’s code):

• DELETE /api/customer/{customer_id}/person/{id} – Deletes a Customer contact person
• DELETE /api/identificators/{id} – Delete Identificator by ID or UUID
• DELETE /api/plans/{planid}/materialusages/{usageid} – Deletes one material usage of a Planitem
• DELETE /api/summarised_worktime/{worker_id}/{id} – Delete WorkerSummarisedWorktime
• DELETE /api/workobjects/{id} – Delete Workobject
• GET /api/workers/last-seen/{id} – Last recorded device access for one worker, by worker id or uuid
• GET /api/workers/brigade-members/{id} – Brigade members of one worker acting as foreman, by worker id.
• GET /api/facilities/enginehours-log/{id} – Facility engine hours and kilometers history from manual entry
• GET /api/facilities/telemetry-log/{id} – Facility engine hours and kilometers history from telemetry data log
• GET /api/fieldbook – Fieldbook Agrifield collection
• GET /api/fuelfillings/facility/{facility_id} – Fuel fillings recorded against one facility.
• GET /api/geoinfo/cadaster/{num} – Cadastral register information for one cadastre number
• GET /api/identificators/{id} – Identificator by ID or UUID
• GET /api/identificators – Identificator collection
• GET /api/identificators/worker/{id} – Identificators registered for one worker
• GET /api/inventorylog/{id} – Get Facility Inventory Log
• GET /api/materials/{id} – Get Material
• GET /api/materials/{id}/harvest_sources – Harvest Material sources
• GET /api/materials/{id}/material_composition – Harvest Material composition
• GET /api/materials/{material_id}/inventory – MaterialInventory of a material
• GET /api/fieldbook/overlapping-check/{agrifield_id}/{crop_period_id} – Reports fieldbook entries whose geometry overlaps for one Agrifield and crop period
• GET /api/planreportsync/{id} – Planitem by ID
• GET /api/projects/{id} – Project by ID
• GET /api/relations/{object_type}/{object_id} – Returns the objects related to one Terake object
• GET /api/summarised_worktime/{worker_id} – Summarised worktime list by worker.
• GET /api/translations-public – TranslationPhrase dictionary
• GET /api/workers/{id}/files – List all files related with parent object
• GET /api/workobjects – All Workobjects list
• GET /api/worktypes/{id} – Get Worktype
• GET /api/integration-partner-data/{terake_object_code}/{object_id} – Integration partner id's related to object
• POST /api/customer/{customer_id}/person/{id} – Creates or modifies a Customer contact person
• POST /api/sendinvitationletter – Sends a partnership invitation to a customer's e-mail address
• POST /api/facilities/integration – Registers a Facility reported by the integration server
• POST /api/facilities/log-mapping-event – Records a facility-mapping event sent by the integration server
• POST /api/flatapi/worker-factory-credentials – Registers a PIN, NFC or RFID credential for a worker
• POST /api/identificators – Create new Identificator
• POST /api/notification-read/{id} – Marks a notification as read
• POST /api/plans/{planid}/materialusages – Adds material usage to a Planitem
• POST /api/plans/{id}/files – Add new file to parent object
• POST /api/plans/{calendaritem_id}/recurrence – Creates or modifies the recurrence of a Rosteritem or Planitem
• POST /api/summarised_worktime – Creates WorkerSummarisedWorktime
• POST /api/workobjects – Creates or modifies a Workobject
• PUT /api/worker-generatepin/{id} – Generates factory credentials (PIN) for a Worker
• PUT /api/workers/brigade-members/{id} – Replaces the brigade members of a Worker
• PUT /api/workers/change_username/{id} – Change Worker username
• PUT /api/workers/priapayees/{id} – Replaces the PRIA payees a Worker represents and the crop periods visible to them
• PUT /api/send_welcome_letter/{id} – Sends the welcome letter to a Worker
• PUT /api/workers/approvables/{id} – Replaces the set of Workers whose work this Worker may approve
• PUT /api/workers/setroles/{id} – Replaces the roles of a Worker
• PUT /api/workplace/{id} – Modifies a Workplace
• PUT /api/identificators/{id} – Modifies an Identificator
• PUT /api/summarised_worktime/{id} – Creates a new WorkerSummarisedWorktime, or modifies the one named in the URL