...
| Page Properties | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
Resources & Remarks article is too brief and not fitting the intended structure. Topic should actually link to SOTs, link to the endpoints for changing storage, and link to a tutorial outlining the usage. Modification History
|
| Excerpt |
|---|
A retention can be used to ensure that a document object is not deleted and the binary content file assigned it is not deleted or changed. |
...
It is possible to extend the functionality of yuuvis® Momentum by configuring Webhooks webhooks and adding custom microservices. Thus, you can build your own specialized solution to realize automated retention management.
You could automatically One possible use case would be to calculate the required retention values based on the individual object's metadata and set them, e.g.,
- during the object creation,
- during a specific update of the object's metadata, or
- triggered by a specific metadata update of the parent folder object (if you use
system:parentId).
For the deletion of document objects with expired retention, you can introduce automated custom solutions as well. E.g., you could build with a custom microservice in your system that automatically searches for objects with expired retention and
- deletes them,
- updates their state in the lifecycle via Tagging tagging, or
- starts a workflow process asking responsable assigned users to delete them (if BPM-ENGINE Service is used).
...