Change Flow Target for a component in a Stream

Hi,

I have the following structure of components and Streams:

Architecture Stream:
Component_Binaries (this component will have to be reused by applications)
Component_Source

ApplicationA Stream:
Component_A
Component_B
Component_Binaries (from Architecture)

ApplicationB Stream:
Component_C
Component_D
Component_Binaries (from Architecture)

Users working on ApplicationA and ApplicationB would like to have
automatic notifications in their workspaces when a new baseline of the
Component_Binaries is created (so they would like to create a "link" to
the Component_Binaries component instead of having in each ApplicationX
Stream a fixed baseline that has to be "manually" update by an
integrator role each time there is a change in the Architecture STream.

A workaround is to use the "ChangeFlowTarget" option for the
Component_Binaries to change the flow target to the Architecture Stream
(just for this component) instead of flowing to the default ApplicationX
stream, so RTC automatically notifies of the changes.

But this would mean that each individual user has to change manually
this change flow for the common components and can be tedious.

IS there any way to have this "ChangeFlowTarget" functionality for
individual components at the Stream Level, so I can configure in the
Stream that a component is a flow target "link" to a component in
another stream, so all repository workspaces for users have the same
configuration from the beginning?.

Or any other idea/workaround to simulate this scenario in RTC?

Thanks,

Ana

Will users be delivering changes to Component_Binaries in the
ApplicationA and ApplicationB streams? If not, they should create a
workspace flowing to the Architecture stream and only load
Component_Binaries. They'll see the changes whenever they're
delivered to that stream. It wouldn't be necessary to have
Component_Binaries in the Application streams.

This functionality is requested in work item 127541 "Allow a stream to
share a component from another stream". Please add a comment to that
work item to indicate your interest/support.

You can simulate this behavior with some manual setup work today, by
telling the developers to specify the Architecture stream as the flow
target for the Component_Binaries component (in a workspace, you can
specify different flow targets for different components). So instead of
keeping a reference to Component_Binaries in the ApplicationA and
ApplicationB streams, you would instruct ApplicationA and ApplicationB
developers have the flow target of their Component_Binaries component be
the Architecture stream.

Cheers,
Geoff

On 5/4/2011 4:47 PM, Geoffrey Clemm wrote:
This functionality is requested in work item 127541 "Allow a stream to
share a component from another stream". Please add a comment to that
work item to indicate your interest/support.

You can simulate this behavior with some manual setup work today, by
telling the developers to specify the Architecture stream as the flow
target for the Component_Binaries component (in a workspace, you can
specify different flow targets for different components). So instead of
keeping a reference to Component_Binaries in the ApplicationA and
ApplicationB streams, you would instruct ApplicationA and ApplicationB
developers have the flow target of their Component_Binaries component be
the Architecture stream.

Cheers,
Geoff

Thanks Geoff. The problem with that option as commented Ana, is that
each developer will need to modify his new Repository Workspace manually.

We are looking for a mechanism that this idea can be setup just once by
the "administrator" in the stream so all developers that come to this
project simply create a Repository Workspace pointing to that stream and
that's all.

I think the WI you commented is what we are looking for, but I will read
it more carefully.

Thanks,

Chemi.