Fix Readme
Abstract
On 10 January 2023, IBM released IBM® Maximo® Application Suite Manage Component patch 8.5.1.
Content
APAR and Known Issue Fixes
| APAR | Application Name | Description |
| DT160590 | Mobile | In Inventory Counting in Maximo Mobile, sorting items the label is Batch rather than Lot. |
| DT169363 | Ticket Templates | Ticket Template hierarchy not always shown correctly in Role-Based Service Requests (SR) Applications. |
| DT172239 | Graphical Assignment | Tool tips do not show Work Order details pressing Alt+left mouse click to view the details of the (gray) assignment bar. |
| DT172848 | Manage Inspection | Attempting to play a video in the Technician Role Based Application fails and an error appears in the logs - "Failed to load resource: the server responded with a status of 500". |
| DT173072 | Mobile | A spinning wheel is display fetching the second set of 20 Service Requests. |
| DT173637 | Mobile | Unable to use the "Go to" capability in the error queue to view/edit work orders with incorrect multi-asset meter readings. |
| DT173641 | Mobile | User is taken to the main Work Order list screen instead of the follow-up work list. |
| DT173643 | Mobile | There is a long delay opening the Role-based Service Request application. |
| DT173762 | Mobile | Submitted SR fails to sync with BMXAA0089E - "Not a valid asset". |
| DT178920 | System Object | Cannot activate Manage application when SMTP is configured. |
| DT178920 | System Object | Cannot activate Manage application when SMTP is configured. |
| DT174070 | Mobile | User is taken to the work order list screen instead of the work order edit list. |
| DT174295 | Mobile | Correction of a failure code results in a sync error |
| DT178218 | Mobile | Error is thrown adding attachment while creating an SR with Location in Maximo SR Mobile Role Based Application |
| DT178612 | Mobile | GPS checkmark not displayed. |
| DT178628 | Mobile | Cache not working well in the Mobile app. |
| DT178638 | Mobile | Inspection app populates all Inspection Form revisions. |
| IJ24576 | Database configuration | The default index Maximo created for a new Object is created on the Maximo data tablespace, not the Index tablespace. |
| IJ32864 | System UI | Double quotation marks at the beginning of an error message display incorrectly as duplicated double quotation mark. |
| IJ34248 | Assets | An error occurs configuring maps with tokens. |
| Preventive maintenance | A Preventive Maintenance record's status can be changed despite missing UI required data (Estimated Next Due Date), leading to erroneous Work Order generation. | |
| IJ39467 | Linked Documents / Attached Documents | Users cannot view PDF files in a Japanese-language environment with the Safari browser with secured attachments. |
| IJ39780 | Qualifications | Error BMXAA4214E occurs when a Qualification does not require a Certification. |
| IJ39803 | Crews | Crew assignment status for a tool assignment shows OK when the asset is decommissioned. |
| IJ40529 | Report | Users cannot upload a JPEG file as a printable attachment. |
| IJ40660 | Condition Codes | Adding a LIFOFIFO condition enabled item on a Job Plan, the condition code value list lookup is not populating the values. |
| IJ40997 | Assignment Manager | Users cannot undelete a row in the Assignment Manager application. |
| IJ41551 | Report | Reports executed through REST are not logged in to REPORTUSAGELOG. |
| IJ43789 | Inventory usage | In the Inventory Usage application, returning an item can incorrectly result in error BMXAA7704E - "The inventory usage lines 1, relate to a deleted inventory reservation. Do you want to proceed with the status change for these lines?". |
| IJ43818 | Work Order Tracking | An Automation Script with attribute launch point does not execute when the value for Long_description field is cleared. |
| IJ43912 | System UI | Users receive error BMXAA4214E filtering on the Print column in the View Attachments dialog. |
| IJ44070 | Work Order Tracking | WOMATSTATUSSYNC creates an entry with user's default insert org instead of the record's org. |
| IJ44123 | Work Order Tracking | Data is not reflected correctly in Assignments updating from Crafts to Crew. |
| IJ44163 | Map manager | Username and Password login window displays opening Map in Maximo with an external url. |
| IJ44229 | Email Listeners | The details section of a Service Request updated or created sending HTML formatted emails to the email listener is not visible in the UI. |
Behavior Changes
| APAR | Behavior Changes |
|---|---|
|
While some customers do generateWork Orders from PMs with null Estimated Next Due Date values, others might not want to allow it. One reason for wanting to prevent this is that if PMs are created from the Asset Templates application, PMs can be created and saved with a null Estimated Next Due Date value. The Asset Templates application has no awareness of fields required in the Preventive Maintenance (PM) application UI. Making this field required in the PM application does not prevent PMs with a null Estimated Next Due Date value from being created.
In the PM application, the status of these PMs can be changed to ACTIVE, because fields required in the application UI are not enforced from the Change Status dialog. Fields required in the application UI are only enforced making modifications with the application tabs, for example, PM, Frequency, Seasonal Dates, Job Plan Sequence, and so on. The behavior here is working as designed.
For customers who do not want to allow Work Order generation from PMs with null Estimated Next Due Date values, that behavior is a problem. This APAR fix addresses this problem outside of the UI required field framework by adding System Property called mxe.app.pm.requireNextDateForActiveStatus, with a default value of 0 (false). Leaving it at 0 allows Users to change a PM's status to ACTIVE and generate work orders from PMs with null Estimated Next Due Date values. Set this property to 1 (true), to disable changing the status of PMs with null Estimated Next Due Date values to ACTIVE.
|
[{"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":"a8m3p000000hB0QAAU","label":"Manage"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.0"}]
Was this topic helpful?
Document Information
Modified date:
10 January 2023
UID
ibm16849203