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 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 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
For drop downs: Dependent values should be automatically removed when person unticks the related drop-down value form another field
This would benefit all the users who are using multiselect drop-down lists, which include additional dependent fields. This would significantly improve the data quality.
This is especially needed for the financial fields, however useful for other situations as well where different impact dimensions are assessed.
For example: Person chooses that the loss event has potential loss and in the dependent potential financial loss field, person writes 100 000 EUR. Later 50 000 EUR materializes. User goes to the system, unticks potential loss (dependent potential financial loss field disappears) and ticks actual loss. Dependent actual loss field comes up and user writes 50 000 EUR.
When taking the extract and analyzing the data, system has both 100k potential loss and 50k EUR actual loss values in there.
This means that instead of the 50k EUR, we need to include 150k EUR in our capital calculations.
How it should be:
When person unticks potential loss from the loss event types, the system automatically removes the 100k value. When taking extract, potential loss is 0 EUR, actual loss is 50k EUR.
Do not place IBM confidential, company confidential, or personal information into any field.