Page Properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
RessourcesRemarksThis article is meant to offer the functional context for the technical implementations tagging and schema flow and is important as such. |
Excerpt |
---|
Information on tagging and schema flow functionality in the context of a document's lifecycle |
Section | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
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.
Repurposing - Schema Flow based on 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 of thê basic schema of in the schema for the assigned document type, which defines theThe goal is to provide a way to change the schema for individual instances of an object during the document lifecycle. This enables you to categorize 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..
Defined secondary object types in the schema - marked as "dynamic" - 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 is available.
Processing by Tagging Functionality
To support you setting up special processes around your documents
...
documents
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
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
Summary
Info | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
Read on
|