Object types can have hierarchical relationships. For example, the relationship between a customer company and its contact person can be defined so that the Contact Person object type is a subtype of the Customer object type. Viewing the value list for the Customer object type also displays the contact persons filtered by customer. You can also, for example, define the properties Buyer and Buyer contact, in which case the contact person selection is filtered into the Customer (Buyer) field by selected customer.
Use the Add... and Remove buttons to add and remove subtypes. You can also define the object type being edited as a subtype of another object type.
For more information, refer to Value Lists/Contents.
The actual final object receives automatic permissions when a value with automatic permissions specified is added for the object.
You can activate the automatic permissions by value, value list, object type or class. You can specify the automatic permissions for each object type in the same way as for each value.
Aliases can be used for identifying semantically equivalent metadata. For example, when importing objects from another vault, their Date and Description properties can be mapped to the target vault's equivalent properties on the basis of aliases even if the properties' internal IDs and/or names are different. That is, the aliases refer to semantically equivalent metadata in different vaults, or in other words, alias is a common ID for the same metadata definition between several vaults.
The alias is defined as a common ID with the same name in both source and target vault.
When defining the alias, you can use various external data type and archive standards, such as SÄHKE2, MoReq2, and Dublin Core.
For more information, see Associating the Metadata Definitions.