Page Comparison

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

It can be triggered 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 content stream 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 action parameter that specifies 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 entire object list as soon as one object meets the predicate. 

Within the interceptor, any user-defined operation can be executed on the corresponding metadata by calling the external endpoint specified as url in the interceptor configuration. Afterwards, the modified multipart has to be routed back to continue the regular process at a 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

POST /api/dms/objects/{objectId}
POST /api/dms/objects/{objectId}

PATCH /api/dms/objects/{objectId}
PATCH /api/dms/objects/{objectId}

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

Repository service