IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.

ADD A NEW IDEA

IBM Engineering - Systems Design Rhapsody/RMM

Showing 508 of 5886

Add tags in a hierarchical manner in Rhapsody 9.0

Hello Team, I need to add tree structure (child elements till nth level) for Tags. Please help us to resolve this requirement. Please refer the video in this IBM ticket to get requirement: TS006406370 Thanks,Dasari
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Other 1 Future consideration

Keep "int" variable in Rhapsody Developer C using Reverse Engineering.

Our developer team notices that the type "int" changes when they do Reverse Engineering in Rhapsody Developer C. They would like to keep the original type "int" in order to facilitate their work.
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Code and Execution 1 Future consideration

Keep an original character in Rhapsody Developer C using Reverse Engineering.

Our developer team notices that, when they do Reverse Engineering in Rhapsody Developer C, one character changes. They would like to keep the original code in order to facilitate their work.
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Code and Execution 1 Future consideration

Keep the original Void in Rhapsody Developer C using Reverse Engineering.

Our developer team notices that the type Void changes when they do Reverse Engineering in Rhapsody Developer C. They would like to keep the original type Void in order to facilitate their work.
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Code and Execution 1 Future consideration

Keep the original Struct in Rhapsody Developer C using Reverse Engineering.

Our developer team notices that the type Struct changes when they do Reverse Engineering in Rhapsody Developer C. They would like to keep the original type Struct in order to facilitate their work.
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Code and Execution 1 Future consideration

Keep the original Union in Rhapsody Developer C using Reverse Engineering.

Our developer team notices that the type Union changes when they do Reverse Engineering in Rhapsody Developer C. They would like to keep the original type Union in order to facilitate their work.
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Code and Execution 1 Future consideration

Keep the original enum in Rhapsody Developer C using Reverse Engineering.

Our developer team notices that the type enum changes when they do Reverse Engineering in Rhapsody Developer C. They would like to keep the original type enum in order to facilitate their work.
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Code and Execution 1 Future consideration

Enable suspect links for artifact children changes

At the moment OSLC (agreed) links between DNG artifacts and RMM artifacts do not become suspect when a child object of an RMM artifact is changed. An example is a link from a DNG artifact to a "logical exchange" in RMM. When an attribute of a flow...
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Modeling and UI 1 Future consideration

Horizontal Swimlanes in Rhapsody Activity Diagrams

Our engineers have asked for an option to create horizontal swimlanes. There was a request created in 2011 for this, 11335, which was declined. My team wanted to create our own request to indicate our interest in this capability.
over 3 years ago in IBM Engineering - Systems Design Rhapsody/RMM / Modeling and UI 1 Future consideration

Rhapsody should not introduce metadata differences when working with multiple editions as this introduces unexpected changes.

When a pool of users work on the same model but use different editions (Developer vs Designer, for example), there is a difference in how types are attributed in the repository. For example, Designer will claim that anything of type Int is from th...
over 1 year ago in IBM Engineering - Systems Design Rhapsody/RMM / Rhapsody Client 1 Future consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.