Everything within this section is only visible while editing. Use Page Properties ID "STUB", "REFACTURE", "PROGRESS", "rDEV", "rDOC", "rLANG" and "DONE". Everything contained within the table is displayed in the (INTERNAL) Reports page.
Resources & Remarks
Modification History Add a new line to this table and fill it whenever you edit the page.
|
Brief (!) description of what this article is about. Example: Choosing an authentication method for yuuvis® Core API. instead of This article details the authentication methods compatible with the yuuvis® Core API and how to choose the correct one for your use case. This excerpt can be displayed in tables generated based on confluence labels. |
CMIS
The CMIS-Based Query Language serves to standardize DMS requests with yuuvis® Ultimate. It consists of a subset of the SQL-92 grammar, augmented by a syntax for requesting full text. Thus, the CMIS query language provides a relational view of the data. The virtual tables requested in the FROM clause correspond to DMS object types and the virtual columns requested in SELECT correspond to the CMIS properties (metadata).
>> "CMIS-Based Query Language"
Compound document
Compound documents are combinations of the binary coding of several individual documents, which can be translated back into the individual documents by means of the intervals (ranges) in which the binary content of individual documents can be found. Compound documents consist of content and metadata, just like any other document (object) in the system.
Content digest
When a document is stored a content digest is generated automatically (Secure Hash Algorithm, SHA256). This digest is returned as a hex-encoded value and is stored together with the metadata of the document. The digest is the only sure way of identifying that object. The hex-encoded value allows you to verify that e.g. the document remained unchanged.
>> "Endpoint | Validate content digest by ID ..."
Document
Business objects of a type that can contain a content file in addition to its metadata. Content files can be office files, pdf files, e-mails, image files, video, etc.
>> "Endpoint | Store one or more documents ..."
Endpoint (operation)
The yuuvis® Momentum product provides a set of endpoints (functions).
An endpoint is one end of a communication channel you use as touchpoint for interacting with yuuvis® Momentum from your web application, for example. It can include a URL of a server or service and is the location from which the resources can be accessed to carry out their function.
History
The history of a business object gives detailed information about the actions and modifications that have been carried out for a given object, e. g., the creation of a document or download of the document file as PDF. Each action or modification is stored in a separate history entry. In yuuvis® Momentum, the object's history protocol is called audit trail.
>> "Endpoint | Get a list of history entries by ID"
Interceptor
The interceptors allow for project-specific extensions of the yuuvis® Momentum standard process flows. The running process flow can be redirected by a condition set on the processed object that has to be specified in the interceptor definition. Whenever the process flow meets the condition, the project-specific process extension is included for the currently processed object at this position of the process flow. Thus, the alternative process can entirely replace the standard one from this position on or resume the standard process at a specified position.
>> Interceptors
Metadata
In yuuvis®, metadata are either basic metadata that are determined by the system, e. g., the creator or creation time of an object or describe the specific properties of a business object (custom metadata), e. g., the sender and recipient of an email or the customer number. These metadata can be used as search parameters to find business objects in the system.
>> "Endpoint | Get document metadata by ID"
Multipart body
For transferring data of several types (e.g. a binary file along with a JSON object) in a single request you typically use multipart body. This type of request combines one or more sets of data, separated by boundaries, into a single body.
Object
In general yuuvis® Momentum manages two main types of objects: folder and documents. The business integrator defines one or more object types and their properties according to specific needs. Any document imported for example will need to be classified as exactly one of the object types defined for documents in the schema of the system. An object contains a set of system-specific basic metadata and depending on its object type it contains custom metadata.
>> Object Type Definitions
Rendition
Document conversion that allows you to carry out transformation processes of various document files into text, pdf, image and more. The PDF can be used, for example, for document previews or dispatching options.
Schema
The schema is the data model defining the object types and property types. Any object's metadata validation is based on the schema. Furthermore, the schema is essential to be able to compose search queries and conditions in permissions.
>> Schema - Defining Object Types
Tenant
A client organization that is served by yuuvis®. This organization’s data is stored in a separate database. A specific instance of yuuvis® with accounts and groups.
>> "Endpoint | Get the raw tenant schema"