IFS Touch Apps are the actual mobile applications which need to be installed on mobile devices. IFS Touch Apps are distributed through the standard channels for the different platforms:
When the IFS Touch Apps is available via a store you search for the IFS Touch Apps and download it to your own device.
The App Resources for the IFS Touch Apps are distributed via the LCS delivery system. They will be found as zip files in your Build Home's client\touchapps folder. Each zip file has a Cloud folder in it, and the App Resource is a DLL file. This DLL file must be deployed in the IFS Touch Apps Server instance's Apps folder.
Selected IFS Touch Apps such as IFS Mobile Work Order are not available via a store but are made available for download through the IFS Touch Apps Server via the LCS delivery system. For detailed installation information about these selected IFS Touch Apps please refer to the relevant section in IFS Applications Business Components and the applicable release notes for that IFS Touch Apps.
In the IFS Touch Apps Server, Customer Portal, security settings for a certain app will be displayed and a role script can be generated. It is important that the security is correctly configured and installed prior to using an app. More details can be found in Touch Apps Server.
Several of IFS Touch Apps can be configured in order to show which fields should be displayed, in which state to fetch notifications, time range format etc.
How and what configuration that exists for a certain app is explained in Touch Apps Business Component.
In order to log in to an IFS App on a mobile device, you need to have a Touch Apps Server installation, user name and password for logging into your installation of IFS Applications. You should also specify the System ID relevant for the IFS Applications installation. On Android devices, these accounts are created using IFS Account Manager, on iOS the login details are entered directly in the login screen of the app. To acquire the System ID, please contact your organization's IFS Touch Apps administrator.
In some situations IFS Application server and/or the Open ID authentication provider (ADFS or DB Identity provider) will be deployed using a SSL certificate that is not issued by a well known certificate authority (e.g.: self signed SSL certificates). In such a situation it may become necessary to install such certificates used by the Identity Provider Server on to the device where mobile application will be used from. In some situations it may be necessary to install the complete certificate chain. Certificate trust varies on different mobile OS versions and also depends on the level of security enforced by each mobile platform.
Please note that for Touch Apps and Aurena Native apps to work properly, the Middleware server needs to have the fully qualified certificate chain. The root certificate and the intermediate certificate need to be linked. If there are any servers in between (proxy server, load balancer, etc), this server is also expected to have the fully qualified certificate chain.
How to use an app is described in the same section as the configuration for a certain app: Touch Apps Business Component.