Versions Compared

Key

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

...

Page Properties
hiddentrue
idPROGRESS

Product Version2.4
Report Notepresentable
AssigneeAntje, Nils

Resources & Remarks

Modification History

NameDateProduct VersionAction
Antje08 FEB 20212.4New page properties macro.



As of Version2.4
HTTP MethodPOST
Response FormatJSON
Description

This Interceptor can be trigger by 

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

A multipart request body is posted. It always contains a "data" part, that contains an object list with the metadata of the affected objects. On an import or content update it can contains further parts as with renditions.

The majority of the metadata in the "data" part is still raw. That means it is not yet normalized, validated and system properties are not yet set. Only content properties are available in case of import or content update. For more details take a look at the examples below.

If the regular import route should be continued, pass the multipart to http://registry/api/dms/objects.
The metadata of the final objects are returned.

Requirements for external endpointThe target URL must be a POST endpoint accepting a multipart request body and returning a list of objects.
Affected API Requests

POST /api/dms/objects

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

Restart Service

Repository service

HeaderAuthorization-Header
Predicate

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.

Examples

Import with Content

...