...
| Page Properties | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Status | |||||||||||||
| Status | ||||||||||||||
| colour | Green |
| ||||||||||||
RessourcesResources & Remarks
Modification History
|
| Excerpt |
|---|
| This tutorial shows how we can use a Java application to make a request to the Core API of the yuuvis® API system to retrieve the history entries of a DMS document. In addition, it briefly describes which history entries are generated for a document. |
...
- Set-up yuuvis® API system (see minikube setup, for example Installation Guide)
- A user with at least read permissions on a document type in the system (see tutorial for permissions)
- Simple Maven project
The History Entry
...
The returned history for a DMS document is a list of all history entries.
Which History Entries Are There?
For the various actions, such as import, retrieve, update, and deletion of a DMS document, there are the following history entries:
Import:
- OBJECT_CREATED
- OBJECT_CREATED_WITH_CONTENT
The difference between these two types of import is that the first type imports only metadata and the second type imports metadata and content simultaneously.
Retrieve:
- DOCUMENT_ACCESSED
- METADATA_ACCESSED
- RENDITION_PDF_ACCESSED
Each of these types distinguishes between retrieving only metadata, content, or the PDF rendition of the content of a document.
Update:
- OBJECT_METADATA_CHANGED
- OBJECT_DOCUMENT_CHANGED
Here, a distinction is made between updating the metadata and the content of a document.
Delete:
- OBJECT_DELETED
- OBJECT_FLAGGED_FOR_DELETE
...
All history codes available in yuuvis® Momentum are listed and explained in the concept article on the Audit Trail.
Summary
In this article, we used theOkHttpClient to retrieve the history of a DMS document and output the result to the command line. If you want to use a client to send several requests to the system in the same user context, we recommend a session handling, such as described here.
...