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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Currently patching documentation provides just enough information on how to perform the tasks, but nothing on what the tasks do.
Very clear example is the recent MRG patch. The recent changes include a relationship change, decommisioning of objects, field changes, new OOTB workflows, and field-group changes.
Which of these happen on an upgrade? Does the workflow require the new Usage/Model relationship change? If so, is that a manual step after? What fields are being modifed and how?
There is no available documentation to answer any of these questions and support has also confirmed that they do not have the information to share. This information should be included in the documentation for upgrades by default.
Do not place IBM confidential, company confidential, or personal information into any field.