Vitor,

the second question: if you update a template these changes will only apply to project areas created from the new template version. If you want to only maintain a few central process configurations, process sharing is the way to go. See https://jazz.net/library/article/1005 , https://jazz.net/library/article/1008 , https://jazz.net/library/article/621 .

I don't think there is any guidance on version controlling the templates. RTC SCM would work, but treat it as a binary file.

All sharing projects are automatically updated.

But you can create a new project area from your template. Then you update the new project area. Then it can share. Then you can notify the projects to change to the new project area at convenience. This allows a more controlled process.

Base on our experience you cannot today do any recording or versioning of process templates.

there is an enhancement request for this in the database someplace. (make the process template a 1st class object).

also all consumers get the new template, there is no branching support..

now.. one warning.. if you do NOT set the process templates sections as final (checkbox for each section), then children processes ARE allowed to change that section..
IF they change that section AT ALL, then it is COPIED from the master and the child will use the copy from then on FOREVER for THAT SECTION. (sections are like Enums, presentations, workflows, ...)

currently you CAN see the changes made to the process configuration by looking at its history
(view the source, right mouse button click, select Show History).
but you cannot save this delta and re-apply it, nor back out to a previous level.