Technical Blog Post
Abstract
As with all Interim Fixes, Maximo Asset Management 7.6.0.8 interim fix 018 is cumulative. It includes all fixes contained in earlier Interim Fixes, with the addition of new fixes listed in this post.
Body
Tivoli's process automation engine 7.6.0.8 interim fix 018 is available at Fix Central.
APAR |
Application Name |
Description |
---|---|---|
IJ09760 |
Database Configuration |
Asset function formulas which use two levels of function cause an error when implemented. |
IJ08742 |
Work Order Tracking |
In Maximo Anywhere, when you enter labor actuals on a device that has a different time zone to the Maximo server, dates are not validated correctly. |
IJ10665 |
System User Interface |
In an environment that has multiple languages, defaults set for YorN parameters do not work properly for languages other than the base language. |
IJ10684 |
Assets |
In the Assets application, the map display in Maximo Spatial maps is not able to zoom to the same level of quality as it does in ESRI maps. |
IJ10597 |
Changes |
In the Changes application, when you create a service request and then create a follow-up change request, the work log tab displays the incident work log and not the service request work log. |
IJ10755 |
Graphical Scheduling |
In the Graphical Scheduling application, not all fields are translated into Portuguese. |
IJ07795 |
Report |
In the Report application, rich text fields are vulnerable to cross-site scripting (XSS). |
IJ02520 |
Service Requests |
In the Service Requests application and in the Incidents application, when you search for tickets, only open tickets are returned. |
IJ09098 |
Work Order Tracking |
In the Work Order Tracking application, when you export activities to Microsoft Excel, predecessors are not visible. |
IJ10063 |
Purchase Orders |
The purchase order/purchase requisition collaboration switch is not working as expected. When the PCVALUE is equal to 1, the status of the purchase requisition automatically changes to closed after the creation of a purchase order. |
IJ07338 |
Preventive Maintenance |
When you change the status of an eSIG enabled preventive maintenance record and the preventive maintenance record has a forecast, the eSIG gets caught in a loop. |
IJ09312 |
Work Order Tracking |
When you have a work order in WMATL status and add another material line, Maximo Asset Management changes the work order status to approved when you delete the new material line. |
IJ09678 |
Chart of Accounts |
When you use the Maximo Integration Framework to import 1000 GL components, an error occurs. |
IJ10051 |
Service Requests |
In the Service Requests application, when HTML code is entered in the Description field, Java script is executed. |
IBM Control Desk 7.6.0.3 uses Tivoli's process automation engine 7.6.0.8. This interim fix can be applied to Control Desk 7.6.0.3.
For product compatibility, see Control Desk, Maximo and Tivoli's process automation engine version compatibility.
To install, see Installing an interim fix in Maximo 7.6.
UID
ibm11113465