Troubleshooting
Problem
After duplicating an app on Mobile 8.8, the new app has the .json file and the ID in the XML created as uppercase and it should be lowercase.
NOTE: If you have an existing cloned app from Mobile 8.7 and you decided to upgrade to Mobile 8.8, after you publish the app on 8.8, check the ID in your XML and the .json file, if they are uppercase, you need to follow the instructions of this document to fix it as well.
Symptom
Work Order List not being updated on the Cloned App.
Cause
Environment
Mobile for EAM 8.8
Diagnosing The Problem
Doing a test and trying to get the schema of all apps, an error is displayed and the cloned app is not listed with the OOB apps:
- Login on Maximo;
- In a new tab and go to this URL (change the Maximo Server and the port):
http://MaximoServer:port/maximo/oslc/graphite/mobile/schema?regenerate=1
The schema error causes the malfunctioning of the cloned app, reflected by the Work Order List not being updated.
Other way to determine the issue is by debugging the app and clicking in the "Check for Updates" button.
The app does a request to the URL and the amount of data is correct, but due to the schema error, the page is not refreshed to display the updated WO list.
Resolving The Problem
To fix this, you need to rename the JSON file to lowercase, change the ID to lowercase in the app.xml and republish the app.
Here are the steps:
1. Fixing the ID in the app.xml:
- Open the app in the Configuration Tool (the app is downloaded to your local workspace specified in the docker run command)
- Go back to the Application List in the Configuration Tool
- On your local workspace (on your workstation) find the downloaded app and open the /src folder and open the app.xml in a local editor
- On the top element of the XML, change the ID (ID="TECHMOBILEDUP") to be lowercase (ID="techmobiledup").
NOTE: do not change the name of the app, just the case.
- Save and close the file
- Open the app in the configuration application - verify the ID value is lowercase.
2. Fixing the case of the JSON file of the cloned app:
- Go back to your local workspace (on your workstation) find the downloaded app and now open the /build/app/public/data folder
- You will see a JSON file with your app ID name (in this example: TECHMOBILEDUP.json)
- Rename that file to lowercase, such as: techmobiledup.json
- Go back to the Configuration Tool and publish the app to the Maximo/Manage server.
After the app is published, generate the schema again, make sure there's no errors in there and that you'll see your cloned app on the app list.
On your device, reset the app (to perform a clean download of all the new data), login and try to use the cloned app again.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m50000000CbKvAAK","label":"Mobility-\u003EInstallation and Builds"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.8.0"}]
Product Synonym
Mobile; Mobile for EAM
Was this topic helpful?
Document Information
Modified date:
17 November 2022
UID
ibm16840093