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 Trail - an "Object's History" page can be moved here as subpage (Inga)
• Antje: make page ready for review

Modification History

Introduction

...

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  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  The steps include: creation, storage, categorizing classification via object types , and metadata assignment of (single properties , or property groups (secondary object types), 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

...

(schema flow)

To support your specialized steps in the best possible way use our "tagging" option to set up a traceable stateful processing.

support in designing the processes and offer a high flexibility by

The goal is to provide a way to change the schema for individual instances of an object during the document lifecycle. This enables you to classify objects at a later point in time and to add or remove metadata at runtime by changing the type. The addition and removal of individual properties is not to be supported. The changes are always made using SOT.

To support you setting up special processes around your documents  

Tags - nachvollziehbare, statusbehaftete Verarbeitung von Dokumenten

Unterschiedliche Verarbeitungen über ein System
Nachvollziehbarkeit
Tag mit Status mit Trace-ID
Audit mit Trace-ID
Log mit Trace-ID = Unterstützung für Support und Admins
Erweiterte Suchmöglichkeiten

Subsection(s)

for (int i = 0; i < 10; i++)
{
	System.out.println("Hello World " + i);
}

...

Flow Using Secondary Object Types

Depending on your business use cases it may be important to change a document's classification options during its 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.

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 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"

...

Another Tutorial

...

...

Another Concept Article

...

...

Another interesting Tutorial

...