Re: Ability to prevent objects from existing in several ECN:s at the same time?
First and foremost the red triangle "Pending Changes Exist" glyph should be the first line of defense. This may require some education of the User base.
I'm looking at a detect and inform to avoid type of solution rather than hard coded logic that prevents. Conceptual solution is to add the detecto code in the Change Request upstream of "Analyze Change Request" and message accordingly.
Ideally this would be an Out of the Box Business Rule that could be evaluated at Change Notice or Change Task submission and route/notify as needed.