| Product Version | 2.4 |
|---|
| Report Note | presentable |
|---|
| Assignee | Antje, Nils |
|---|
Resources & Remarks Concept article linking to the respecive tutorials Modification History | Name | Date | Product Version | Action |
|---|
| Antje | 08 FEB 2021 | 2.4 | New page properties macro. |
To be added to table in section "Inteceptor Types": Interceptor type | Evaluation target of the predicate | Interceptor input data | Description |
|---|
dms.request.objects.upsert.database-before | All objects of the objects list in the data part of the multipart body after enrichment. | a multipart request body | 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. |
To be added as H1: Interceptor Configuration Example The following example configures an interceptor that will be trigger by every update of a content (action code 301). At the take-off point after the REPOSITORY service, the enriched request body is passed to the external endpoint specified by url. To activate this configuration, the REPOSITORY service needs to be restarted. | Code Block |
|---|
| language | yml |
|---|
| title | Example interceptorConfiguration.json. |
|---|
| linenumbers | true |
|---|
| {
"interceptors": [
{
"type": "dms.request.objects.upsert.database-before",
"predicate": "spel:options['action']==301",
"url": "http://exampleinterceptorcontentupdate/api/dms/objects/upsert",
"useDiscovery": true
}
]
}
|
|