...

Introduction

If an object is imported to yuuvis® Momentum, a binary content file can be assigned in addition to the object's metadata. The storage of the binary content file is managed by the REPOSITORY service. Afterwards, the metadata are stored in a separate database and indexed for search.
>> Basic Use Case Flows

As soon as the object import process is finished, the binary content file can be accessed as well. Especially, it can be analysed in order to set some content-related metadata properties for the corresponding object. The metadata update is possible, i.e., via POST or PATCH /api/dms/objects/{objectId} and triggers the creation of a new object version. However, in some use cases, it might be necessary to set metadata properties depending on an analysis of the corresponding binary content file already for the first version of the imported object. For this purpose, the binary content file can be accessed from a webhook that is called after storing the content and before storing the metadata. This tutorial describes an example solution using an internal endpoint of the REPOSITORY service.

Setting up the Webhook Service

The webhook entry point has to be located after storing the binary content file and before storing the metadata in the process chain of an object import. For this purpose, the type dms.request.objects.upsert.database-before is suitable.

...