Sometimes it is helpful to be able to trace the inheritance of types in a model, or identify how objects are related to each other through associations. The definitive reference for this type of information is the set of *Model.xml files distributed with the Alfresco web application. This section shows the content of those files graphically, with one diagram for each model file.
The diagram syntax is essentially UML. The following image shows the bpm:task from the bpmModel.xml file:
These notes will help you read the diagram:
The <<type>> indicates that this is a type rather than an aspect.
The type has one mandatory aspect, cm:ownable, shown in italics just below the type name.
The type has several properties. Properties that begin with a hash (taskId, for example) are protected. Properties that begin with a plus (bpm:description, for example) are public.
The bpm:status property has a default value of Not Yet Started, and it is a mandatory property and has a constraint on its values.
Two imported types are shown. The cm:content type is the parent type as indicated by the line with a triangle. The sys:base type is the target of an association called bpm:pooledActors. In this case, there can be zero or many instances of sys:base associated with a bpm:task.
