General Page
Maximo Mobile applications connect with Maximo by using APIs that reference Object Structures. Users can define a main object and its relationships with other related/child objects. Depending on the size or data load of the target query results, the performance of data gathering and subsequent transactions can be affected. These factors cause slowness in the app. An example is MXAPISR object structure, as reported in the support case TS010972526.
The MXAPISR object structure will be updated in future releases, starting from 8.11 and finishing in 8.12 (planned). Not all the related or child objects for the SR object are needed for the Maximo Mobile Service Requests application, such as SITE, PERSONGROUP, TICKETSPEC, CLASSTRUCUTURE, TKTEMPLATE, RELATEDRECORD and potentially others. We'll be progressively removing each unused related object and refining the MXAPISR object structure. The main objective is to improve performance for the Maximo Mobile Service Requests application and the Maximo Mobile app overall.
Ensure that no customizations are using the objects mentioned above on the mobile device. They will no longer be downloaded nor reside in the device's local storage and will need to be re-added as customized data sources when necessary.
[{"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":"a8m3p000000hAgaAAE","label":"Maximo Application Suite-\u003EMAS Applications-\u003EMobile"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
31 January 2023
UID
ibm16857315