When working with Change Notices (CN) in PDMLink, does anyone else have to fill out these three fields (which are really identical) in order for useful information to be displayed on all the right places (CN, Task, email notifications, etc?).
We have a little automation in place because the CN description will do a one time propagation to the Task auto-propagate, but after that the connection is broken so if one changes the other will not update. This reputation is a nuisance, conducive to error, and takes up space!
Any way to get these to synchronize all the time and then only have to enter it once, or update it once?
We are using Windchill 10.1 M050, and only use 1 task per 1 ECN. Perhaps this is better in EC11?
I wouldn't recommend automating that at all. The Change Notice is only the "collection hub" for the individual work packages (Change Tasks) that people of various departments have to do in order to make a change, the CN itself doesn't actually do any work on its own. CNs can have multiple CTs connected to them and each could be a completely unique assignment. For example, task 1 could be the standard CAD and Part design work of your designers, task 2 could be your Supply Chain getting quotes/feedback from the suppliers, task 3 could be for your Service group to update their service instructions, task 4 could be your Legal department...you need the ability to give custom Descriptions and Names to each task relevant to the work that the Assignee of each task is supposed to do, which could be wildly different from each other and trying to put all of the instructions for all of these roles into the main Description of the parent CN could make it far too verbose, and hard for each individual role to pick out which part they need to pay attention to.
What you're proposing would only really be valid if every single CN your company makes and ever will make will only ever have one Change Task on it. That seems...extremely limited. But is that indeed the case for you?
What you describe sound like a it could be nice once/if it was set up right.
Thanks for the explanation and examples of multiple CTs on a single CN.
It is hard to say what will happen in the future but, yes, right now we only have one CT per CN. So that means what you describe as super powerful, is a pain point to us who are not using that power...
Did you ever get this figured out. This would be nice to do when you only use one CT per CN. I know that you can pass custom parameters back and forth between the two, but these are OOTB parameters that need to be passed.