Restrict linking work items to ERM artifacts to either module context artifacts or base artifacts

Enforcing data conistency is very important when working with a large amount of users on developing a product. ^ When linking a work item with a ERM artifact, you have two options: (a) linking to the base artifact (b) linking to an artifact in the module context Our currently valid requirements all exists in module contexts and we decided to link all elements in context of a module. If the user works inside ERM, he typically works inside a module and every link he creates, is created in a module context. However in EWM, when starting to create a link to the ERM, the user typically chooses the easiest way, not selecting a module first, but to search directly by the artifact id and selecting the resulting requirement. This leads to a link to the base artifact, not the module context artifact. We already tried to train the users to always choose a module first and then choose the artifact inside the module, so that the link is created to the module context artifact and not the base artifact. This improved the situation, but is still very error prone. This is why it would be a good feature, if we are able to assist the user by the tool to create a correct link. This requires a feature, which either (1) restricts the ERM artifact selection wizard to only select artifacts in module context (or base artifacts, if the data model concept is the other way around) (2) or alerts the user to the fact that he did create a wrong link to a base artifact instead of a module context artifact and prohibits saving the work item Same problem does appear when linking from ETM artifacts to ERM artifacts