All,
I can't seem to find the ability to create a new custom object type, I only see the ability to Rename an already existing Object Type. I am in the Administration Console/Configurations/Methods/Object Type location.
Any help on creating a new one otherwise I guess I will have to rename one. Would also like to create a new API Name with that new Object type too
Thanks
M. Zschuckelt on
Hello. Here are the answers:
1. You cannot create new object types.
2. You cannot define API names for any user-defined ARIS artefacts. You have to access them via their Type Number or GUID. Observe, that the type number is only valid as long as you stay on the same tenant with your databases. So in order to write portable scripts that use type numbers, you should populate some variables (your personal API names) with the type numbers that are assigned to the GUID of each type. There are methods that return the type number for a given GUID.
3. Renaming an object type just for the sake of having an own object type may become a lot of work, because whichever object type you choose, it will have a hell of a lot of semantic connections types in it's backpack that you cannot use, because you declared that object type to be something different. And renaming connection types also is dangerous, as they may occur also between other objects that you use. Also you would have to re-invent the symbols, if the standard ones don't suit the concept you want to represent. If you just want some concept renamed, e.g. instead of "information carrier" you prefer "media type", which someone might argue represents the same idea (don't start arguing on this example, it might be bad), renaming the object type is the right approach. Most of the time what people see is the symbol type. And in many cases you will find, that a certain concept is another "flavour" of a more abstract concept. If that is the case, you should invent your own symbol type for that abstract concept it maps to. With the method filter you have full control, which connection types are allowed between which symbol types in which model types. So most of the time it is o.k. to realize own pseudo "object types" with the definition of a new symbol type for an object type that is a close match.
Regards, M. Zschuckelt