Fix Readme
Abstract
On 29 December 2022, IBM released IBM® Maximo® Asset Management 7.6.1.1 interim fix 023. As with all interim fixes, it is cumulative. In addition to the new fixes listed here, all fixes from earlier interim fix releases for this Feature Pack are included.
Content
Interim fix 023 is the final interim fix released for Maximo 7.6.1.1.
Tivoli's process automation engine 7.6.1.1 interim fix 023 is available at Fix Central.
| APAR | Application Name | Description |
| IJ44151 | Graphical Assignment | In Spatial Scheduling Scenario dat files, the parameter "Allow Secondary Work Zone Assignment" is always false and the parameter "Match Work Zone" is always true. |
| IJ40906 | Integration | Data Sheet import for calibration fails. |
| IJ43951 | Security | For more information about a security vulnerability, see IBM X-Force Exchange. |
| IJ43544 | Graphical Assignment | In Graphical Assignment, attempting to assign labor when the property mxe.skd.syncwodates is set to 1 results in error BMXAA4589E - "The start date must be before the finish date". |
| IJ35446 | Assets | In the Assets application, an error occurs changing an item number. |
| IJ42091 | Item Master | When Different Sites share an Item Set, a System Message is displayed: BMXAA2093E "There are multiple default vendors for this item". |
| IJ42208 | Graphical Scheduling - Large Project | Filtering on a column in Graphical View for Graphical Scheduling - Large Projects results in an error in the UI. The logs include the error: "Failed to invoke Method: async_load_gantt_pages with signature [null] with args". |
| IJ41810 | Security | For more information about a security vulnerability, see IBM X-Force Exchange. |
| IJ41699 | Assets | Shipment releases Asset with Ancestor but without Parent. |
| IJ41709 | Work Order Tracking | Warning message BMXAA0159W does not appear rescheduling an assignment without labor to a date after the Work Order's "Finish No Later Than" date. |
| IJ41412 | Graphical Scheduling | In Graphical Assignments, Labor hours duration is mismatched splitting work. |
| IJ41316 | Work Order Tracking (Cal) | In Work Order Tracking, rescheduling an assignment to a date after the Work Order's "Finish No Later Than" date does not generate a warning message. |
| IJ41230 | Security | For more information about a security vulnerability, see IBM X-Force Exchange. |
| IJ40875 | Integration | When the Status is changed using MIF, and CHANGEBY information is sent, Maximo does not use the value sent in the transaction to fill the CHANGEBY field in the WORKORDER and WOSTATUS tables. It uses the logged-in user who sent the transaction. |
| IJ30938 | System UI | Special characters are being cut off the top of the values in the description & long description field. |
| IJ40656 | Integration | Generating the XML schema for an Object Structure causes an exception to be thrown because some of the Object Structure values have the hierarchy path set with "\" delimiter instead of "/". |
| IJ40524 | Create Requisition | Duplicating a Purchase Requisition, the Issue on Receipt? checkbox is cleared even though there is a value in Work Order field. |
| IJ29093 | Inventory | Maximo allows a user to be set to inactive despite that user having pending transactions. |
| IJ33742 | Work Order Tracking | Cannot add file attachments to Work Orders on iPad or iPhone in a Maximo 7.6.1.2 interim fix 007 environment. |
| IJ30647 | System UI | When configured to use the iot18 skin, Maximo field hover help text merges with the data displayed in the field. |
| IJ38123 | Ad Hoc Reporting | There is a security vulnerability in Ad Hoc reports. |
| IJ35837 | Install / Upgrade | In environments upgraded to Maximo Asset Management 7.6.1.2, random groups are visible. |
| IJ26420 | System UI | The Accessibility Help link is broken. |
| IJ24500 | Linked Documents / Attached Documents |
In any Maximo application, if you create a document in a library, attach the document to a record, and then remove the attachment later, the library record is deleted.
|
The final Maximo Integration Framework 7.6.1.1 interim fix is MIF interim fix 011.
IBM Control Desk 7.6.1.0 and 7.6.1.1 use Tivoli's process automation engine 7.6.1.0. This interim fix can be applied to Control Desk 7.6.1.0 and 7.6.1.1.
Related Information
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"ARM Category":[{"code":"a8m50000000CbP7AAK","label":"Install-\u003EFixpack"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.1","Line of Business":{"code":"LOB59","label":"Sustainability Software"}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWT9A","label":"IBM Control Desk"},"ARM Category":[{"code":"a8m500000008b3TAAQ","label":"Miscellaneous Category (Portal, UI, Maximo, Install)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.1","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
29 December 2023
UID
ibm16852153