Is it possible to sync a Rhapsody Model Manager component between two project areas?
Use case is as follows using ELM 7.0.2 SR1:
We have a component that holds various profiles/extensions that are defined at a business level to drive consistency in our approach to MBSE,
This component is in it's own project area, and write access to it is strictly controlled. This component is then added to other project areas (for various business projects) via navigating to streams, select Add Component > Component in another repository workspace or stream and grabbing that component.
Is there a way to have changes pushed to the originating project area propagate downwards? Eg. When a change set is delivered to the owning project area, deliveries are made for the project areas that have it added?
I had found some discussion on Flow Targets but my understanding is they can only be used within a single project area. Other guidance hasn't been particular forthcoming or descriptive.
One answer
For all I know the SCM part of EWM, RMM is orthogonal to project areas. There is only one component. The component contains all histories of all files it contains. You can add a component to a stream in any project area that has access to the component (by visibility/owner). Each stream (and repository workspace) selects a specific configuration of the component.
You can select any flow target that is available for you. There is no project area involved in choosing the flow target. The flow target is across a repository - even across repositories, should you use distributed SCM.
So the question is wrong, there is no sync between components, because there is only one component.
The second answer, as far as I can tell, is that you can use the flow target to accept into a repository workspace and then to deliver these changes to a different flow target. This is how you are supposed to integrate changes in a component across different streams.
If there are no conflicts, you can also flow from one stream to another and deliver from one stream to another.
You can also use baselines to select specific states of the changes in components in a stream.
So the question is wrong, there is no sync between components, because there is only one component.
The second answer, as far as I can tell, is that you can use the flow target to accept into a repository workspace and then to deliver these changes to a different flow target. This is how you are supposed to integrate changes in a component across different streams.
If there are no conflicts, you can also flow from one stream to another and deliver from one stream to another.
You can also use baselines to select specific states of the changes in components in a stream.