sync rule template ?
I would like to use one sync rule definition for all RTC projects. Ideally would be that if I create a project from a template I get a connection to an external repository and the respective sync rules already defined.
My understanding is that today I have to configure a sync rule fror one project, export it, rename it add the new name into the xml-file and than import the renamed sync rule into a new project. This for each and every project.
Is there any way to automate this process completely ? Can I somehow setup a sync rule that is than used by all projects ?
My understanding is that today I have to configure a sync rule fror one project, export it, rename it add the new name into the xml-file and than import the renamed sync rule into a new project. This for each and every project.
Is there any way to automate this process completely ? Can I somehow setup a sync rule that is than used by all projects ?
2 answers
A sync rule template sounds like an interesting idea.
You are correct that if you wanted to clone an existing sync rule into a different project area, you would have to export/import it with a new name since we require that sync rule names are unique across project areas. You would also have to modify the cloned sync rules if they reference other sync rules. You can enter an enhancement request to clone a set of sync rules from one project area to another.
Since sync rules are scoped to a project area, there isn't a way to define a set of sync rules that are global.
You are correct that if you wanted to clone an existing sync rule into a different project area, you would have to export/import it with a new name since we require that sync rule names are unique across project areas. You would also have to modify the cloned sync rules if they reference other sync rules. You can enter an enhancement request to clone a set of sync rules from one project area to another.
Since sync rules are scoped to a project area, there isn't a way to define a set of sync rules that are global.
Thank you for the answer. Infact this is useful if you work with a groupwide standard syncronisation between an external repository and RTC, what is a quite common pattern. As well as to have one or few company wide standards for the RTC process template, that all projects have to follow.
I will enter an enhancement request for that.
I will enter an enhancement request for that.