I expect windchill can check and can't submit if Affected Objects and resulting objects is the same object in change notice.
easy to customize in the Workflow, wizard step validator, or may be in the new validation rules in 10.1...
But you're right ... it should be out of the box
I don't agree that this should be OOTB. If anything it should be preference controlled. We have use cases where we need to do this.
Agree Joe , with a preference.
What about your use case ? To set effectivities on an already Releaesd part, but in a new Product context ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.