Mobile Work Order

The purpose of this page is to provide some specific installation information related to Mobile Work Order.

Contents

• About Mobile Work Order
• Touch Apps Server
• Finalize Mobile Work Order Installation - On Premise
• Finalize Mobile Work Order Installation - Cloud
• Android Client Install
• Windows Client Install
• iOS Client Install

About Mobile Work Order

An overview of IFS Mobile Work Order functionality and permissions sets activity grants required to run the application can be found here (end user documentation).

Touch Apps Server

Mobile Work Order is designed to run against the latest version of the Touch Apps Server (TAS).  If operating Mobile Work Order on premise then it is important to keep the TAS up-to-date with the latest release of the TAS.  Documentation on the TAS can be found on the web site IFS Touch Apps Cloud - Downloads.

Mobile Work Order Cloud Configuration

Configuration exists to control the synchronization of Objects and Parts.  To view this logon to the TAS and select to configure Mobile Work Order.  Documentation on the TAS can be found on the web site IFS Touch Apps Cloud - Downloads.

If all Equipment Objects registered in IFS Apps are required to be synchronized then the configuration to "Sync all Objects" should be set.

If all Parts (Inventory, Sales and Purchase Parts) registered in IFS Apps are required to be synchronized then the configuration to "Sync all Parts" should be set.

If the historical work orders of all Equipment Objects registered in IFS Apps are required to be synchronized then the configuration to "Sync all Objects" and "Sync WO History for All Objects" should be set.

Cloud resources where the default where clause is changed when the option "Sync all Objects" is selected:

• Customer
•  CustomerInfoAddress
• MobileObjectMeasurement
• PartSerialCatalog
• HistoricalSeparate

Cloud resources where the default where clause is changed when the option "Sync WO History for All Objects" is selected:

• HistoricalSeparate
  

Note 1: These settings should only be set if the system can handle the numbers of parts and objects that will be synchronized.  If thousands of records will be synchronized by enabling this configuration then the Basic Data for Mobile Part Basic Data and Mobile Object Synchronization Data should be set-up.

Note 2: Only the parts and equipment objects that the end user has site access to will be synchronized.

Finalize Mobile Work Order Installation - On Premise

Prerequisites

Before the manual steps to finalize the Mobile Work Order install are followed ensure that:

• The FNDMOB and MWO components are installed.
• The TAS is installed

Installation Steps

The following steps must be taken to finalize the Mobile Work Order install:

1. Log on or remote desktop to the server where the TAS is installed.
2. Navigate to the below URL replacing the <server> and <port> with the server and port of the IFS Installation and download the mwo.zip file.

http://<server>:<port>/client/touchapps/mwo.zip

Note: The <server>:<port> is the same as the IFS Home Page.

3. Extract the mwo.zip files to the local host.  This should contain the below file structure:

4. Copy the dll files from the mwo\Cloud folder to the TAS installation IFS Touch Apps Server\apps folder as shown below:

5. Logon to the TAS Console and Enable the new mWorkOrder version.  Documentation on how to do this can be found on the web site IFS Touch Apps Cloud - Downloads.

Note: If the mobile users will receive the client files via an MDM or a private store or a custom process then the install can stop at step 5.  If distributing the client files via the TAS download page then continue with the install steps.

6. If using the Android client, copy the Android APK files from the mwo\Android folder to the TAS installation IFS Touch Apps Server\Downloads\<SystemId> folder as shown below:

Note 1: In the above screenshot the <SystemId> of lkppde1134 is used as an example.  The first time a System ID is registered in the TAS console a new folder will be created as IFS Touch Apps Server\Downloads\<SystemId>

Note 2: If installing an Upgrade then the previous APK file should be removed to avoid confusion on which version the mobile users should download.

7. Optional Step if using Mobile Work Order and Quick Facts Touch Apps together.

Copy the Transformer APK files from the mwo\Android\Transformers folder to the TAS installation IFS Touch Apps Server\Downloads\<SystemId> folder as shown below:

Note 1: In the above screenshot the <SystemId> of lkppde1134 is used as an example.  The first time a System ID is registered in the TAS console a new folder will be created as  IFS Touch Apps Server\Downloads\<SystemId>

Note 2: If installing an Upgrade then the previous APK file should be removed to avoid confusion on which version the mobile users should download.

8. If using the Windows client, copy the Windows EXE file from the mwo\Windows folder to the TAS installation IFS Touch Apps Server\Downloads\<SystemId> folder as shown below:

   

   Note 1: In the above screenshot the <SystemId> of lkppde1134 is used as an example.  The first time a System ID is registered in the TAS console a new folder will be created as  IFS Touch Apps Server\Downloads\<SystemId>

   Note 2: If installing an Upgrade then the previous EXE file should be removed to avoid confusion on which version the mobile users should download.

   Note 3: The .ZIP file contains the Install Files for the Windows Client that can be used via an MDM or an Enterprise Store.

9. If using the iOS client, copy the iOS IPA and PLIST files from the mwo\iOS folder to the TAS installation IFS Touch Apps Server\Downloads\<SystemId> folder as shown below:

   

   Note 1: In the above screenshot the <SystemId> of lkppde1134 is used as an example.  The first time a System ID is registered in the TAS console a new folder will be created as  IFS Touch Apps Server\Downloads\<SystemId>

   Note 2: If installing an Upgrade then the previous IPA and PLIST files should be removed to avoid confusion on which version the mobile users should download.

   Note 3: On first navigating to the TAS Download page (in Step 10 below) a PLIST file will be generated based on the TEMPLATE.PLIST file.

