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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
While I understand the considerations why Rhapsody behavior is as described, in the concrete use-case the reference is (logically) owned by the model in which the deletion happens.
The model is split up into multiple RMM (EWM SCM) components to be able to only share smaller parts of complex models to other models (which then include those in read-only manner).
Therefore - in this special case - it would make total sense if Rhapsody would delete also the referenced units. As this difference will be hard to be detected automatically, it would probably make sense to introduce an flag/option for r/w reference on how to handle deletion (and also moving of units).
Hi,
We’ve reviewed the reported behavior and can confirm that Rhapsody is functioning as expected in this scenario.
As a best practice, we recommend that model elements be deleted only from their owning model. When elements are deleted through the model editor, the associated unit files are automatically removed, helping to maintain model consistency and integrity.
If you're not observing this behavior in your environment, we suggest raising a support ticket and including the product version details. There was a similar issue reported previously, which has been addressed in the latest release.
Please don’t hesitate to reach out if you have any further questions or require assistance with the recommended procedures.
Regards,
Suneel...