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 document lifecycle management, multi-stage and asynchronous processes are not uncommon—quite the contrary. The first process steps are carried out with the highest priority. More complex and currently not absolutely essential process steps are carried out asynchronously with a lower priority. This saves time, and carrying out operations in parallel lets you distribute resources more evenly. To resume a process chain, additional information about the current status of the process is necessary. In order to not mix an object's metadata with its status data, there is the possibility to tag objects.
>> Tagging
Audit Trail
The audit trail is the history protocol of an object, serving to document its entire lifecycle. There are many different actions that trigger the creation of a new entry in the respective object's audit trail. In this article, an overview of the different history codes is provided that can occur in the audit trail.
>> Audit Trail - an "Object's History"
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.