Templates and assets
A template is a type definition for assets. An asset is an instance of this type definition. The template is based on XML and defines, for example, the possible attributes, possible relationships to other templates and which actions can be triggered.
A single asset represents the definitive values within the possible values, i.e. the values within the restrictions defined in the template, e.g. the characters of a string attribute or the IDs of the associated assets.
Architecture
The Data Management module is based on different objects for the management of master data: Organizations, templates and assets.
The organization is the functional and technical environment within which templates and assets are assigned and stored. The OrganizationID in particular defines the storage location in which templates and assets are stored and can be found bundled together.
A template is a template. It defines the properties and appearance of data that is stored in assets. Other templates can be referenced within templates; these are relational relationships.
In each template itself, the relationship to the desired other template is defined using a parent-child relationship. Below this, you can define different properties for the relationship, such as the number of parents that reference the child.
An asset is ultimately the specific master data object defined on the basis of the template. This now contains real data that is actively used.
The diagram shows a possible structure for a supermarket chain. The organization is the supermarket, which in this case has several stores. Each store has different products, whose quantities, stock information and properties it manages. A store has several products, while each product belongs exclusively to one store.
