Page Properties | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Resources & Remarks Modification History
|
...
Section | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Excerpt |
---|
FeaturesHere, you will find some of the new release's features. Check out the Change Log for further information on all changes. Schema - Defining Object TypesAccording to your specific needs you set up the underlying schema. It is based on a set of so called object types and a set of properties. In detail you define object type definitions for documents, secondary object types as well as folders. Secondary Object TypesSecondary object types allow you to design a more complex schema. In a way the idea correlates to the concept of inheritance: they can be used to create property groups which can be referenced by other object types (e.g., documents or folders). Like other object types, a secondary object type itself can have references to properties. By referencing a secondary object type, the properties of the group will be "inherited" by the object type. In general, secondary object types are abstract and cannot be instantiated. Folder Object Type DefinitionYou define folders as structuring elements either in your global, tenant-specific or application schema. They do not have their own content files in contrast to document object types and cannot be set up in a hierarchical structure – a folder inside a folder is not allowed. (As of version 2.4, a folder hierarchy will be possible.) Folders allow the grouping of multiple documents and have their own metadata which will not be inherited by the assigned documents. Similar to a document object type a folder can reference a secondary object type's property group. The properties can be used as regular properties on folder level. Folders with documents assigned to them cannot be deleted. The document object types are the elementary object types of your schema in which the "real" content is stored. During import or update of a document the object ID of the target folder is provided as the new object's parent ID ( Classification Attribute for Property DefinitionWhen defining the set of properties for your object type additional attributes are available per property. For further processing – e.g., for the presentation and validation in the client – a Webhooks - Manipulating MetadataSystem hooks (AMQP Hooks and Webhooks) are functions that apply to core functions of the yuuvis® Momentum API whenever certain conditions are met and that extend or modify those functions. As such, they serve as a modular, external approach for the introduction of new functionalities as extensions of already existing ones. A webhook extends the function by an HTTP call. Whenever the condition is true, an optional HTTP call to a web URL is performed. For the manipulation of an object's metadata upon the first import, we introduced a new POST webhook type |
Section | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|