A mobile-ready API for field apps
Field team management: a mobile-ready API that saves site work to the work order
ELX is a cloud service hosted and operated by Matrix that runs in the browser, and its field team management relies on a separate REST API built for field mobile apps. Field staff sign in with their existing permissions, receive tasks, save data and upload site photos, and relay survey, permit, project and replay tasks under the same validation rules as the web system.
What does the mobile API offer for field team management?
The API is part of ELX and works on the same work orders the office follows in the web system.
Documented REST API
A separate, documented REST API built for field mobile apps and reading and saving the same work orders the web system uses.
Sign-in and permissions
Staff sign in with username and password, the field app receives a signed access token, and only the mobile screens allowed by the same permission matrix are shown.
Language and assigned districts
Staff pick Arabic or English with the matching text direction, and the app loads their assigned districts and the available languages.
Field-stage tasks
Field staff receive their survey, excavation permit, project, connection, replay-stage and maintenance tasks, and confirm receipt of each assignment.
Save and relay under the same rules
Survey, permit, project and replay tasks are relayed only after mandatory fields, notes and attachments are checked, just as in the web system.
Site photos and files
Staff upload photos and files to their task in any of these stages and can view the files already attached to it.
Delay justifications
When a task is past its time limit and justification is mandatory, staff add the justification with supporting files and can delete a file attached by mistake.
Matching forms by email
When the survey or materials do not match, staff can email the survey or material matching form through the API, just as from the survey screen in the web system.
Last known field location
The field app sends GPS points to ELX and each field user's last known location is updated; Matrix can show these locations on a central monitoring map.
How does the field team work day to day?
- 1
The office assigns
A supervisor assigns the order to a field user from the distribution screen. The task appears in their list through the API and they confirm receipt.
- 2
Inspect and record on site
The engineer opens the task, reviews its files and records the data from lookup lists such as drill types, permit-need options, materials, implementation items and warehouses.
- 3
Upload photos and attachments
Site photos and files go onto the task itself, so they stay with the work order and its stage instead of getting lost in chats.
- 4
Save, then relay
The data is saved, then a survey, permit, project or replay task is relayed once ELX has checked mandatory fields, notes and attachments, with a delay justification if settings require one.
- 5
The office follows up
The order moves to its next stage in the web system, where that stage's team finds it in their list and the office tracks progress on the dashboard. The engineer's last known location updates whenever the app sends GPS points.
From photos scattered across chats to one work order record
When field engineers send photos and notes in scattered chats, the office retypes them, files end up spread across phones, and nobody knows a stage is done until someone calls. ELX's mobile API saves what is recorded on site into the work order itself.
- Field staff work on the tasks assigned to them, within their permissions and districts.
- Data is saved straight into the work order stage instead of being re-entered at the office.
- Relay goes through the same mandatory-field and attachment checks as the web system.
- Delay justifications are recorded with their files when a time limit is passed.
What can field staff do in each stage through the mobile API?
What the API supports for each type of field task; anything it does not cover is completed in the web system.
| Stage | What field staff can do | Relay to the next stage |
|---|---|---|
| Site survey (Kashfia) | Receive, view and save tasks, upload photos and files, and email the survey and material matching forms | Through the API |
| Excavation permits | Receive, view and save tasks, upload photos and files | Through the API |
| Projects | Receive, view and save tasks, upload photos and files | Through the API |
| Connections | Receive, view and save tasks, upload photos and files | In the web system |
| Replay stage | Receive, view and save tasks, upload photos and files | Through the API |
| Maintenance and emergency | View and list tasks, save data, upload files | In the web system |
Field work and the mobile API: common questions
Is ELX a mobile app?
No. ELX is a cloud (SaaS) service hosted and operated by Matrix. It runs in the browser with no servers needed on your side, and it is not a published app-store app. It includes a separate API built for field mobile apps, covering sign-in with permissions, field-stage tasks, photo and file uploads, relay and last known locations. To see how your field team would work in ELX, request a demo.
What can a field engineer do through the mobile API?
They receive assigned survey, excavation permit, project, connection, replay and maintenance tasks, confirm receipt, review files, save data and upload photos and attachments. Survey, permit, project and replay tasks can be relayed once mandatory data is checked, with delay justifications where required. Maintenance tasks support viewing, saving and files, and their relay is completed in the web system. Our field engineer mobile app guide covers what contractors need from a field tool.
Are mobile permissions separate from system permissions?
No. The mobile screen list is built from the same permission matrix the administrator sets for each user at screen and action level. On sign-in, the app loads the screens the user may open and the districts assigned to them, so field staff see only what they are allowed to see.
Does ELX record where field teams are?
ELX keeps each field user's last known location, not a full route. When the field app sends GPS points, up to the ten most recent per upload are stored and the user's last known location is updated. Matrix can show these locations on a central monitoring map. This is not continuous route tracking or route planning, and how your team views the locations is agreed with the Matrix team.
How does a field user learn about a new task?
Assigned tasks appear in the user's task list through the API, where they confirm receipt of each one. ELX also sends a Telegram message, plus WhatsApp when enabled, when a work order enters a new stage, to users who can view that stage's screen, have notifications on and have a registered number. See instant notifications for how the channels work.
Articles about Field work & mobile API
Field Engineer Mobile App: What Contractors Need
What a field engineer mobile app must do for utility contractors: claim tasks, record stage data, upload site photos and relay orders under one set of rules.
Read articleMaintenance and Emergency Work Orders: A Field Guide
How to run maintenance and emergency work orders on power networks: notice, station and feeder data, team dispatch, the emergency permit and clean close-out.
Read articleSaudi PDPL for Contractors: What Systems Must Handle
Saudi PDPL for contractors: subscriber and technician data in work orders, data subject rights, 72-hour breach reporting and questions for your vendor.
Read articleDaily Work Order Digest on WhatsApp and Telegram
How managers get a daily work order digest on WhatsApp and Telegram: today’s receipts, order aging, team workload and warehouse activity in one message.
Read article
Want to see ELX on your own projects?
Request a demo from our team on WhatsApp and see how work orders, extracts and warehouses run in one system.