Ressources

Resources & Remarks

This article is meant to offer the functional context for the technical implementations tagging and schema flow and is important as such.

•  If this page is published the Audit the Audit Trail - an "Object's History" page can be moved here as subpage (Inga)
• Antje: make page ready for review

Excerpt

Information Modification History

Excerpt
This article gives information on tagging and schema flow functionality (secondary object types) in the context of a document's lifecycle.

Section
border true
Column Table of Contents Table of Contents exclude (Table of Contents|Read on|Tagging|Audit Trail - an "Object's History"|Changing Schema Structures \(\"Schema Flow\"\)|Ressources|Remarks)

Introduction

Efficient Managing your documents in yuuvis® Momentum means efficient document management from creation to deletion ...

Completely organize Keep your document's lifecycle documents' entire lifecycles organized and streamline every step in yuuvis® Momentum – —from the minute it’s it is created to it's its eventual archival archiving or the minute it’s it is destroyed. Proper procedures throughout the document’s lifecycle documents' lifecycles are an important part - —a set of defined processes help helps to organize, store and deliver information crucial to its their 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 Depending on your business use cases it may be important to change a document's classification options during it's its lifecycle: e.g. triggered , 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 Secondary object types defined 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 removed again 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 the article linked below, 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.

Info
icon false
Read on Section Column width 25% Tagging Insert excerpt Tagging Tagging nopanel true Keep reading Column width 25% Changing Schema Structures ("Schema Flow") Insert excerpt Changing Schema Structures ("Schema Flow") Changing Schema Structures ("Schema Flow") nopanel true  Keep reading Column width 25% Audit Trail - an "Object's History" Insert excerpt Audit Trail - an "Object's History" Audit Trail - an "Object's History" nopanel true  Keep reading