Change Management: Change Implementation Plan Association Rules
Product: Windchill PDMLink
Release: 11.0 M010
Benefit
Use change association rules to configure implementation plan requirements by configuring relationships between change tasks and change notices.
Additional Details
Change association rules were released with Windchill 11.0 F000. These rules enable you to easily configure rules to dictate allowed or required relationships between change objects.
Previously, you could use change association rules to define requirements for the Associated Process Objects and Associated Reference Objects tables. Now, you can also define requirements for the Define Implementation Plan step. This step defines the relationship between a change notice and its change tasks when creating or editing change notices and change notice templates:
Enabling this feature results in the following changes:
Change Association Rule Type Selection
Previously, you could select between the Change Process and Change Reference association types. Now, a Change Implementation Plan association type is also available:
When you select the Change Implementation Plan association type, the following options appear:
Role A Type | Change Notice and its subtypes |
Role B Type | Change Task and its subtypes |
Cardinality | • 1:many (default) • 1:1 |
Owning Role | Role A |
Required Role | • None • Role B (default) |
Out-of-the-Box Change Association Rule
A default implementation plan rule is provided with the following values:
Context | Site |
Association Type | Change Implementation Plan |
Role A Type | Change Notice |
Role B Type | Change Task |
Cardinality | 1:many |
Owning Role | Role A |
Required Role | Role B |
| To facilitate the new Change Implementation Plan association type, additional enhancements have been made allowing you to configure default change notice templates. These changes are also implemented when the opt-in features are enabled. For more information, see Change Management: Default Change Notice Templates. |
Related Information
