Configuring Mobile Services

See Archibus Configuration Options for instructions on enabling mobile services.

See Configuring Archibus Mobile Applications (User Help) for instructions on enabling a mobile user.

Using Chrome to Troubleshoot Mobile Apps

Using Chrome to troubleshoot and test mobile applications is recommended. Before opening the AppLauncher, you will want to clear the cache:

1. In Chrome, open the Settings dialog
2. Select "Show Advanced Settings" to view all settings
3. Go to Privacy > Clear Browsing Data
4. Select to Empty the cache, Clear data from hosted apps, and Delete cookies and other site and plug-in data

To open the AppLauncher in Chrome, go to

http://localhost:8080/archibus/schem...her/index.html

Use Chrome Tools > Developer Tools to debug mobile applications.

Managing Mobile Apps

Several views have been provided in Web Central for managing and editing the mobile forms. These can be found in the Navigator under: System / Mobile Apps Manager

For example, the Manage Asset & Equipment Surveys task ( ab-products/workplace/assets/mobile/ab-eq-survey-console.axvw ) lists the assigned surveys and their statuses. From this view, the Mobile Apps Manager can view survey results, create new surveys and edit existing survey fields.

Personalization and Upgrade

Mobile technology is moving rapidly. Mobile devices change regularly as do the third-party libraries that Archibus uses for mobile. As such, those who personalize mobile apps should be prepared for a faster rate of change in the mobile environment than they would in other parts of the Archibus product.

Within reason, the server-side portion of mobile -- the DWR services and the Workflow Rules that are part of the mobile framework -- will be upward compatible, meaning that we may add services from release-to-release but we will not remove services. This means that if your mobile app calls Archibus server-side workflow rules in one release, that same call will work in the next release. You can upgrade your Web Central server, and keep your mobile app deployment the same if you wish.

However, do be prepared for more rapid changes in the client-side apps, the client-side JavaScript API, and the client-side libraries. The client-side code includes all content in the \schema\ab-products\common\mobile\ subfolders, including the AppLauncher and common subfolders. That is to say, if you make your own changes to the files in the \schema\ab-products\common\mobile\ subfolders, you may need to update your changes in future revisions of Archibus and rebuild your mobile apps.

Localizing

You localize mobile apps in the same way that you localize other Archibus components (see Reading or Writing Translatable Files ) with one important exception: after reading and writing the translatable files, you must rebuild and republish the mobile apps in the native device. For information, see Localizing the Mobile Apps.