Ability to prevent objects from existing in several ECN:s at the same time?

[afabre]

In PDMLink you are not able to prevent objects (wt-parts, PDMLink-documets, CAD objects) to exist in several running ECN:s.

According to PTC it is "Not part of Windchill functionality" (see Document - CS151467).

This behavior causes three main problems for us:

-The last finished ECN “overwrites” the information in the other ECN:s that finished ahead of it (we are carrying a lot of other vital information apart from the objects themselves in our ECN:s).

- Objects in an ECN can suddenly be released due to another ECN being resolved that objects also reside in.

-Information in the ECN is incorrect due to objects in it being changed by another ECN that the ECN owner is unaware of.

This causes a lot of ECN:s needed to be reissued.

The result is a large amount of time and money being wasted.

We would therefore like to prevent objects from being able to exist in more than one running ECN at a time.

Has someone in this community been able to prevent this?

Is someone else in thiscommunity suffering from a problem similar to ours?

[kpritchard]

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.