Stream rename and impact in "Delivery restrictions"
We have lots of streams and each stream has "Delivery restrictions" set.
When a stream us renamed, unfortunately RTC doesn't respect this and simply resets the "Delivery restrictions" in the Team area configuration.
We want to rename streams (due to business requirements). What are the easy ways to retain the "delivery restrictions" in tact ?
Considering that we have lots of components per stream and combinations for access, it is a huge and error prone activities if we do it by hand. We may need to plan for longer down time in worst case.
- Can we write some scripts to do this?
- Can we just add the new names of streams in Team area process configuration xml file?
Is IBM addressing this in future releases to make RTC intelligent enough to remember the stream renaming in delivery restrictions?
Accepted answer
I tracked down the following Defects that sound related to this.
StreamComponentsPermissionAdvisor should avoid using stream/component names in process spec (120435)
Until these are fixed, it will be a manual process of updating the scm artifact names in the process advisors.
Comments
Arun K Sriramaiah
Sep 01 '16, 6:26 a.m.Hi Karthik,
Which is your RTC version ?
Karthik Krishnan
Sep 02 '16, 7:16 a.m.6.0.1. In fact we were facing this from 4.0.2