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.
We understand the business justification to this enhancement request but must understand the functional enhancement and use case better.
When the supplier makes comments on the requirements, which RM too is the supplier using?
Does the supplier make a change to the type system or does it remain the same?
Business Justification: The customer spends a fortune on maintaining a consistent type system and consider it not acceptable to get their type system contaminated by a random ReqIF import. Currently it is impossible to prevent that from happening.
When data is reimported it will need to be received back from the supplier with the same data types or the import would be difficult. It sounds like the data is received back from the supplier has a different ID to the type exported. Can you confirm this is the case?
If you receive data back from a supplier with a different type to that exported, what are you suggesting we do to resolve the situation? Selecting an attribute for import will need to create a new type if DOORS Next feels that the type does not exist.
Also see TS003974857 where this happens in the context of the user.