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 Subscribe
Status Under review
Workspace IBM Engineering - Systems Design Rhapsody/RMM
Categories Server
Created by Guest
Created on Jun 18, 2025

RELATED IDEAS

RMM API response includes every rhapsody unit in stream even when the unit is not part of the model

In our current setup, Stream A contains over 100 components, with one default component containing the Rhapsody model(.rpyx). The model in Component A has data(.sbsx/.clsx/..,) added from the other 99 components. When an element(say .clsx) from Component B which is added in the model in Component A is deleted, the element is removed from the model, but its file remains in the file system of Component B. This leads to below issues:

 

"When the deleted element’s File is still present in the component B, the RMM API includes these deleted elements as well in its response since it gives the response from the stream level"

 

To address the issue, we request the following enhancements for the  RMM API:

"Enhance the RMM API to provide responses based on the unit files that are part of the Rhapsody model  NOT from the data present in the file system"

Idea priority Urgent
Needed By Yesterday (Let's go already!)
  • Post comment
  • Guest
    Aug 14, 2025

    Scenario:

    Rhapsody allows storing the model files (sbsx and clsx) across multiple components with one component being the default component (containing the .rpyx file)

    For variant management purpose, we delete few packages and classes from the model on a monthly basis

    When the unit file for these packages and classes are stored in default packages, the unit files are deleted when the elements are deleted.

    Problem: 

    When the unit file for these packages and classes are NOT stored in default packages, the unit files are NOT deleted when the elements are deleted.

    This leads to inconsistency.

    Now, when we query this model using the REST API provided by RMM, we get the deleted elements also included in the response because the unit file for these elements still remained in the component(Even though the element is deleted from the model)

    Use case:

    This is a productive use case where we create variants from the Master model for our monthly release every month. We need to delete few elements from the model which are not relevant or that particular release. This deletion is not reflecting in the response of the REST API provided by RMM due to the issue mentioned above.

    Expectation:

    We would like the REST API provided by RMM to verify if the unit files  (sbsx, clsx) are still part of the model.

    If they are part of the model, they should be included in the response

    If they are not, they should not be listed in the response.

    Reply
  • Admin
    SANTHARAM SUNEEL
    Jul 21, 2025

    Hi,

    We would like to clarify your requirement regarding the list of model files used by the Rhapsody model.

    Are you referring to the list of model element files specifically used by the Rhapsody model, or the complete list of all files within the system directory (as accessed via the Java API provided by Rhapsody or the REST API provided by RMM)?

    To better understand your current setup, could you please confirm:

    • Are you using any custom Java plugin?

    • Are you leveraging the RMM REST API to retrieve this information?

    • Or are you using any standalone functionality provided by the product?

    Additionally, could you help us understand the intended use case of this implementation?

    Is this requirement primarily for a diagnostic or cleanup operation, where a one-time script or sample utility that lists model-related files (e.g., to a console or text file) would suffice, even without full optimization for large models?

    OR

    Are you looking for a full-feature implementation where RMM operations (e.g., check-in, deliver in EWM) explicitly handle only Rhapsody model element files? This would require deeper integration and likely involvement from the RMM development team.

    Your clarification will help us propose the most appropriate solution path.

    Regards,
    Suneel...

    Reply

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.