cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Add a preference for one change task per change notice

Add a preference for one change task per change notice

Create a preference that only allows for one change task to be created per change notice.

 

In my company we do not allow for multiple tasks to be created per a single change notice.  The problem is that there is no way to control it.  When a user does not follow this, it creates a lot of problem.

  1. Reports for manufacturing do not work correctly.
  2. Need to reseed the table to a later change number for both activity and notice.
  3. Stop all affected change notices/tasks and recreate them.

 

I know that not all companies follow this, but I would think that there would be alot of them that only use one task per notice and that is why it should be a preference.

4 Comments
Newbie

We have this need but would need the preference to allow it to be set for a specific sub-type of a CN.  We have one sub-type for a Fast Track Change Notice that we want to limit to one Change Task. We also have a Full Track Change Notice sub type that we allow multiple.  We also need to constraint the Type of the Change Task based on the Change Notice sub-type.

Peridot

The functionality to set constraints between Change Notices and Change Tasks is in development for the next release of Windchill.  This will enable you to constrain which type of Change Task types can be created for Change Notice types as well as Cardinality.  For example you could say that a Simple Change Notice can only have 1 Change Task of type Simple Change Task.

Peridot

This is supported with Windchill 11.0 M010 with the addition of Change Implementation Plan rules to define Change Associations.  With this one can define which CT types can be related to which CN types and their cardinality (eg. 1:1 or 1:Many)  Below is an example of setting up a rule where only 1 CT can exist per CN.  Note - make sure the CN type does not inherit any CT relationships from higher levels to support this case when you build your rules.

Further - one can define this as the default Change Notice Template for this Change Notice type to further simplify and streamline the CN creation process. This is also new for Windchill 11.0 M010

CTCNrule.png

def_cn_template.png

Community Manager
Status changed to: Archived