Mobile App - Administration

Several components are involved in the Innosoft Mobile Field Service process. The Mobile App is installed on the technician's Windows, Android or iOS device and provides the technician with the necessary data. For many functionalities, no permanent online access to the planning data relevant to the technician is required, as the Mobile App replicates relevant planning data from the central database locally via a synchronization mechanism. The App Server (or App Backend) provides a corresponding interface for data exchange between the Mobile App and the office staff and is essential for using the app. In addition, the App Server contains the Admin Console, a web-based interface that you can use to make most of the relevant configurations.

Additional components are usually required for a complete process. The following table gives you an initial overview.

System component	Description
Mobile App (Innosoft Mobile)	Application that the technician installs on their Windows, Android or iOS device and in which the data is recorded in the field. The app is made available on Android and iOS via the platform-specific app store. You can find out more about deploying the Windows App in Setting up the Windows Mobile Clients.
App Server (App-Backend & Admin-Console)	Interface that the Mobile App uses to exchange data with the office staff. A large part of the administration is carried out via the web-based interface (Admin Console).
Print Service	Optional service (or scheduled Windows task) that processes print jobs and generates a .pdf document. The technician can print service reports, weekly reports and (technical) reports in the Mobile App. A customer contact person and the technician usually sign the data in the .pdf document. The signature is embedded in the .pdf document. The generated .pdf document can then be sent automatically by e-mail (see File Sender). You define the structure of the printout and which data is included in the FSM via Quick Report Files (see Reports).
File Sender	Optional service (or scheduled Windows task) which, among other things, sends the .pdf documents created via the Print Service as an e-mail, e.g. to customer contacts.
Push Notifications Sender Service	Optional service that notifies the Mobile App for iOS and Android about changes in the head office (e.g. new assignment for a technician) and thus triggers data synchronization on the Mobile App. You can find out more about automatic data transfer in App Transmission Status, automatic Data Transmission, App Change Messages .
File Server Web Api	Is required if the App Server cannot/may not access the document directory directly. Not required by default, as the App Server accesses document directories directly. For further information, see App Server: Access to the Innosoft Document System.
External Open Id Provider	You can configure external Open Id providers, such as Microsoft EntraId, via the Admin Console. The technician logs in via this within the Mobile App. The login is required to access the App Server when exchanging data. By default, the login within the Mobile App is carried out using the login data of the corresponding Innosoft user (see Administration of Users). You can find out more about setting up external OpenId providers/OAuth in Setup: OAuth / Open Id Connect in the AppServer.
Field Service Management (FSM) Portal	Not only dispatchers can use Field Service Management. Technicians can also access some functionalities such as the ticket system. The Mobile App provides a portal for specific FSM pages. Find out more about the integration of FSM pages in Integration of FSM pages in the App (FSM Portal) .

Further information can be found in the following articles: