...

The yuuvis® Momentum Schema

All work with yuuvis® Momentum begins with a data model – the yuuvis® Momentum schema. The schema is used to define object types via which users create and manage business objects. It is part of yuuvis® Momentum core and can be accessed or modeled only via the corresponding core endpoints.
>> Schema - Defining Object Types

The schema is divided in three parts that can be customized independently by means of separate endpoints. Thus, permissions can be set for customizing the individual parts.

...

yuuvis® Momentum uses schemata to ensure a valid and consistent data structure for the metadata of stored business objects. The metadata consists of properties. Some predefined system properties are automatically assigned to all objects during their creation. Further properties can be defined in a schema.
>> Defining Object Types for a Library-based Client

The individual properties can be referenced in object type definitions. If you create a business object, you will select one of those object types. It determines the set of properties that will be available for business objects.

Schemata are configuration files containing property and object type definitions.

• All tenants can refer to the global system schema.
  → yuuvis® architect allows its management only for users with the YUUVIS_SYSTEM_INTEGRATOR role.
• An app schema contains object types for one specific application. If necessary, multiple application schemata can be defined. The object types defined in the application schemata can be used by all tenants.
  → yuuvis® architect: Modeling of metadata forms is possible only with the YUUVIS_SYSTEM_INTEGRATOR role.
• A tenant schema contains object types for one specific tenant. Users cannot use objects types defined in a tenant schema not belonging to their own tenant.
  → yuuvis® architect: Modeling of metadata forms is possible only with the YUUVIS_TENANT_ADMIN role.

...

• Additionally, each tenant can configure an own tenant schema. All properties and object types defined in a tenant schema are not available in other tenants. 
  → yuuvis® architect allows its management for users with the YUUVIS_TENANT_ADMIN role.
• An app schema contains property and object type definitions that will be available in all tenants for which the concrete app is enabled.
  → yuuvis® architect allows its management only for users with the YUUVIS_SYSTEM_INTEGRATOR role.

Note: The roles used by yuuvis® architect are not defined in the schema but in a tool-specific role set. This role set is also required for yuuvis® Momentum clientthe default library-based clients. However, yuuvis® Momentum allows you to define your own rolesetrole set. If you do so, you will not be able to use yuuvis® architect or yuuvis® Momentum client.

Idea of Object Types

An object type identifies a business object by means of specific metadata which can be used to find and identify the object. Metadata describes the properties of a business object. For example, an invoice document is defined by its invoice date, invoice number, and vendor/customer. The properties are defined and assigned to the object types in the schema.

...

From document and folder object types defined in the schema, document and folder objects (short documents and folders) can be instantiated. Those objects have the properties that are assigned to the object type in the schema from which they are instantiated. Documents and folders in the system can be found via their metadata.

Document object types enable the instantiated documents to include a document file in addition to metadata. Document files can be text files, e-mails, image files, etc. Documents can reference a folder to be their parent.

Folder object types enable the instantiated folders to be the parent of multiple documents in the system. Each document can be contained in one parent folder only.

...

Secondary object types (SOT) are abstract object types. No business objects can be instantiated from SOTs. However, they act as groups of properties that can be referenced in multiple document and folder object type definitions. Thus, the properties for SOTs can be available also for the referencing object types. These additional properties are included in the search as well.

...

...