We're working in a multi-user environment and have discovered that different teams would duplicate stereotypes, since a stereotype that is created in a diagram belongs to the package that owns the diagram.
It would reduce the duplication if we could make Rhapsody create stereotypes in a default package, that way, folks could just look in the one package before creating a new one.
Has anyone accomplished something like this?
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2013-03-11T17:32:29Z by SystemAdmin
Pinned topic Assign default package for new stereotypes
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-11T17:32:29Z at 2013-03-11T17:32:29Z by SystemAdmin
shanz9903 270003S6R4268 PostsACCEPTED ANSWER
Re: Assign default package for new stereotypes2013-02-27T09:26:54Z in response to SystemAdminI normally create my stereotypes in my <CompanyName>Profile.sbs.
Then every project can add this profile and use all the stereotypes.
All new projects can be made to automatically include this profile too using the prp files with properties such as AutoReferences.
You could just outlaw creating shareable local stereotypes.
I know this isn't quite what you were asking.
SystemAdmin 110000D4XK1305 PostsACCEPTED ANSWER
Re: Assign default package for new stereotypes2013-03-11T17:32:29Z in response to shanz9903Hi Shanz,
interesting topic you are covering now. How do you "outlaw creating shareable local stereotypes"? Some event triggered plug-ins can be used but maybe you found another way via properties, etc?