Event Configuration
Event Rules let you trigger jobs from content service calls. For example, if a file is updated in a source system, an event can be set up to trigger an index.
Field Options
- Name: The name of the document.
- Content Length: The size of the document.
- Content Type: The content type (mimetype) of the document.
Limitations
The previous three field options will currently only work for the following endpoints. This may change in future releases.
/file
/properties
/contentStream
- Content Connector: The
connectorId
which was used. Can trigger on any endpoint. - Event Type: The type of action. See the table below for the action for each end point.
Creating an Event Job
Event Job Tutorial - A walkthrough tutorial on how to create an event job.
Event Types and Endpoints
Event Type | Endpoint | Method |
---|---|---|
FILE_DOWNLOAD | /file | GET |
FILE_DOWNLOAD | /inlinefile | GET |
CREATE_DOCUMENT | /file | POST |
UPDATE_DOCUMENT | /update | PUT |
UPDATE_CONTENT | /updateContent | PUT |
UPDATE_PROPERTIES | /updateProperties | PUT |
CREATE_FOLDER | /folder | POST |
DELETE_OBJECT | /delete | DELETE |
STREAM_CONTENT | /contentStream | HEAD |
STREAM_CONTENT | /contentStream | GET |
FIND_PROPERTES | /properties | GET |
DELETE_ACL | /acls | DELETE |
GET_ACL | /acls | GET |
EDIT_ACL | /acls | POST |
VERSION_DOWNLOAD | /version/content | GET |
FIND_VERSION_PROPERTIES | /version/properties | GET |
CREATE_VERSION | /version | PUT |
REVERT_VERSION | /version/revert | POST |
DELETE_VERSION | /version | DELETE |
LIST_VERSIONS | /listversions | GET |
Related Articles:
Simflofy Integrations Overview
Integration Job Configurations