Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
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 URL
RFE Product Rational Software Architect
  • Admin
    Osman Burucu
    Reply
    |
    Jul 10, 2023

    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The offering team has carefully reviewed this idea and has decided that it does not fit into our current plans, or the idea has aged or has been implemented, so the idea will be closed. The idea will be kept in IBM's ideas repository and may still be voted on. It might be reassessed or reopened for additional feedback in the future. We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

  • Guest
    Reply
    |
    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
    Reply
    |
    Jan 28, 2009

    This enhancement request is under consideration for a future release.

  • Guest
    Reply
    |
    Jan 23, 2009

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