Page Comparison

The Interceptor allows for manipulation of the metadata before storing in the database.

It can be trigger by

• an object import,
• an update of the content or
• an update of the metadata.

The take-off point of the interceptor is after the REPOSITORY service. The initial request body is already normalized, validated and enriched with system properties as can be seen in the examples provided below.

The enriched multipart request body is taken by the interceptor. It always contains a data part, that contains an objects list with the metadata of the affected objects. For each object, the options section contains the parameter action that indicates the type of the call in an action code.
The predicate is applied to every single object in the list. The Interceptor is triggered for the whole object list as soon as one object satisfies the predicate. 

Within the interceptor, any user-defined operation can be executed on the corresponding metadata, e.g. by calling an external endpoint. Afterwards, the modified multipart has to be routed back to continue the regular process at the suitable point.

If the interceptor should continue the regular process exactly at the take-off point, pass the multipart to http://registry/api/dms/objects.

POST /api/dms/objects

POST /api/dms/objects/{objectId}
PATCH /api/dms/objects/{objectId}
POST /api/dms/objects/{objectId}/contents/file

Repository service

The predicate is applied on all objects of the object list in the "data" part. If at least one object matches, the interceptor is called.