Mobile setup
The same products, inside the FSA mobile app. This is a configuration task in FSA, not a deployment — there is nothing to push through an app store.
On this page
What runs on mobile#
- Warranty Checker — Is this repair covered? Equipment and a date give a verdict before the work starts.
- Stock Checker — Live S/4 material availability, per plant and storage location — before anyone drives out.
- Service Report Compiler — One activity becomes a branded PDF — and goes back onto the record as an attachment.
- S/4 Live — Browse any live S/4 entity from inside FSA — no screen to build first.
- Attachment Renamer — Rename attachments in bulk by pattern — with a history you can actually undo.
Screens you have published as their own extensions can target mobile too — see publishing a screen.
Configuring the Web Container#
- In FSA, create a Web Container configuration for the relevant user group.
- Point its URL at
https://pwa.altiwerk.com. - Set the auth key to your licence key — the same one the web install uses.
- Assign it to the technicians who should have it, the way you assign any other Web Container.
With no further configuration, each technician sees a tab per product their licence covers. One configuration serves the whole workforce.
Showing one product, or a few#
Three shapes, chosen by how the URL is configured:
| You want | Configure |
|---|---|
| Everything they are licensed for | The plain URL. Navigation shows one tab per product. |
| Exactly one product, locked | The product parameter naming it. It opens straight in, with no navigation at all. |
| A curated few | The same parameter with several names. Navigation shows those; the licence still decides what is actually allowed. |
The exact parameter values are in the runbook we send with onboarding — they are per product and short.
Passing the record through#
Set the container's object types — equipment, activity, service call — and the host record travels with the technician. Opening the warranty check from an equipment arrives already filled in and answered.
On a phone keyboard, that difference is larger than it sounds: it is the gap between a two-second check and a technician typing a serial number with gloves on.
Installing it on the device#
It can also be added to the home screen and opened as an app in its own right. That is a browser capability rather than a distribution channel — there is no store listing, no MDM package and nothing to sign.
Sessions and offline#
Mobile sessions expire. When one does, the app says so and tells the technician to reopen it from FSA — rather than showing an empty list that looks like missing data. In the field, that distinction matters more than it does at a desk.
Products that read live S/4 data need a connection by design: a cached warranty verdict is a wrong warranty verdict. Where an offline copy genuinely helps, the studio's snapshot pattern pulls the record into FSA first and FSA's own offline behaviour takes over.