Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page Properties
hiddentrue
idDONE

Product Version
Report Note
Assignee

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

NameDateProduct VersionAction
Antje08 FEB 20212.4New page properties macro.
Antje24 MAR 20222022 Summerrefacturing
Agnieszka24 MAR 20222022 SummerrLANG

Automated Retention Management

It is possible to extend the functionality of yuuvis® Momentum by configuring Webhooks and adding custom microservices. Thus, you can build your own specialized solution to realize automated retention management.

You could automatically 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 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 or
  • starts a workflow process asking responsable users to delete them (if BPM-ENGINE Service is used).
Antje25 APR 20222022 Summeradd section "automated retention management"



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.

...

An object under retention cannot be deleted or changed even by users that have a write or delete permissions; retentions take precedence over write or delete permissions.

Automated Retention Management

It is possible to extend the functionality of yuuvis® Momentum by configuring Webhooks and adding custom microservices. Thus, you can build your own specialized solution to realize automated retention management.

You could automatically 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 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 or
  • starts a workflow process asking responsable users to delete them (if BPM-ENGINE Service is used).

Summary

Retentions can be set for document objects via a predefined SOT that provides an expiration date property. Before this date is reached, the document object cannot be deleted and its assigned binary content file cannot be updated or deleted via yuuvis® Momentum API.

...