Enable relationship constraints for Change management object (ECR/ECN/CT)

[flemoine]

Could it be possible to enable relationship constraints between change requests/change notices and change notices/change tasks.

Lot of customers have different change management object types and they all request to avoid users to select wrong change notice types for specific change requests.

[BjoernRueegg]

Is this not already implemented since 11.0? You can see the constraints under site-> utilities -> "Business Rules"

[flemoine]

You are right, I did not look at business rules. I only checked on Type and Attribute manager to create relationship constraint.

[JeffZemsky]

This functionality has been supported since 11.0 F000 (PR, Deviation/Waiver, CR, CN) and 11.0 M010 (Change Tasks) using the flexible Change associations.  Admins can configure which Change object types can be related to each other, which are required and cardinality.

Some examples

1) Link a PR directly to a CN

2)Create a "Block CR" that has 1 to many child CRs

3) A Production CR can only be related to a Production CN.  Production CN must have a CR related to it.

4) A Prototype CN can only have a Prototype Change Task related to it and only 1 Change Task is allowed

Information can be found here

https://support.ptc.com/help/windchill/wc110_hc/whc_en/#page/Windchill_Help_Center%2FChgMgmtFlexibleLinksAbout.html%23