Effectivity Updates on Change Notification Revision

[dpoisson]

The Current Windchil 10.1 M040 system doesn't correctly update effectivity changes that are made on new revisions of a Change Notification object.

This is a requst to enhance the Windchill change management functionality to properly reflect effectivity changes that are made on revisions of a change notification.

Here are the steps to reproduce:

1. Create a CN
2. Add Rev 1 of Part As affected object
3. Rev the part to add it to resulting objects table
4. Set effectivity with Effectivity Context (Context of itself) , Date Effectivity, Qualifier = Exact, Effectivity Range= 9/15/2013 -
5. Release CN, Notice the Effectivity
6. Revise the CN, For Impact select Revise
7. Change the effectivity on resulting part (rev2) With Effectivity Context (Context of itself) , Date Effectivity, Qualifier = Exact, Effectivity Range= 09/25/2013
8. Release CN, Notice the Effectivity has NOT been updated. Effectivity should be updated to the new Range, 9/25/2013
   

[JeffZemsky]

This has worked for some time.  It appears that there was some misconfiguration and user issu above. In the example above it looks like the user type 9/15/2013 for version 2 as it closed the range on 9/15/2013.  Note that Sibling Propagation = Yes must be set to automatically close the previous revision range. Example posted below:

Effectivity for Rev A set to 9/1/2014-

And now with second CN, revise and set Effectivity to 9/25/2014-

[dpoisson]

Jeff,

The enhancement request that Raytheon is asking for is that the same functionality that takes a second CN be allowed with the new revision of the first CN.  Please refer to step 6 in my process to reproduce.  Our users do not want to have to create a new CN.  They want to be able to revise the first one and have the effectivity updated to reflect the changes on the new revision of the CN.

Danny