Problem Description

The doclinks relationship is the primary mechanism for managing attachments in Maximo objects such as workorder, Assets, and locations. In mobile environments, users typically do not require all attachments associated with related objects like JobPlans, SR, INCIDENT, and PROBLEM. However, the default doclinks relationship includes all of these, which can significantly impact the performance of the mxapiwodetail API.

Solution

The linked document below provides comprehensive steps to alter and optimize the doclinks relationship specifically for mobile use cases, resulting in substantial performance improvements.

Problem Description

The Technician application includes a feature that displays the last three work orders performed on the Asset and Location associated with the current work order. While this functionality provides valuable context for technicians, the underlying relationship used to retrieve these historical work orders can be computationally expensive in many Maximo environments—particularly when the WORKORDER table contains millions of records.

Solution

The blog linked below outlines strategies for optimizing this functionality to achieve significant performance improvements. It provides practical guidance on how to restructure queries and leverage best practices to minimize database overhead and improve download time in Mobile.

Problem Description

An attribute existed in the Technician mobile application that caused nearly all assets to be downloaded to mobile devices. This attribute, rel.itemasset, was present under the woReservedMaterialds datasource. This issue not only impacted performance in terms of download timing but also caused the mobile application to hang and eventually crash.

Solution

This attribute has been removed from out-of-the-box (OOB) patch versions:

• Version 9.1.4
• Version 9.0.18
• Version 8.7.25
• Version 8.6.31

Problem Description

A non-persistent attribute related to calibration functionality in the Technician application has been identified as causing API performance degradation for many users.

Solution

Problem Description

The autolocate attribute has been identified as one of the most costly attributes to fetch along with work orders. While removing this attribute may impact Map functionality in the mobile application, it can be useful for performance investigation purposes.

Solution

Problem Description

For many users experiencing API timeout issues, adjusting page size parameters has proven to be an effective approach to improve performance.

Solution

Two key parameters control data fetching behavior:

• download-page-size: Determines the page size for fetching records from the server during mobile download operations
• page-size: Defines the number of records in the datasource and UI, and also controls record fetching in Role-based Applications

Problem Description

For some users, database query performance related to long descriptions has been identified as a bottleneck affecting overall application performance.

Solution

Adding the following indexes has been observed to improve performance. Implement these indexes if they do not already exist in your database:

Primary Index:

Additional Recommended Indexes:

Problem Description

In 9.1, Inbound processing classes associated with MXAPIASSET and MXAPIOPERLOC object structures have been identified as time-consuming operations that negatively impact API performance.

Solution

If you are not utilizing the Health Application in your MAS environment, consider removing the following classes from their respective object structures:

For Object Structure: MXAPIOPERLOC

• Class: psdi.iface.app.location.MoutHealthOperLocProcess

For Object Structure: MXAPIASSET

• Class: psdi.iface.app.asset.MoutAHAssetProcess

Problem Description

In MAS environments, users may experience Cloudflare timeout issues when fetching large datasets for Maximo Mobile applications running in the native/container app. These timeouts occur when data retrieval operations exceed the maximum allowed response time, resulting in failed data synchronization and degraded user experience.

Solution

MAS environments support an asynchronous data fetch mechanism that prevents timeout issues by decoupling the data request from the data retrieval process. This is achieved through the maximo.mobile.async.fetch system property.

How It Works

When this property is enabled, the data fetch process operates asynchronously:

1. The mobile application initiates a data request to the server
2. The server immediately responds to acknowledge the request and begins querying the data in the background
3. The mobile application polls the server every 5 seconds to check if the data is ready
4. Once the data is prepared, it is returned to the mobile application on the next poll

This approach prevents timeout issues by ensuring that the initial request-response cycle completes quickly, while the actual data retrieval happens asynchronously in the background.