Technical Blog Post
Abstract
As with all interim fixes, Maximo Asset Management 7.6.0.7 interim fix 005 is cumulative. It contains all fixes from earlier interim fixes, with the addition of new fixes listed in this post.
Body
Tivoli's process automation engine 7.6.0.7 interim fix 005 is available at Fix Central.
| APAR |
Application Name |
Description |
|---|---|---|
| IV89431 |
Security Groups |
Access is required to create work orders and tasks. |
| IV95332 |
Assets |
In the Assets application, for multiple assets, you cannot change the status in the background. |
| IV98279 |
Conditional Monitoring |
In the Conditional Monitoring application, when you add a job plan to a condition, the priority does not populate. |
| IV94406 |
Graphical Scheduling |
In the Graphical Scheduling application, when you use Microsoft Internet Explorer 11, the Gantt view does not render. |
| IV94978 |
Job Plans |
In the Job Plans application, when auto-number functionality is enabled, job plan predecessors are not recorded correctly in the database. |
| IV92471 |
Purchase Orders |
In the Purchase Orders application, when you use the Go To function on a purchase order line and the work order site is different that the main purchase order site, records are not returned. |
| IV93059 |
Automation Scripts |
When you change the status of an asset, an automation script causes an exception. |
| IV97336 |
System Object |
When you install one or more secondary languages, some messages in the browser are incorrectly translated. |
| IV95258 |
System Object |
Maximo searches on the SQL server are adding additional brackets that cause the search to fail. |
| IV90039 |
Inventory Usage |
In the Inventory Usage application, you cannot update an inventory usage document if it has an associated reservation that is canceled. |
To install, see Installing an interim fix in Maximo 7.6.
UID
ibm11113429