Object Types

As a component of the project schema, object types are the basis on which users in yuuvis® RAD client create business objects. Business objects can be folders and documents.

Database fields for the metadata of a business object are defined for object types. Metadata describes the properties and values of the business object (folder and documents). Folders and documents in the system can be found via their metadata.

Before users in yuuvis® RAD client can create and manage business objects of the object types, they must be assigned the permissions via roles in order to access the object types.

The maximum number of object types is specified in the license file.

Document Types

Document types can be created in an object type group for a better overview.

A document file is generally assigned to documents, in addition to metadata. Document files can be text documents, e-mails, image files, etc.

Folder Type

Each object type group can contain a folder type. Fields of the folder type can be included in the search by documents.

Tree Items

The folder content will be displayed in a structure tree. Tree items are configured for the structure tree, and the content is listed based on these tree items. Basic tree items are document types, creators, and creation periods, for example. Tree items can be nested, for example, documents of one document type can be displayed as other tree items by metadata.

Tree items also have a storage function: Documents can be stored in this structure and receive tree items such as document type and metadata as properties.

Abstract Object Types

Abstract object types are templates for other object types, that is, other object types can be derived from abstract object types. The fields of an abstract type are adopted. Multiple abstract object types can be integrated as a template for one object type. No business objects can be created from abstract object types.

If a new object type is derived from abstract object types, all the properties and fields of the abstract object types are inherited by the new object types. Other properties can then be defined for the derived object type. Changes to abstract object types affect the fields of the derived object types. For example, if you add a field to an abstract object type, the field can be integrated into all the derived object types, though it may need to be transferred to forms.

Users in yuuvis® RAD client can use an abstract object type to search for business objects of all object types where the abstract object type acts as a template. Search forms can be created for abstract object types.

Forms for Metadata

For each object type, yuuvis® RAD automatically creates a default form with all the metadata of the object type.

You can create separate forms for the Create, Edit, and Search working scenarios. For example, you can hide fields from a search form that are only necessary to create an object.

You can use default forms if you don’t want to create custom forms. These forms are generally sufficient for technical data transfers or for linking yuuvis® RAD as an archiving solution.