Maximo Asset Management 7.6.0.6 interim fix 008 released

System User Interface

In a custom Everyplace application, the lookup in the toolbar does not work.

Map Manager

In the Map Manager application, you cannot find signature options that you created with Visible set to false and then added to a layer.

Service Requests

In the Service Request application, you cannot create a work order from a service request that was created with a linear asset.

Work Order Tracking

In the Work Order Tracking application, on the Actuals tab, after you add a start and stop timer, the End Date field is populated with incorrect data.

Work Order Tracking

In the Work Order Tracking application, when you use the mechanical clipboard, a class error occurs.

System Properties

The mxe.pluss.tooltip.delaytime property does not apply to all tools.

Cron Task Setup

When a scheduled job runs once from multiple JVMs, the job fails.

System User Interface

When a screen reader is enabled the focus is in a Menu button or a Lookup button, when you select the button, nothing happens.

All Applications

When creating a new change record, you attempt to select a value from a field. Instead of retrieving the record, you receive the following message: BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 1795.  The record could not be retrieved from the database.

Graphical Assignment

When the default browser language is set to French, in Gantt view, Maximo prints incorrect reports.

Automation Scripts

When you create a custom script for the USEREXIT.USEREXIT.IN.BEFORE script, a null error occurs.

System Object

When you publish report object structures in an LDAP environment an error occurs.

System User Interface

When you use Microsoft Internet Explorer 11 and the Document to the Default Location property is not selected, a button is missing on the Attachments dialog box.

Assets

When you use a unique ID condition in the condition expression manager, an error occurs.