Devices, browsers and network prerequisites
Use this commissioning checklist for the devices and connections people will actually use. It is a practical test matrix; your deployment agreement defines supported versions and service commitments.
Choose the device
| Device or mode | Prepare | Verify before assignment |
|---|---|---|
| Office browser | A current maintained desktop browser, HTTPS access, JavaScript, cookies and site storage | Sign-in/MFA, workspace selection, search, the intended editor and file download. |
| Tablet or phone browser | A current maintained browser and a viewport suited to the task | Touch targets, portrait/landscape layout, keyboard/scanner input, photos and reconnect. |
| Installed Ennea Shop Floor | Install from the shop-floor sign-in page; pair that installation and assign the intended account | Start from the installed icon, sign in, open the assigned App and verify the correct workplace. |
| Shared terminal | Dedicated shop-floor account and approved device/browser profile | Sign-out, account switching, allowed Apps and denied administration. |
| Local equipment connection | Separately commissioned Edge Runtime and approved local network paths | Cloud sync, correct machine identity and actual cloud reporting result. |
The browser used for setup and an installed App can have different storage. Pair and operate the same installation. Clearing site storage, reinstalling or changing browser profile can require a new device setup. See Accounts and devices.
Network and browser settings
Allow HTTPS to the application and API origins supplied by your deployment operator. Realtime updates require the configured WebSocket connection. File previews/uploads and authentication can use additional configured storage or identity-provider origins; obtain the actual allowlist rather than opening arbitrary domains.
Proxy, TLS inspection, content filtering and strict browser policies can affect authentication, WebSockets, iframe-based Apps and file delivery. Ask IT to test those paths with the intended policy and account. A loaded home page alone does not prove that saves, updates or uploads work. Keep device time and timezone correct.
Camera and microphone permissions are needed only for the features that use them. Test the actual camera, audio device, file type and scanner mode. Video/audio codecs vary by browser; media guidance describes supported preview paths. A barcode scanner acting as a keyboard still needs the intended field and configured input behavior.
Connectivity and recovery
Operational saves, submissions and uploads need connectivity. App drafts can be resumable when the App explicitly implements saved input; they do not create an offline submission queue. If a response is lost, keep the pending request and read its status before repeating the action. See Data entry and running Apps.
Edge buffering is a separate feature with its own supported operations and limits. A browser success message, local Edge acceptance and a persisted cloud event are different outcomes.
Record a rollout check
Record device model, OS/browser version, installation mode, viewport, account type, App publication, workspace and date. Run one controlled task, reopen its saved result and check one denied action. Include narrow layout, keyboard/touch, slow or lost connection, a validation error and an expired session. Resolve failures before assigning the device broadly.
For a failure, capture the exact task and safe error text and follow support.