Fix Readme
Abstract
On 30 July 2021, IBM released IBM® Maximo® Asset Management 7.6.1.2 interim fix 011. As 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.
Content
Tivoli's process automation engine 7.6.1.2 interim fix 011 is available at Fix Central.
| APAR |
Application Name |
Description |
|---|---|---|
| IJ33496 |
UpdateDB Utility |
Updatedb fails on the script V7612_02 with a null pointer exception. |
| IJ33456 |
Inventory usage |
In the Inventory Usage application, when you update the status of an item and a conditional expression is used, the system freezes. |
| IJ21217 |
Anywhere |
When you run an Maximo Anywhere build script from a command shell, an error occurs. |
| IJ33136 |
Graphical Scheduling |
When you configure a data restriction filter for the Graphical Scheduling application, then open the application, the filter is ignored. |
| IJ33055 |
Graphical Scheduling |
In the Graphical Scheduling application, you can save null values in mandatory fields. |
| IJ32752 |
Work Order Tracking |
In the Work Order Tracking (Tr) application, when you save a record and an error occurs, the displayed labor costs do not match the labor costs in the order. |
| IJ33011 |
Inventory |
Updates to date and location details for inventory in the Work Order Tracking application are not reflected in the Inventory application. |
| IJ32791 |
Job Plans |
In the Work Order Tracking application, when you create an order that uses a job plan that is associated with a route, the work units are not inherited from the route stops. |
| IJ32706 |
System UI Security Scans |
Maximo applications that allow users to add attachments also allow malicious scripts to be uploaded and executed. |
| IJ32696 |
Work Order Tracking |
In the Work Order Tracking application, when you update start and end times for labor, the regular hours are not calculated correctly. |
| IJ32658 |
Inventory usage |
In the Inventory Usage application, when you complete a record, an error occurs. |
| IJ32045 |
Purchase requisitions |
When auto-numbering is enabled for purchase requisition numbers at the organization level and you run the Reorder cron task, requisition numbers are not incremented correctly. |
| IJ32277 |
Service requests |
In the Service Requests application, when you search for decimal values, the localization settings are ignored. |
| IJ32330 |
Work Order Tracking |
In the Work Order Tracking application, when you close or complete several calibration work orders, an error occurs. |
| IJ32156 |
System UI Security Scans |
Unvalidated data that Maximo applications export to spreadsheet files is vulnerable to malicious injection attacks. |
| IJ31900 |
Assets |
In the Assets application, you can move assets that are associated with open work orders to other sites and locations. |
| IJ31898 |
Install/Upgrade |
UpdateDB fails when the option |
| IJ31061 |
Integration Modules |
After LDAP security authentication is configured in Maximo, password-related options remain accessible through the user interface. |
| IJ31669 |
Purchase requisitions |
In the Purchase Requisitions application, when you approve a purchase order, then revise it and try to reapprove the purchase requisition, authorization errors occur. |
| IJ30779 |
Preventive maintenance |
For meter-based PMs that already have forecast data, the forecasting cron task does not generate additional forecasts. |
| IJ31129 |
Workflow Designer |
In the Purchase Requisitions application, workflow assignments are not routed correctly. |
| IJ30385 |
JSON Resources |
In the JSON Resources application, new records that contain a path with more than 50 characters cannot be created. |
| IJ30958 |
Work Order Tracking |
When you generate a work order from a PM that contains a route that has 800 or more stops, then open the order in the Work Order Tracking application, system performance is slow. |
| IJ31027 |
Inventory usage |
In the Inventory Usage application, the Create Remaining Usage Lines action does not create usage lines correctly. |
| IJ31024 |
System Object |
In the Maximo Anywhere app for Service Requests, user tokens are not consumed correctly. |
| IJ30608 |
System Object |
The licensing information for Maximo applications in the License Usage Monitor application does not match the licensing information in those individual applications. |
| IJ30515 |
License Usage Monitor |
In the License Usage Monitor application, users that have read-only access to Industry Solution applications do not receive the correct licenses. |
| IJ30716 |
Preventive maintenance |
In the Work Order Tracking application, for work orders that were generated from a PM that uses a crew work group on the job plan, the orders are not assigned to the crew work group. |
| IJ30530 |
Graphical Work Week |
In the Graphical Work Week (GWW) application, filtering does not work correctly. |
| IJ28306 |
Work Order Tracking |
When a user's time zone differs from the time zone of the database or the application server, an incorrect date selection is displayed. |
| IJ19213 |
Report |
In the Report Administration application, the Report Usage report generates incorrect data. |
| IJ25335 |
System Object |
Inactive database sessions are not purged correctly from the MAXSESSION database table. |
| IJ28853 |
Asset templates |
In the Asset Templates application, when you enter a decimal value and save, the value is displayed with the wrong precision. |
| IJ28859 |
Multi-Tenant |
In the Database Information application, when you add a new attribute to an entity, such as a service request, then try to delete a record of that entity's type, an error occurs. |
| IJ25972 |
System UI |
In the Application Designer application, when you add a lookup field to the list tab of the Service Request application, then create a service request and use the field, an error occurs. |
| IJ28952 |
Work Supervision |
In the Service Request Work Center, when the user's language is not English, some labels are not translated. |
| IJ20606 |
Assignment Manager |
Interrupting an assignment in a time zone different than the current user fails. |
| IJ29282 |
Work Execution |
In the Work Execution Work Center, when you scroll through the list view, header options stop working. |
| IJ29350 |
Linked Documents/Attached Documents |
In the Work Order Tracking application, when you attach an item to a work order and save, the displayed work order number is updated to an incorrect value. |
| IJ29501 |
Report |
The report that provides details on the number of concurrent users that are logged in to the system is incorrect. |
| IJ29853 |
Multi-Tenant |
In a multi-tenanted environment, when you insert a new attribute object in the Database Configuration application, an error occurs. |
| IJ24858 |
OSLC Providers |
In the OSLC Providers application, when you create an OSLC interaction, an error occurs. |
Interim fix 008 for Maximo Integration Framework 7.6.1.2 is also available at Fix Central.
| IJ32157 |
Integration |
When LDAP authentication is enabled, native authentication that uses MAXAUTH header cannot be used for the Webservice calls. |
| IJ29402 |
Launch in Context |
Launch in context URL is not encoded properly for an attribute. |
IBM Control Desk 7.6.1.2 uses Tivoli's process automation engine 7.6.1.1. Apply interim fixes for Maximo Asset Management 7.6.1.1 to IBM Control Desk 7.6.1.1.
IBM Control Desk 7.6.1.3 and 7.6.1.4 use Tivoli's process automation engine 7.6.1.2. This interim fix can be applied to IBM Control Desk 7.6.1.3 and 7.6.1.4.
Related Information
Was this topic helpful?
Document Information
Modified date:
01 April 2022
UID
ibm16477008