|Front page › Concepts › Registrations made with the mobile client||Search|
Some of the mobile client’s functions work by initially just recording user actions on the mobile unit and then transmitting them later to the IMMS server. This local recording of data and steps ensures that the mobile client can be used in most situations without continuous access to the wireless network, so the user’s work does not go down the drain if the connection is lost. Data is, for example, stored locally when items are moved to a location or a transport unit, when items are shelved, when items are picked or when the status of a transport unit is changed.
To ensure that IMMS has the most accurate picture of the state of things, the mobile client will attempt to transmit the registrations to the server as soon as an activity is finished. This is done automatically in the background without the user needing to do anything further. If the registrations are not successfully transmitted, the mobile client only makes another attempt after a short period of time has passed.
In general, the user does not have any influence on automatic sending of registrations. However, the user who performed the activities is in effect the only one who can ensure that IMMS receives the information contained in the registrations. For this reason, registration transmission is an integrated part of the “log off” procedure, and the user’s only opportunity to initiate the transmission of registrations on his/her own is through logging off. If registrations are stored on the mobile client that cannot be delivered when the user logs off, then he/she is challenged to establish a connection to the network before the session is completely terminated.
Registrations are automatically sent to the IMMS server without any action required on the part of the user. However, the user can see the automatic sending status in the notification bar at the top of the screen. (If needed, refer to Introduction to the IMMS mobile client - Registrations).
When a registration is made, it is transmitted immediately and if the transmission is successful, auto-sending just waits until the next registration is made.
If a registration cannot be delivered, it is placed in a queue for later delivery. As long as there are registrations in the queue, the mobile client will automatically attempt to send them at routine intervals
Auto-sending can be configured with one of three different intervals:
If a new registration is made while there is a queue, then the new entry is just placed in the back of the queue and transmission is delayed until the next auto-sending.
If there is an error in a registration, it is not placed in the queue but is stored until the next time a user logs onto IMMS and is then sent again.