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.
Hi,
Historically, Rhapsody indeed stores some basic information about referenced elements from other Rhapsody models.
But storing the information from different domains (RM, QM, CCM) can be more problematic.
We have consulted with some design partners from A&D who are sensitive to access control permissions about preserving this specific information (names of remote artifacts).
Sorry, we can't take this request forward.
Regards,
Suneel...
Hi Suneel,
Please let me know if you need any other information here.
Regards,
Mounika
Hi,
RMM intentionally didn't implement caching of internal requires information because in offline mode Rhapsody cannot validate access permissions to the associated project/module. To avoid a possible leak secured information we preferred to not store any requirement information (except URI) locally.
Regards,
Suneel...