This article details the authentication methods compatible with the yuuvis® Core API and how to choose the correct one for your use case.
Define properties and reference them in object type definitions for the entire system, for individual tenants or for a specific app.
A yuuvis® Momentum user has to be authorized to the functionality of the system by assigning roles. For the individual roles, permissions can be set to allow actions on objects restricted by defined conditions where appropriate and the usage of specific endpoints can be controlled.
How to query in an SQL-like manner.
A description of the structure in which yuuvis® Momentum expects objects to be formatted and returns objects.
The described database tables are used to manage the metadata of objects.
Binary content files can be imported and assigned to document objects in yuuvis® Momentum. Archiving can be managed and renditions can be retrieved.
Various types of renditions are available for binary content files to provide their information in different formats.
This article gives information on tagging and schema flow functionality (secondary object types) in the context of a document's lifecycle.
A retention can be used to ensure that a document object is not deleted and the binary content file assigned it is not deleted or changed.
Management of apps that are based on yuuvis® Momentum via schema, permissions, system hook configuration and availability configurations.
Structure and identification codes of errors that can be thrown during different processes.
Define additional actions triggered by specified events, extend the functionality of yuuvis® Momentum API.
Intervening a running process at a certain position and redirecting the process flow in order to include project-specific processing steps.