Skip to Main Content
Cloud Platform

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 for resolution.

For more information about IBM's Ideas program visit

Status Planned for future release
Created by Guest
Created on Jan 20, 2009

Addition of a Decision point that has multiple inputs and outputs

In Rational Rose we have models that use a decision point as a combination of a decision node and merge node. We converted our old models over and would like to keep this functionality, whether or not it strictly adheres to the UML 2.1 spec.

Right now our workaround has been to add a blank small merge point before the decision point so that we can have 2 inputs and 2 outputs on one "decision".

Something similar to the model validation constraints in the preferences would be nice, so that those who choose to not follow the exact specification of UML 2.1 can still use the tool without adding a bunch of needless nodes to diagrams.

Being able to customize what rules are used to draw the diagrams would be nice.

Idea priority High
RFE ID 1872
RFE Product Rational Software Architect
  • Guest
    Sep 24, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Application Platform
    Product - Software Architect

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Software Architect

  • Guest
    Jan 28, 2009

    This enhancement request is under consideration for a future release.

  • Guest
    Jan 23, 2009

    Thank you, this request is under consideration and will be review by our software development team.