Shared project process: what parts get shared with child

We're tryng to understand what parts of a 'master' projects process definition get shared with child projects. Specifically, if I make changes in the master, what gets flowed to the child projects process.
Also are there any situations where perhaps a change in a child would stop the further flow of changes to that child.
We're struggling to find anything definitive on how this all works. All I could find at the end of a short article on chaging to a shared process was
The project area now uses the roles, permissions, operation preconditions and follow-up actions, and configuration data from the sharing project area. Within your project area, you can customize process settings unless the project administrator of the sharing project area has set those settings as Final (ignore customization of this operation in child areas).
Although editor presentations are part of configuration data, it doesn;t seem to flow through.
Pointers anyone ??

Hi Alan,

The following link has information about process sharing: https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.jazz.platform.doc%2Ftopics%2Fc_sharing_project_area_process.html&re=1&scope=null

Have You used the Unconfigured Process template to create the project area that consume process (as the note on the top of the above page recommends)? As the note says, using a template that defines its own process causes the project area that consumes process to override the process it is consuming, which is not usually the desired behavior.

Regards,
-Vlad

We're tryng to understand what parts of a 'master' projects process definition get shared with child projects. Specifically, if I make changes in the master, what gets flowed to the child projects process.
Also are there any situations where perhaps a change in a child would stop the further flow of changes to that child.
We're struggling to find anything definitive on how this all works. All I could find at the end of a short article on chaging to a shared process was
The project area now uses the roles, permissions, operation preconditions and follow-up actions, and configuration data from the sharing project area. Within your project area, you can customize process settings unless the project administrator of the sharing project area has set those settings as Final (ignore customization of this operation in child areas).
Although editor presentations are part of configuration data, it doesn;t seem to flow through.
Pointers anyone ??

Hi Alan,

The following link has information about process sharing: https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.jazz.platform.doc%2Ftopics%2Fc_sharing_project_area_process.html&re=1&scope=null

Have You used the Unconfigured Process template to create the project area that consume process (as the note on the top of the above page recommends)? As the note says, using a template that defines its own process causes the project area that consumes process to override the process it is consuming, which is not usually the desired behavior.

Regards,
-Vlad

Thanks for the link Vlad, that was exactly what I was looking for. In this particular case, we didn't create the child project from an unconfigured template as the projects already existed, but were originally created from the same template and the process hadn't been customised in either project. We just wanted to share the changes we were about to start making (we compared the XML to be sure). We were following the instructions on linking projects, but the first thing we tried was customising the editor presentation and that didn't get flowed across. This is what prompted the question. Looks like we may have to have a rethink