10. Navigate to the below URL for the TAS Download page replacing the <TASserver> and <port> with the server and port of the TAS Installation

http://<TASserver>:<port>/Downloads.aspx

Confirm that the clients are available to download.

This should display the clients as downloadable links as shown below:

9. A URL should be created that exposes the TAS to the mobile users so they can download the clients and synchronize with IFS Applications

Finalize Mobile Work Order Installation - Cloud

Prerequisites

Before the manual steps to finalize the Mobile Work Order install are followed ensure that:

• The FNDMOB and MWO components are installed.
• A System ID has been registered in the IFS Touch Apps Cloud.
• mWorkOrder version has been enabled in the IFS Touch Apps Cloud.

Installation Steps

1. Navigate to the below URL replacing the <server> and <port> with the server and port of the IFS Installation and download the mwo.zip file.

http://<server>:<port>/client/touchapps/mwo.zip

Note: The <server>:<port> is the same as the IFS Home Page.

2. Extract the mwo.zip files to the local host.  This should contain the below file structure:

3. Distribute the client files to the mobile users via an MDM or a private store or a custom process.

Android Client Install

If distributing Mobile Work Order via an MDM or a private store or a custom process then not all of these installation steps will be relevant.

Prerequisites

Before installing the Android client ensure that:

• The Finalize Mobile Work Order Installation - On Premise or Cloud steps have been followed.
• A User has been created in IFS with access to the permission set Activities under the TouchApp mWorkOrder3 folder and the functional role TOUCHAPP_RUNTIME.
• The device allows the install of applications from unknown sources.

Installation Steps

1. Navigate to the TAS download page on the android device and download the required version of the client as shown below:

2. Once downloaded, Install Mobile Work Order as shown below:

3. Once installed, open Mobile Work Order and Activate the client entering the User ID, Password, Service URL and System ID.  Once Activation is completed the home screen will be displayed as shown below:

Note 1: The System URL is the URL to connect to the TAS.  If connecting from outside the internal network then this will need to be an external connection that routes to the TAS.

Note 2:  The home screen may be different depending on the permission set Activities that have been granted to the mobile user.

Windows Client Install

Prerequisites

Before installing the Windows client, ensure

• The client is running Windows 8.1 Pro with update 2919355, or Windows 10 Home, Windows 10 Pro or Windows 10 Enterprise.

• The Finalize Mobile Work Order Installation - On Premise or Cloud steps have been followed.
• A User has been created in IFS with access to the permission set Activities under the TouchApp mWorkOrder3 folder and the functional role TOUCHAPP_RUNTIME.
• Ensure you can sideload apps onto your device.  Instructions on how to configure your device are here >>

Installation Steps

1. Navigate to the TAS download page on the windows device and download the required version of the client as shown below:

   

    

2. Once downloaded, Install Mobile Work Order as shown below:

   

   Note 1:  This is a self-extracting installer, and when run, will verify that the client is suitably configured

   Note 2: During the process, a security certificate may need to be installed. This is done by the installer, but will require user permission to complete the task. If using an account that is a member of the local administrators group, a simple dialog may appear.

   

   The Yes option must be selected, to allow installation of the certificate.

   If the account is a member of the local administrators group, then a different dialog will appear, and an account which is a local administrator, along with the appropriate password, must be entered in order for the installation of the certificate to succeed.

   

3. Once installed, open Mobile Work Order and Activate the client entering the User ID, Password, Service URL and System ID as shown below:

   

Note: The System URL is the URL to connect to the TAS.  If connecting from outside the internal network then this will need to be an external connection that routes to the TAS.

4. Once Activation is completed the home screen will be displayed as shown below:

   

   Note:  The home screen may be different depending on the permission set Activities that have been granted to the mobile user.

    

.

iOS Client Install

If distributing Mobile Work Order via an MDM or a private store or a custom process then not all of these installation steps will be relevant.

Prerequisites

Before installing the iOS client ensure that:

• The Finalize Mobile Work Order Installation - On Premise or Cloud steps have been followed.
• A User has been created in IFS with access to the permission set Activities under the TouchApp mWorkOrder3 folder and the functional role TOUCHAPP_RUNTIME.
• The TAS download page must be accessible via a https URL for the mWO client to be downloaded to an iOS device.

Installation Steps

1. Navigate to the TAS download page on the iOS device and download the required version of the client as shown below:

2. The first time Mobile Work Order is opened you will get a popup saying "Untrusted Enterprise Developer". If the popup does not have a Trust option then:

   Open the Settings app on your device

   Select General Select 'Profile' or 'Device Management' or 'Profiles & Device Management'

   Click 'IFS World Operations AB'

   Click 'Trust "IFS World Operations AB"

   Click 'Trust'

   Open the App again

3. Open Mobile Work Order and Activate the client entering the User ID, Password, Service URL and System ID.  Once Activation is completed the home screen will be displayed as shown below:

Note 1: The System URL is the URL to connect to the TAS.  If connecting from outside the internal network then this will need to be an external connection that routes to the TAS.

Note 2:  The home screen may be different depending on the permission set Activities that have been granted to the mobile user.