IBM Support

IBM Maximo Application Suite - Manage Component patch 8.6.26

Fix Readme


Abstract

On 5 May 2025, IBM released IBM® Maximo® Application Suite Manage Component patch 8.6.26. 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

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 Behavioral 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.
 
APAR Application Name Description
DT178586 Database configuration In the Database Configuration application, creating a simple view from LABTRANS causes an error.
DT395000 Report Unable to sync Cognos users in MAS Manage due to a syntax error.
DT396483 Report A user with an email address containing upper-case letters cannot schedule a report with URL attachments, receiving error BMXAA8113E - "The following email addresses are not in the Maximo database: MAXIMO_User@my.maximo.com. Remove these addresses and resubmit the report request.".
DT397288
Manual Change
Classifications In Classifications application, the Classification Attributes for Linear Asset and Feature Specifications of the  'DATEVALUE' attribute operate inconsistently.
DT397298 Maintenance Manager Changes to Labor or Crew assignments in the Role based application are not reflected in the Manage Work Order assignment.
DT416661 Report Users cannot run Direct Print with Attachments with some PDF attachments
DT418781 Mobile In a non-English base language environment in the Technician role-bases app, receiving Material in a work Order causes error BMXAA4024E - "The synonym value ISSUE is not valid for the domain ISSUETYP, siteid=XXX, orgid=YYY. Specify a valid synonym value. You can find a list of valid values using the Domain application." to display.
DT419672 System (Object) When Locale is set to en_CA, entering Time values into any field causes error BMXAA4155E - "The time format is not valid. Make sure a valid value is entered that conforms to the date time properties of the current locale.".
DT422710 Mobile In the Mobile Technician app Worklog, the user is prompted to save or discard changes without having added to or made changes to the log.
DT422988 Spatial Resetting the mobile app does not delete the Vector Tile Package (VTPK) on the device.
DT423394 Scheduler/Crew In Scheduler Data Manager, validating a query does not display the number of records.
DT424155 Mobile Multiple timers start when the Mobile user switches between List view and Map view.
DT424163 System (Object) Protocol reference in JSON file response under response info href is http instead of https.
DT424186 Mobile Answers using multiple Inspection Form revisions are saved for the same Inspection.
DT424321 Mobile Labor and Failure Reporting Details visible in Manage are not visible in the mobile Technician application.
DT424373 Scheduler/Crew In Scheduler Data Manager, when a shift has been defined with a Pattern that is not a multiple of 7, Calendar validation throws the error "Shifts must be applied for the entire span of the schedule.".
DT425583 System (Object) In Work Order Tracking, selecting a record, and clicking GL Account lookup causes error BMXAA6714E - "The data for the next record in the mboset could not be retrieved for the SQL query.".
DT425606 UI Page will scroll down as its focusing on "Select Groups" to the bottom of the page
DT425833 Scheduler/Crew In Graphical Assignment, Labor records that do not share the same Skill Level and match Labor 1 in Work Order requirements are highlighted in blue.
DT426626 Scheduler/Crew In Graphical Assignment, Emergency Cron Task execution subsequently removes the ability to make changes to the record.
DT433198 Mobile Flow-controlled Work Orders do not work as expected.
DT433401 Mobile After revision, Inspection Forms with 400+ questions, each with a condition, do not appear in Manage.
DT433905 Mobile In Inspection Forms, the Executed Date field turns red when cleared, as expected for a required field. However, the form still allows submission, and the previously entered date is saved despite the field being cleared.
DT435138 UI Scheduled Start/Scheduled Finish fields automatically select the current date.
DT435373 Mobile SR Mobile incorrectly displays sub-categories.
DT435467 Mobile Cannot select options in Multiple Choice Domain responses.
IJ44449 Conditional Monitoring Condition Monitoring is creating new Work Orders even though there is an existing open Work Order.
IJ47388
Manual Change
Report Running the Location Hierarchy report, selecting SITEID using lookup and that value is at the maximum length (default: 8 characters), the DB2 database throws an exception.
IJ47470
Manual Change
Report Running the calibration_error.rptdesign BIRT report shows Data Sheet Status as blank.
IJ48283 Item Master Adding a new item results in errors BMXAA7136E - "Validation failed when the database default values were set. See the associated message for more information." and BMXAA7831I - "Do you want to apply the tax-exempt status to the organization level for the item, and to the vendor level for the item?".
APAR Change instructions
DT397288
A. Database Configuration
Add a date value attribute for the FEATURESPEC and ASSETFEATURESPEC objects. For example:
1. Open Database Configuration.
2. Filter for the FEATURESPEC application.
3. Click the Attributes tab.
4. Add a date value attribute:
  • Attribute: DATEVALUE
  • Type: DATE
  • Title: Date Value
  • Description:- Date Value
  • Length: 4
  • Leave the Persistent? toggle on
Repeat for the ASSETFEATURESPEC object.
Follow the steps in the documentation at Adding attributes to objects
 
Modify the ASSETATTRID attribute for FEATURESPEC and ASSETFEATURESPEC objects. For example:
1. Open Database Configuration.
2. Filter for the FEATURESPEC application.
3. Click the Attributes tab.
4. Filter for the ASSETATTRID attribute.
Change the Class name: Class - psdi.app.ticket.FldTKCommonSpecAssetAttrid
Save.
Repeat for the ASSETFEATURESPEC object ASSETATTRID attribute.
Once Database Configuration changes are done, apply them by following the steps in the documentation at Configuring the database in administration mode.

B. Application Designer
Make XML changes required in asset.xml and feature.xml to implement UI changes for the Date Value field.
1. Open Application Designer.
2. Filter for the ASSET application, and click it.
3. Export Application Definition. Save the file as asset.xml
4. Open the asset.xml file in a text editor.
5.1 Search for id "AssetFeature_specifications_table_tablebody_4"
5.2 After that, add the line
<tablecol dataattribute="datevalue" id="AssetFeature_specifications_table_tablebody_date_11" lookup="datelookup"/>
5.3 Search for id "AssetFeature_specifications_table_1_griddetails2_3b"
5.4 After that, add the line
<textbox dataattribute="datevalue" id="AssetFeature_specifications_table_1_griddetails2_date_8" lookup="datelookup" smartfilloff="true"/>
6. Save asset.xml
7. In Application Designer, import the modified asset.xml file.
8. Save changes
 
9. Filter for the FEATURE application, and click it.
10. Export Application Definition. Save the file as feature.xml
11. Open the feature.xml file in a text editor.
12.1 Search for id "specification_featurespectable_tablebody_4"
13.2 After that, add the line
<tablecol id="specification_featurespectable_tablebody_4b" dataattribute="datevalue" lookup="datelookup"/>
13.3 Search for id "specifications_specifications_table_1_griddetails1_row_col2_sec"
13.4 After that, add the line
<textbox id="specification_featurespectable_1_griddetails_date_4b" dataattribute="datevalue" lookup="datelookup" smartfilloff="true"/>
14. Save feature.xml.
15. In Application Designer, import the modified feature.xml file.
16. Save changes.
IJ47388 Use the Report Administration application to import loc_hierarchy.rptdesign manually.
IJ47470 Use the Report Administration application to import calibration_error.rptdesign manually.

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

Document Information

Modified date:
20 June 2025

UID

ibm17231539