...
In our example of asynchronous full-text indexing, the API-gateway service is responsible for evaluating the system hook. To apply the configuration, the API-gateway service must be restarted after saving the configuration file. Messages will then be send to the messaging system haben wir hier was zur Installation for the import of compound documents.
AMQP Hook Types
dms.response.insert (previous object.insert.document)
Please exchange the previous denomination (object.insert.document) by the current denomination (dms.response.insert). The old denomination will not be supported in yuuvis® Momentum 2.4 anymore.
Response Format | JSON | |||||
---|---|---|---|---|---|---|
Description | Object creation events can trigger this AMQP Hook with the corresponding object properties in its body. | |||||
Example Predicate | 1) reaction to every object creation: 2) reaction to every object creation having a content 3) reaction to every object creation without content: | |||||
Action Codes - History Codes | 101 - OBJECT_CREATED_WITH_CONTENT 100 - OBJECT_CREATED | |||||
Example Response |
|
...
Response Format | JSON | |||||
---|---|---|---|---|---|---|
Description | Object update events and tag operations can trigger this AMQP Hook with the corresponding object properties in its body. | |||||
Example Predicate | 1) reaction to every object update: 2) reaction to every tag creation: 3) reaction to every tag deletion: 4) reaction to every metadata update: 5) reaction to every content update: | |||||
Action Codes - History Codes | 300 - OBJECT_METADATA_CHANGED 301 - OBJECT_DOCUMENT_CHANGED 303 - OBJECT_UPDATE_CONTENT_MOVED 110 - OBJECT_TAG_CREATED 310 - OBJECT_TAG_UPDATED 210 - OBJECT_TAG_DELETED | |||||
Example Response |
|
dms.response.
...
delete
Response Format | JSON | |||||
---|---|---|---|---|---|---|
Description | Object deletion events can trigger this AMQP Hook with the corresponding object properties in its body. | |||||
Example Predicate | 1) reaction to every object deletion: 2) reaction to every object deletion of type 3) reaction to every failed deletion of objects that were flagged for deletion: | |||||
Action Codes - History Codes | 200 - OBJECT_DELETED 202 - OBJECT_FLAGGED_FOR_DELETE | |||||
Example Response |
|
...