It's all about the answers!

Ask a question

Fine-grained Customization of Configuration Data - RTC 6.0.1 Support

IBM Rational Product User (23316) | asked Jun 24 '16, 10:59 a.m.

Does RTC 6.0.1 supports Fine-grained Customization of Configuration Data ?

We have some core processes for problem management. We have taken Scrum template as a base and customised scrum processes to meet our needs. The customised template is a base process template for multiple departments within our organisation. But each department has a flexibility of adding attributes and wotkitem types as per their need. When we configure do shared project one as master and others as slave, if slave customises configuration data, the link with master is broken. It no more inherits configuration from master.

If Fine-grained Customization of Configuration Data is not supported, what is the best practice to do it in RTC 6.0.1 ?


Accepted answer

permanent link
Geoffrey Clemm (30.1k33035) | answered Jun 24 '16, 2:59 p.m.
There are a set of specific customizations you can do without breaking the master/child relationship.
Note that they are done via editing the process XML (no GUI for it yet). 
This is described in the online documentation:

That page will point you to the following wiki page for details:
IBM Rational Product User selected this answer as the correct answer

IBM Rational Product User commented Jun 27 '16, 6:34 a.m.

 Thanks Geoffrey.

We have three server (Dev, QA, Prod). What will be your recommendation on migrating/importing process template changes from Dev to QA to Prod ? Do you recommend the same  approach of updating XML in master project ?


Geoffrey Clemm commented Jul 01 '16, 12:57 a.m.

I wouldn't recommend updating the XML in the master project, only in the slave projects (and I only recommend updating the XML in the slave projects if you are adding/removing delta XML declarations in the slaves).   One reasonable approach for migrating process changes is to create a process template from the current master, create a new project area in Dev from that template, and then make your process modifications in that new Dev master project area.   When you are happy with the new process, close down that new master project area for changes, and notify your project admins to share from the new master project area (they can share back to the original master project area if things don't look right).   Note that I'm not bothering with a separate QA project area, but rather doing QA against the new dev master project area.

IBM Rational Product User commented Sep 29 '16, 7:16 a.m. | edited Sep 29 '16, 7:17 a.m.

 Thanks Geoffery.

Can you share any post which explains impact of changing your master process template reference on slave project data? 

Geoffrey Clemm commented Oct 01 '16, 12:30 a.m.

Your answer

Register or to post your answer.