This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We upgraded from MX 76 to MAS9 with customs Java classes. Everything is working fine but after each upgrade, no matter if automated or manual, classname attributes are overwritten by standard classes. For example a custom class for Workorder object.
After the upgrade, all classnames has to entered manually again. I tis hard to accept such solution in platfrom so robust, as it potentially results in a significant amount of manual work.
First and foremost, the core issue is not whether the upgrade is performed manually or automatically — that is irrelevant.
The real problem lies in how Maximo handles custom Java classes during or after the upgrade process.
By design, Maximo allows the use of custom Java classes and enables references to them within the appropriate objects. Therefore, we expect that — also by design — the upgrade process (regardless of whether it's automated or manual) should not require us to manually reconfigure each and every reference to these custom classes. Please consider that there could be dozens of them.
Plase, consider any improvement in this area.
Thanks.
Idea priority | Urgent |
Needed By | Yesterday (Let's go already!) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Hi Kim,
Thanks for your response — we’ll double-check on that. However, if this capability already exists, why does the answer in support case TS018792226 say otherwise? Your colleague responded as follows:
"Currently, Maximo doesn't have the capability to support this functionality, as it's not part of the existing design."
That’s why I originally logged this idea.
Best regards,
Milan
Thanks for your submission. The capability exists, please make sure you have supplied an a_customer.xml definition file that the system uses to build proper inheritance and set the meta data appropriately. Some reference materials: https://www.ibm.com/support/pages/how-prevent-lost-customizations-when-add-products-are-installed
https://www.ibm.com/docs/en/control-desk/7.6.1.x?topic=updates-product-descriptionxml-file
https://www.ibm.com/docs/en/masv-and-l/maximo-manage/continuous-delivery?topic=customizing-customization-archive-guidelines#concept_xvm_xd2_nsb__title__1