Hello all,
I am wondering why each model object in the BizArchitect/Designer is located (by default ... and by chance?) within the group where it was initially created. Is there any modelling philosophy that suggests this ... or is this just the best guess to have it "somewhere"?
Any thoughts are welcome!
Currently, I am preparing an XML-Ex- and Import that will move all objects to a dedicated group like "Model Objects Repository". Unfortunately, the tree view does not allow for multiple (objects-)selection, which would allow me to do this manually in a reasonable time.
Stefan
Hi Stefan,
ARIS access rights are related to ARIS groups. That's why object definitions are always created in the same group where the model is saved. So all users that should see the model have access to all included objects. If you move an object to an other group you have to make sure that all relevant users will at least have the access right 'read' . Otherwise these objects will not be fully displayed.
To solve your problem I'd highly recomment the report (Administration) Move object definitions to the group of the model. Using this report you can select object types to be moved to the defined group. Not only to the group were the model is saved.
Regards
Roman
Hi Stefan,
I guess the way to think about it is that, yes, the objects have to be captured in the repository "somewhere." So initially, all objects are stored in the same group as the first model on which they occur (in other words, the model for which they were intially created). It's kind of a best practice as you mention to create an "object library" for easily reusable objects such as roles, application systems, technical terms (data), etc. Further, I would suggest that the fatsest way to manually populate your object library groups would be to first use the "Find" functionality to search for each of the object types for the library. Then, these objects can be "cut" from the Find results window and "pasted" in to the target library group. Alternatively, you can grab the objects with a right mouse click and drag them to the target library group. Thus, by making periodic "sweeps" of the database, you can grab any "new" library objects created by your users (considering that you don't have an ARIS role of "Library Administrator" currently).
Hope this was helpful.
Best regards,
Bob
Hi Stefan,
Further to Bob's response above, having a common object library is best suited for reusable objects and not for every other object in your process models.
As for picking those "reusable" objects spread across multiple groups, I agree the Find results will be the easiest way.
Regards,
Shankar
