Updating existing artifacts after changes to the template
Accepted answer
Hi Naghmeh,
The simple to this is No. Templates are used only to populate relevant Sections of the Asset at the time of creation. Once the Asset is created it no longer has any link to the template. So any change in the template is not going to affect the existing assets and which is the desired behavior else you would have to revisit every other asset created from the template if you modify the template.
One other answer
Actually - this ability would be fantastic. Any time our methodology templates change, we have a big manual process to get those templates into production, then work with all of our users that want to use the new templates on an in-flight project (artifacts existed prior to template change). Never really thought about the ability to dynamically (and optionally) update project artifacts based on new project template changes (although I did request this enhancement for the artifact templates).
Hrm, something to think about!!!
Comments
If you use process sharing, you can upgrade the process e.g instanciate a new project area. Then the sharing projects can be changed to share the updated process. This is, as far as I can tell, the suggested way to achieve what you want. Today, that implies that the sharing project area does not change it's process. New capabilities are introduced in newer versions to allow changes such as additions of custom attributes.