Information on tagging and schema flow functionality (secondary object types) in the context of a document's lifecycle.
Table of Contents
Introduction
Efficient document management from creation to deletion ...
Completely organize your document's lifecycle and streamline every step in yuuvis® Momentum – from the minute it’s created to it's eventual archival or the minute it’s destroyed. Proper procedures throughout the document’s lifecycle are an important part - a set of defined processes help to organize, store and deliver information crucial to its operation in the most effective manner possible. The steps include: creation, storage, classification via object types and metadata (single properties or property groups), delivery or sharing, repurposing, review and reporting, archiving and / or destruction.
yuuvis® Momentum supports you in various ways to deal with the challenges during a document's entire lifecycle.
Schema flow using Secondary Object Types
According to your business use cases it may be important to change a document's classification options during it's lifecycle: e.g. triggered by certain conditions further properties are needed or temporary information should be available for a period of time. This implies adding or removing additional properties at runtime, which will be provided next to the defined set of properties in the schema for the assigned document type.
Defined secondary object types in the schema - marked as "floating" - are used to provide the additional properties and enable a "Schema Flow". They can easily be added or removed using the known endpoint for updating metadata (POST /api/dms/objects/{objectId}) to a document's instance. As a result, an extended set of properties can be made available and later on removed again, if only needed temporarily.
>> Changing Schema Structures ("Schema Flow")
Stateful Processing using Tags
In modern data processing chains, asynchronous operations become more and more popular. Concerning the administration of such complex procedures, a status measure is essential. The lifecycle of any document needs to be recorded with a view to a general knowledge on the current state of progress, and in order to enable the prosecution of interrupted processes. If the document status would be located in the metadata, each pass through a multi-stage processing chain would create a completely new version of the whole document, that needs to be stored in addition to the previous one. In contrast, the tags are treated separately. They always have a state and a unique traceid, which is a basis for external support as well as a possibility to control asynchronous operations. These additional features are stored together with the document, but they are completely independent on the metadata and on the document's version. In fact, they are always available for the current version. The management and modification of tags neither creates a new version nor triggers events that become due when documents are modified. The so assigned processing status reflects a concrete state of the document and serves as the basis for further transactions. The tag operations are recorded for any document in its audit trail.
>> Tagging
Summary
This article gave an introduction into the document lifecycle management possibilities provided by yuuvis® Momentum. More detailed information on on each topic can be found in the articles linked below.