IBM Support

IBM Maximo Application Suite - Manage Operator patch 8.7.31

Fix Readme


Abstract

On 26 March 2026, IBM released IBM® Maximo® Application Suite Manage Operator patch 8.7.31. As with all patches, it is cumulative. In addition to the new fixes listed here, all fixes from earlier patches for this version are included.

Content

This patch uses Graphite 2.12.460.
 
Manage and Mobile APAR and Known Issue Fixes
When an APAR or Known Issue has Manual Change in the first column, click the link or go to the Manual Changes section for directions.     
When an APAR or Known Issue has Behavior Change in the first column, click the link or go to the Behavior Changes section for information.
When an APAR or Known Issue has Database Change in the first column, click the link or go to the Database Change Details section for information. 
APARApplication NameDescription
DT422782Configuration ToolSaving and publishing changes in Maximo Application Framework (MAF) running in Docker updates mobile devices but does not always update the browser-based Role-Based Application, despite a successful publish.
DT444162Work Order TrackingWork Orders generated from Nested Job Plans via PM Records display incorrect Estimated Labor Hours.
DT454684Oil & GasHS&E Field class on WORKORDER.WORKTYPE causes a select * from workorder with some REST API Requests.
DT458395Service itemsDuplicating a Service Item with a Classification does not add the attributes to the new Item.
DT458658Work Order TrackingIn Data Sheets, the Required? button on the PM Work Order Data Sheet becomes editable when users enter and remove field values before saving.
DT458712RoutesWhen a user manually creates a Work Order from a PM with a Route that references the same Inspection Form on multiple Route Stops, the Inspection Results on the Work Order display in ROUTESTOPID order instead of the Route Sequence.
DT458749Preventive maintenanceIf a PM record uses a synonym from the WOSTATUS domain in the Add Work Order Status? field, generating a Work Order from that PM sets the Work Order status to the default value of the selected status instead of the chosen synonym value.
DT459796Service requestsIn Incidents, the Drilldown dialog points to wrong site.
DT459906Preventive maintenanceIn Preventive Maintenance, when a Work Order is generated from a PM that has an associated Job Plan, the system does not calculate the Target Finish correctly using the Job Plan Duration.
DT459908InvoicesIn environments where the System Property mxe.app.invoice.crInvNoServRec is set to 1, modifying the Quantity on a Credit Invoice line fails with a java.lang.NullPointerException error.
DT460073MobileIn the Mobile Assets Role‑Based Application, the system retrieves vendor records from a different organization, even though vendor records are organization‑specific.
DT460123ReceivingFor Service receipts, the unit cost is calculated incorrectly when the receipt is voided and re-received.
DT460658
Manual Change
Database Change
RoutesIn the Routes application, when a user enters values in the Asset Description or Location Description fields in Advanced Search, the system does not return results. The entered text disappears when the user moves to another field, preventing searches based on descriptive criteria.
DT461075MobileIn Mobile Navigator, calling the API to download the active package checks for the latest version but downloads an older version. As a result, the Navigator displays an outdated version number in Settings even though the API request succeeds.
DT461212Work Order TrackingIn Work Order Tracking, assigning a Person Group to a Work Order sets the Lead field to the member with the lowest sequence number instead of the Group default when none of the group members have a Calendar or Shift assigned.
DT461534Work Order TrackingAfter multiple Assignments are completed, Work Order Status does not change to Complete.
DT461707Preventive maintenancePMForecastCronTask resource leak.
DT461731MobileIn Mobile Inspections, after clearing the answer of required questions, the count of required questions is incorrect.
DT461902UIWhen a user switches from the Technician application to the Manage Start Center and then returns to the Technician application, the mobile application opens the last viewed Work Order instead of the list.
DT462113MobileIn the Inventory Counting mobile application, changing the count of an item fails with error "The physical count date cannot be after the current date. BMXAA9937E.".
DT462725MobileIn Inventory Counting, clicking the Save button does not work reliably, causing duplicate item entries to be entered in the Counted tabs.
DT462946
Database Change
Purchase ordersThe help text for the PO Line Prorate Service field is inaccurate.
DT462981UIIn Budget Monitoring, saving rules with required fields left blank fails validation with error BMXAA7998E – "You have not entered a value in the following required fields:". After the error appears, the Rules table shows only one row while the record counter indicates two records.
DT463003UIIn Crafts, adding a seventh line causes the incorrect page number to display..
DT463289UIWhen accessing Component Documentation or Developer Documentation in the Maximo Application Framework (MAF) tool, the error "ENOENT: no such file or directory" appears, with a list of the paths.
DT464266MobileOpening Asset Details from a Technician Work Order does not return the user to the originating Technician Work Order detail view. Using the back action instead navigates to the Asset list page in the Assets application.

APARChange details

Steps to Configure the Message
1. Go to Database Configuration → More Actions → Messages.
2. Click New Message.
3. Fill in the following details: 

FieldValue
Message GroupPO
Message KeyopenInvoiceForPO
Display MethodMSGBOX
Message ID PrefixBMXAA
Message ID SuffixE
Display ID?
Checked
Message Value:
Cannot cancel the purchase order because it is referenced by one or more open invoices.
ButtonsChecked: OK
Unchecked: All other buttons

4. Click OK.

DT460658

1. Go to System Configuration → Platform Configuration → Application Designer.

2. Under Applications, filter for ROUTES, then click it.

3. From Common Actions, click Edit Dialog.

4. Click More Search Fields.

5. Locate the Location label. From Common Actions, click Control Properties.

6. Find the Attribute for Part 2 label.

Change the value from ROUTE_STOP.ASSETDESCRIPTION to ROUTE_STOP.LOCATION.DESCRIPTION.

8. Locate the Asset label. From Common Actions, click Control Properties.

9. Find the Attribute for Part 2 label.

Change the value from ROUTE_STOP.ASSETDESCRIPTION to ROUTE_STOP.ASSET.DESCRIPTION.

10. Close the dialog.

11. Click Save in Application Designer.

12. To verify the changes, open the Route application and search by Asset Description or Location Description.

APARChange details
Updated the remarks for the prorateservice field on the POLINE object.
Updated the Route application Search Field Attribute Value.

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"label":"IBM Maximo Application Suite","code":"SSRHPA"},"ARM Category":[{"code":"a8m3p000000hB0QAAU","label":"Manage"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.7.0"}]

Document Information

Modified date:
26 March 2026

UID

ibm17266692