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
Start by posting 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 offering manager 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 a 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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
For the GUI in web, we implement an extension to customize the UI a little bit. For example some ClearQuest-Ids become linkable directly or some pop-up-windows interact to special value-changes.
For example to get all Multiline-fields, we are using the following JS-function:
var multilines = rq1Core.getDojo().query(".dijitTextBox");
The problem is, that the result will not return only the Multiline-fields, it also returns String-fields, choicelists etc.. So we have to analyze all returned fields with much effort (analyzing special attributes etc.).
The same problem occurs for pop-up-message-boxes. The function rq1Core.getDojo().query("#cq_widget_CqMessageDialog_0_desc"); returns only the message-box with the number zero in the attribute-value. But by getting the message-box again this number is different.
Now we need an attribute at each GUI-element which identifies the element unique. Possible GUI-elements are: - choicelist - multi-choicelists - text-field (for Short-string) - text-field (for multiline-string) - reference-list - reference - checkbox - radio-buttons - lable - buttons - tabs - groups/frames - ...
As more and more fields are added to the GUI of a record, the parsing and analyzing stuff needs more time and more effort, than searching for a unique attribute.
Because of that it is necessary to make the analyzing functions much faster.
So the identification of the field-types is necessary for making text linkable, add some icons, interact to changes of special field-types, etc.
Do not place IBM confidential, company confidential, or personal information into any field.