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.
The clip installs S/4 Live because it had to install something. The steps do not change from one product to the next — copy the mobile URL, create the container, paste the licence key.
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#
A Web Container screen has no way to renew its sign-in — FSA hands the session to the container that opened it, and there is no refresh channel to ask for another. So the session lasts as long as that container.
When it runs out, the screen says so and sends the technician back to FSA to reopen it. Importantly, it stops before a write rather than during one: a bulk rename or a report upload started on a dead session is refused outright, instead of applying to some records and failing on the rest. Recovering from a refusal is a tap; recovering from a half-applied batch is manual work.
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.