We have built universes based on one Core universe, which contains all that is common to all our universes. When adding classes and objects to this core-universe they also become available in the derived universes. However, they are not in the place that we want them, but appear on the bottom of the list of classes/objects(in the same class). Has any of you had this problem and knows of a way to force classes/objects on a specific place in the object list of derived universes…
Thanks for any feedback,
Diederik Dellaert,
PricewaterhouseCoopers
I pasted below something I found in a thread about 3 weeks old…hope this helps!
In version 4.1.2a there is a note in the technic.wri file
Restrictions on Derived Universes
Deriving or linking (whichever word you prefer!) a universe is a powerful feature that simplifies the maintenance burden on your universes. However, you should be aware that it is complex and entails certain restrictions:
ï Hierarchies and contexts defined in a kernel universe are not inherited in a linked universe. They must be redefined in the linked universe. ï You can find more information in the Designer’s Guide. ï CORE_ORDER_PRIORITY=Y or N is a new parameter that allows you to define if objects order are the same in core and derived universe or not. This parameter is set in the appropriate PRM file.
We have built universes based on one Core universe, which contains all that
is common to all our universes. When adding classes and objects to this core-universe they also become available in the derived universes. However,
they are not in the place that we want them, but appear on the bottom of the list of classes/objects(in the same class). Has any of you had this problem and knows of a way to force classes/objects on a specific place in the object list of derived universes…
The CORE_ORDER_PRIORITY is probably just what I need. I suppose I have to
specify it in the RDBMS-section of the prm file which corresponds to my
repository database (since this is another one than my DATA-rdbms).