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.
The original problem with this function was hitting the database by 2n*n (Asset and Location * total workorder) number of queries while downloading workorders into mobile. The relationship was improved through the public DT DT438297 in 9.0.15 and later on even further by internal enhancement by introducing new relationship assetsrecentwos and locationsrecentwos.
The original implementation of this functionality resulted in excessive database queries—approximately 2n × n (Asset and Location multiplied by total work orders)—during the download of work orders into the mobile application. This approach significantly impacted performance in environments with large datasets.
To mitigate this, improvements were introduced through public defect DT438297 in version 9.0.15, and further enhanced internally by adding new relationships:
- assetsrecentwos
- locationsrecentwos
However, for users with databases containing millions of work orders, it was observed that removing this functionality entirely (as detailed later) provided substantial improvements in data download performance for the Technician mobile application.
For users on version ≥ 9.0.15 and 9.1, the following steps can be taken to disable this feature:
- Remove the relationships:
assetsrecentwos (id="rrb4e")locationsrecentwos (id="r7mpj")
from app.xml
- Remove the associated button from the UI in app.xml with:
id="vde7k"icon="carbon:calendar--heat-map"
Note: changes below are only for versions before 9.0.15, as they were corrected in the OOB application after that.
This article will help improve performance if you observe that the following queries are firing too many times and are costly while you fetch work order data in the Mobile Technician app.
select * from workorder where (((status = 'COMP' or status = 'CLOSE')))......
And if you don't want to use this "View history" function in your application,
Remove the following from app.xml,
1. This will remove the button from the UI. Remove following button
<button icon="carbon:calendar--heat-map" on-click="openAssetWorkOrder" on-click-arg="{{'item':woAssetLocationds.item, 'locItem':woLocationds.item, 'woNum': woDetailResource.item.wonum}}" hidden="{page.state.assetLocation}" disabled="{page.state.loading || page.state.workloading ||page.state.historyDisable}" kind="secondary" id="vde7k"/>
2. This will remove the workorder history records of the Asset.
Remove the following attributes from woAssetLocationds datasource
<attribute name="rel.wobyasset{wonum,description,status,status_maxvalue,statusdate,worktype,siteid}" id="w74bm">
<maximo-child-filter related-path="asset.wobyasset" order-by="-statusdate" limit="3" where="status in ["COMP","CLOSE"]" id="m2ypx"/>
</attribute>
2. This will remove the workorder history records of the Location.
Remove the following attributes from woLocationds datasource
<attribute name="rel.wobylocation{wonum,description,status,status_maxvalue,statusdate,worktype,siteid}" id="n7d8n">
<maximo-child-filter related-path="locations.wobylocation" order-by="-statusdate" limit="6" where="status in ["COMP","CLOSE"]" id="bm558"/>
</attribute>
Keeping history icon to view history
The query contains a status filter in two distinct where clauses, which are costly database queries.
There are few options here :
1) Show all the Wos except Cancelled in Mobile for Workorder history of Asset or Location.
Remove the where clause from app.xml from the following lines:
<maximo-child-filter related-path="asset.wobyasset" order-by="-statusdate" limit="3" where="status in ["COMP","CLOSE"]" id="m2ypx"/>
<maximo-child-filter related-path="asset.wobyasset" order-by="-statusdate" limit="3" id="m2ypx"/>
Same for Locations
<maximo-child-filter related-path="locations.wobylocation" order-by="-statusdate" limit="6" where="status in ["COMP","CLOSE"]" id="bm558"/>
change this to
<maximo-child-filter related-path="locations.wobylocation" order-by="-statusdate" limit="6" id="bm558"/>
2) Update the relationships in Database configuration, to remove “Cancelled” clause from where clause.
This may affect other functionality in your Manage or Integrations where this is being used by including cancelled Workorders as well wherever this relationship is used.
- Go to Database configuration Application
- Search and go to “Asset” record
- Search and select “wobyasset” relationship
- Update where clause from
assetnum=:assetnum and siteid=:siteid and istask=0 and status in (select value from synonymdomain where domainid ='WOSTATUS' and maxvalue not in ('CAN'))
to
assetnum=:assetnum and siteid=:siteid and istask=0
The same goes for Locations
- Go to Database configuration Application
- Search and go to “LOCATIONS” record
- Search and select “WOBYLOCATION” relationship
- Update where clause from
location=:location and siteid=:siteid and istask=0 and status in (select value from synonymdomain where domainid ='WOSTATUS' and maxvalue not in ('CAN'))
to
location=:location and siteid=:siteid and istask=0
3) Create a new relationship that returns only Closed and completed Workorders.
- Update app.xml to use the new relationship. Search for the attribute with
rel.wobyasset and rel.wobylocation and update as rel.NEWRELATIONSHIP
- Remove the where clause – as shared in the very first option.
4) Adding new indexes can also help improve performance
- CREATE INDEX "MAXIMO"."WORKORDER_STATUS_LOC_IDX" ON "MAXIMO"."WORKORDER" ("STATUS", "LOCATION", "SITEID", "ISTASK");
- CREATE INDEX "MAXIMO"."WORKORDER_STATUS_ASSET_IDX" ON "MAXIMO"."WORKORDER" ("STATUS", "ASSETNUM", "SITEID", "ISTASK");
Additional Resources:
Maximo Mobile - Performance optimization
#MaximoMobile #Mobile #Technician #Performance #MaximoMobilePerformance