Fix Readme
Abstract
On 2 November 2023, IBM released IBM® Maximo® Application Suite Manage Component patch 8.6.6.
Content
APAR and Known Issue Fixes
When an APAR or Known Issue has Manual Change in the first column, click the link or go to the Manual Changes section for directions.
When an APAR or Known Issue has Behavior Change in the first column, click the link or go to the Behavioral Changes section for information.
When an APAR or Known Issue has Behavior Change in the first column, click the link or go to the Behavioral Changes section for information.
| APAR | Application Name | Description |
| DT173969 | Technician | Get Reserved Items not working for Rotating Items. |
| DT179014 | System UI | Button Alignment setting is ignored. |
| DT189344 | Technician | The Pause and Stop buttons are displayed instead of the Start button upon returning online. |
| DT196324 | System UI | A user cannot change the width parameter in the XML definition. |
| DT225598 Manual Change |
Login | Update E-Key error message is not correct. Note: This fix requires MAS 8.10.5 be installed. |
| DT236752 | Companies | In the Companies application, moving to a Branch changes the Organization. |
| DT237302 | Mobile | Resetting the application and pointing to another environment intermittently causes a blank screen to appear. |
| DT238165 | Technician | When reporting item consumption in a work order in Maximo Technician, the lookup displays items that exist in multiple organizations. |
| DT238267 | Mobile | Mobile record creation fails due to header size too large from app select. |
| DT238493 | Database configuration | A user is unable to access Database Configuration when Maxadmin security group is NOT independent of other groups. |
| DT239443 | Mobile | In Mobile SR, creating records does not release all datasource resources, leading to orphaned datasources. |
| DT240691 | System Object | In environments where the Base language is English and the Secondary Language is Simplified Chinese, the Workflow Map node description is garbled. |
| DT240992 | Install/Upgrade | In a Red Hat OpenShift Container Platform 4.12.x environment with MAS version 8.10.3, the Grafana Dashboard reports stop working. |
| DT241227 | System Object | MAS Core statuses of TIMED_OUT and DELETE_TIMED_OUT prevent user's information from being accurately loaded or synchronized in the Application system. |
| DT241482 | Mobile | Resetting App data does not log out the user. |
| DT243253 | Mobile | Answering questions on an Inspection Form causes transactions to build up in the queue. When more transactions exist, the records are sent more slowly to the server. |
| DT243419 | Mobile | Transitioning from offline to online, a user sees a spinning wheel in the Assigned Work work list page and no work order displays. |
| DT243419 | Security Groups | Users created with LDAPSync are not mapped to Security Groups. |
| DT243657 | Mobile | Maximo Mobile Application in Data Update view crashes attaching photos or trying to refresh. |
| IJ18522 | Inspection | Using MAXDEMO data, the Form Status cannot be changed from Inactive to Active. |
| IJ38170 | Inventory usage | If an Item becomes Rotating in an open Inventory Transfer, the Rotating Asset cannot be associated with an Inventory Usage record. |
| IJ42356 | Work Order Tracking | Work Orders cannot be saved when WOACTIVITY.WONUM is hidden. |
| IJ42466 | Item Master | When an Item is added to a Storeroom, the "Rotating" field becomes read only. |
| IJ44238 | System UI | Radio Button group alignment is lost when the window is resized. |
| IJ45154 | Integration | Loading a flat file with no data results in error BMXAA6992E. |
| IJ45847 | Graphical Scheduling | In the Graphical View of the Graphical Scheduling application, the white bars corresponding to the Maintenance Schedule of the Asset are not visible. |
| IJ46377 | Classifications | Classification attributes with the DATE data type marked as mandatory are not copied from the Ticket Template to the SR record. As a result, saving the SR record displays the wrong error message "BMXAA0191E - Field Table Value for attribute DATE is required. Please enter a value.". |
| IJ46662 | Database configuration | Database connection leak in Bulletin Board UI control. |
| IJ46745 | Integration | In the Maximo Integration Framework (MIF), the SET processing rule causes an error for the DATETIME attribute. |
| IJ47115 | Integration | In cases where two people have the same display name, the ReportedByID populates incorrectly in the Service Request application. |
| IJ47385 | Work Order Tracking | Work Order MULTIASSETLOCCI target description overwritten by Inspection Form name. |
| IJ47621 | Linked Documents/Attached Documents | Maximo replaces the "&" with "%C2%B6" in any URL that is includes "¶m". |
| IJ47624 | Purchase orders | When a PO is created from RFQ / PR, the sequence numbers for the terms in the Terms and Conditions" tab of the PO are incorrect. |
| IJ47651 | Purchase orders | When "Copy PR Line Items to PO" is used, changing the status to APPR results in error BMXAA3279E. |
| IJ47689 | Integration | MaxSoftwareProcess and MaxSwRelProcess classes are missing from all 7.6.1.X releases. |
| IJ47737 | Inspection | Inspection Form Preview does not show Meter Reading answers. |
| IJ47852 | Graphical Assignment | In Graphical Assignment, no routes are being displayed when multiple queries are defined. |
| IJ47863 | Application Designer | When an Application is set to "Is Mobile" in Application Designer, the Conditional Properties do not work. |
| IJ47885 | Linked Documents/Attached Documents | Filtering the DOCLINKS in the View Attachments dialog box results in error BMXAA4129E. |
| IJ47934 | Automation Scripts | An Automation Script does not fire with ASSETSPEC.NUMVALUE changes. |
| IJ48020 | Graphical Scheduling | The Where Conditional can be edited through the Quick Query Builder by a different user than the one who created the schedule. |
| IJ48611 Manual Change |
System UI | Cloudflare timeout can cause table download to fail. |
Manual Changes
| APAR | Change instructions |
|---|---|
|
1. Go to Database Configuration.
2. Click the Messages action menu to bring up the Messages dialog. 3. Click the New Row button to insert the following messages. Click OK after messages are entered. These field values are common to all changes listed here.
Message Group: signature Display Method: MSGBOX Message ID Prefix: BMXAA
Message ID Suffix: E
Buttons: OK
1) Message Key: PW2minLower
Value: Password is not valid because it does not meet the password rule: Minimum number of lowercase characters: \{0} Explanation: Use the minimum number of lowercase characters required to set your password. 2) Message Key: PW2allowLastNumericFalse
Value: Password is not valid because it does not meet the password rule: Last character cannot be a number. Explanation: Use an alphabet, for example, "a" as the last letter of your password. 3) Message Key: PW2minUpper Value: Password is not valid because it does not meet the password rule: Minimum number of uppercase characters: \{0} Explanation: Use the minimum number of uppercase characters required to set your password. 4) Message Key: PW2minSpecial Value: Password is not valid because it does not meet the password rule: Minimum number of special characters: \{0} Explanation: Use the minimum number of special characters, for example, "@", to set your password. 5) Message Key: PW2minNumeric Value: Password is not valid because it does not meet the password rule: Minimum number of numeric characters: \{0} Explanation: Use the minimum number of numeric characters required to set your password. 6) Message Key: PW2allowedCharacters Value: Password is not valid because it does not meet the password rule: Allowed characters: \{0} Explanation: Use the allowed number of characters for your password. 7) Message Key: PW2allowUserNameFalse Value: Password is not valid because it does not meet the password rule: Password cannot contain a user ID. Explanation: Please make sure that your user ID is not the same as your password or part of your password. 8) Message Key: PW2allowLastSpecialFalse Value: Password is not valid because it does not meet the password rule: Last character cannot be a special character. Explanation: Use an alphabet, for example, "a" as the last letter of your password. 9) Message Key: PW2allowFirstSpecialFalse Value: Password is not valid because it does not meet the password rule: First character cannot be a special character. Explanation: Use an alphabet, for example, "a" as the first letter of your password. 10) Message Key: PW2allowFirstNumericFalse Value: Password is not valid because it does not meet the password rule: First character cannot be a number. Explanation: Use an alphabet, for example, "a" as the first letter of your password. 11) Message Key: PW2minLength Value: Password is not valid because it does not meet the password rule: Minimum password length: \{0} Explanation: Use the minimum number of characters required to set your password. 12) Message Key: PW2maxLength Value: Password is not valid because it does not meet the password rule: Maximum password length: \{0} Explanation: Use the allowed length of characters for your password. |
|
|
Verify the web.xml at applications/maximo/maximouiweb/webmodule/WEB-INF/web.xml includes this new servlet information. If it does not, add it.
<servlet> <servlet-name>TableDownloadServlet</servlet-name> <servlet-class>psdi.webclient.servlet.TableDownloadServlet</servlet-class> <init-param> <!-- The character encoding the servlet will use for all http requests and request responses. --> <param-name>char_encoding</param-name> <param-value>UTF-8</param-value> </init-param> </servlet> <servlet-mapping> <servlet-name>TableDownloadServlet</servlet-name> <url-pattern>/tabledownload/*</url-pattern> </servlet-mapping> ------------ New Cron Task: TableDownloadCleanupA new crontaskcalled TableDownloadCleanup was added. It is disabled by default. When files are downloaded in xlsx or csv format, a temporary file is generated on the file server, and then deleted after the file is downloaded. We added this crontask to clean up the tabledownload folder on the server where these temporary files are saved. If you notice files in the tabledownload folder on your webserver, you could enable this crontask to help with an automatic cleanup. Otherwise, you leave it off, as we do not expect system failures to occur caused by the presence of these temporary files. |
Manually Installing the Patch
- Log in to Maximo Application Suite Administration as an administrative user.
- On the left, click Applications.
- From the Action menu, select Update configuration.
- In the dialog box, click the pencil icon on the Components line.
- Under Activation configuration, click your workspace details page link.
- From the Action menu, select Update configuration.
- Under Configurations, click the pencil icon on the Components line.
- In the Maximo Base line, under new version click the down arrow.
- Select Version. Enter 8.6.6
- Click Save.
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hB0QAAU","label":"Manage"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0"}]
Was this topic helpful?
Document Information
Modified date:
26 December 2023
UID
ibm17063685