Technical Blog Post
Abstract
On 25 April 2019, IBM released IBM® Maximo® Asset Management 7.6.0.10 interim fix 005As 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.
Body
Tivoli's process automation engine 7.6.0.10 interim fix 004 is available at Fix Central.
APAR |
Application Name |
Description |
---|---|---|
IJ15109 |
System Object |
After upgrading to Maximo Asset Management 7.6.0.9, you cannot open any work order that has a long description. |
IJ13183 |
Conditional Monitoring |
In the Conditional Monitoring application, when you generate a work order for a measurement point and populate only the Lower Warning and Lower Action fields, you receive a message that says to specify a valid job plan or PM. |
IJ12671 |
Time Zone Rules |
In the Time Zone Rules application, the time zone conversion is completed in the wrong direction. |
IJ12799 |
Work Order Tracking |
In the Work Order Tracking application, data sheets created with a specific organization and site are not associated with the correct Site ID. |
IJ13064 |
System UI Security Scans |
Security defect; User enumeration. CVE-2018-2028; CVSS Base Score: 6.5; CVSS Temporal Score: See X-Force Exchange for the current score. |
IJ13065 |
System UI Security Scans |
Security defect; User enumeration. CVE-2019-4048; CVSS Base Score: 2.1; CVSS Temporal Score: See X-Force Exchange for the current score. |
IJ07111 |
Assets |
When you move an asset with child records to a site, the child records are not created in the new site. |
Maximo Integration Framework 7.6.0.10 interim fix 001 is also available at Fix Central.
APAR |
Application Name |
Description |
---|---|---|
IJ12557 |
Integration Modules |
In the JSON Mapping application, if you map the DOCLINKS attribute DOCUMENTDATA for outbound transactions that contain Base64 encoded data, an error occurs for the JSON processing class when you attach documents. |
Related Information
UID
ibm11111485