Skip to main content
B
BF_1381190014-Alexandrite
14-Alexandrite
January 12, 2026
Question

Supersede Change Notice & Change Tasks

  • January 12, 2026
  • 1 reply
  • 126 views

Version: Windchill 13.0

 

Use Case: I have a requirement to supersede change notices and the change tasks associated to them. Objects that can be included on issued change notices as affected/resulting objects can often no longer be subject to the changes that the change notice is being used to represent. This is because newer change notices can be issued that includes the same parts as affected/resulting objects and the changes detailed on the older change notice would then no longer be required. In instances such as this, it would be good to be able to update an attribute against the change notice and it's associated change tasks to allow users to easily identify that they have been superseded by a new set of change tasks associated to a newer change notice. Please note that there will be occasions when some of the change tasks on a change notice that eventually becomes superseded may have already been completed.


Description:

Can anybody suggest an effective solution that meets this requirement?

1 reply

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
January 12, 2026

"We apologise for the fault in the subtitles previous change notice. Those responsible have been sacked. Those responsible for sacking the people who have just been sacked have been sacked."

Be clear about where you would like this indicator, on the change objects or the resulting objects? My assumption you would have resulting objects (revisions) that exist with incorporated changes already. Essentially, you are creating a new change notice which would result in a new revision? If that is the case, one change undoes the previous one. A lot depends on when the decision to invalidate a change is done. If its after its been incorporated and released, well, that is the normal change process. If its before the completion of a change where you want to reverse course, I would think you can either cancel the change or rework it to change the write up and conform to new changes. In either case, the Lifecycle state would be an indicator of that. 

 

I would focus on the business process however to avoid this happening at all. It seems there is a point in time in the process where things are "locked in" but not yet fully incorporated. This might be easier than adding additional things to the process. 

    Terms & ConditionsCookie settingsAccessibility statement