Technical Blog Post
Abstract
As with all interim fixes, Maximo Asset Management 7.6.0.7 interim fix 012 is cumulative. It contains all fixes from earlier interim fixes, with the addition of new fixes listed in this post.
This is the final interim fix release for Maximo Asset Management 7.6.0.7.
Body
Tivoli's process automation engine 7.6.0.7 Interim Fix 012 is available at Fix Central.
| APAR |
Application Name |
Description |
|---|---|---|
| IJ04876 |
Incidents |
In the Incidents application, you cannot create an investigation if an incident has an inactive person record. |
| IV96628 |
Job Plans |
In the Job Plans application, when using the application import option to import a job plan with a job plan task, the NESTEDJOBPLANID field does not populate. |
| IJ06031 |
Receiving |
In the Receiving application, when you create assets by receiving items and asset number are automatically created, the asset numbers are not sequential. |
| IJ05595 |
Work Order Tracking |
In the Work Order Tracking application, the ISSUETYP lookup field is not validated. |
| IV90580 |
Work Order Tracking |
In the Work Order Tracking application, when a work order status change fails with multiple child work orders, multiple dialog boxes are displayed. |
| IJ04806 |
Work Order Tracking |
In the Work Order Tracking application, when you duplicate a work order with specifications, the copied work order has more specifications as the original and saving the work order does not work. |
| IJ04373 |
System Object Security Scans |
Security vulnerability: Apache issue: CVE-2016-1000031; CVSS Base Score: 9.8; CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117957 for the current score. |
To install, see Installing an interim fix in Maximo 7.6.
UID
ibm11113549