What's new in Maximo Mobile 8.11

Learn more about what’s new and changed in Maximo Mobile 8.11.

Shared device mode

You can share a mobile device between users without sharing your data.

For more information, see Configuring a mobile device for multiple users.

Change default site

You can change your default site from a mobile device.

For more information, see Changing the default site.

Near-field communication (NFC) tag support

You can use your mobile device to scan asset or location NFC tags to show all the work orders for that asset or location.

Mobile Asset Manager enhancements

Asset Manager includes support for attachments, classify assets in offline mode, view assets in a map, and update specification attributes.

Shipment receiving

Shipment receiving is now available in the Receiving function. It allows the storeroom clerk to receive and stock items from another storeroom within the same organization. You can look up shipments, scan packages, receive items into inventory, perform inspections, void receipts, and create rotating assets from assets that are received from other sites.

Issues and transfers

Storeroom clerks can issue items that are reserved for approved work orders. Users now have access to existing inventory usage records on their mobile devices.

FIPS compliance

Maximo Mobile includes limited support for FIPS 140-2 Validation for Android and iOS platforms.

For more information, see Device requirements for Maximo Mobile.

Server selection

When you log in to a server, you can provide the server address URL by scanning a QR code.

You can also provide the server address by selecting an address from a list of recently used servers.

Record attachments

Thumbnail images are displayed for image attachments that are listed in the attachment list view for a record.

Multiple records can share an attachment. If one of the records that shares an attachment is removed from the database, the attachment is not removed from the device.

Service request fields support table domain information

Service request fields now support lookup queries to table domains to specify a field value.

Electronic audits

Electronic audit records can include Maximo Mobile data.

Enable electronic audits on an attribute for an object that can be edited in a mobile app, for example, the wopriority attribute in the WORKORDER object. When you change the attribute value on a mobile device, the username and timestamp for the change is written to the electronic audit table for the object.

For more information, see Electronic audit records

IBM Graphite Declarative Application Framework Developer Reference

The IBM® Graphite Declarative Application Framework Developer Reference includes information for Maximo Mobile developers to develop mobile applications. This reference includes topics on troubleshooting and an API reference.

You can access the guide from the Help menu in the Maximo Application Framework Configuration application.

Maximo Application Framework comment component

A comment component was added to the Maximo Application Framework. You can now add comments in application XML files.

For more information, see Anatomy of an application XML file.

Maximo Application Framework application upgrade

The Maximo Application Framework Application upgrade automatically captures changes to an application in a delta file that can be applied to the new release of the application. Before Maximo Mobile 8.11, delta files were updated manually.

For more information, see Application upgrade using the Maximo Application Framework Configuration application.

Maximo Application Framework Configuration application canvas improvements

In the Maximo Application Framework Configuration application, you can right-click components that are rendered in the canvas area to access a component menu. From this menu, you can cut, copy, paste, and delete components that are displayed on the canvas. When you select an action, the XML code that represents the component in the application XML file is updated. For example, if you delete a component from the canvas area, the XML code for that component is deleted from the XML file, including children of that component.