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.
Sort order in association grid selector should reflect the visible columns
We noticed when we configure the "Associate" button on an object grid in a task view, the default sort order of the grid results are on System Fields.Name, even if that field is not visible in the grid.
IBM support confirmed that this is working as expected (always sorting the results by default on System Fields.Name, even though the field is not visible in the grid).
Would be great and more intuitive for users if it would default sort on the first visible column in the grid instead.
An example use case would be Employee objects that are autonamed. The autoname has no meaning for the end user. Only the First Name and Last Name fields. But when they summon the Employee picker to select employees, even if Last Name is the first grid column, they appear to not be in alpha order at all because they are being sorted by default on the autoname that is not even visible.
Current workaround is simply a training issue that users have to click on the first column heading in the picker to dynamically sort the available object alphabetically on the Last Name field.
Do not place IBM confidential, company confidential, or personal information into any field.