Table 15 details the event notification features supported by the
connector.
Table 15. Event notification features
Category | Feature | Support | Notes |
---|---|---|---|
Connector Properties | Event distribution | No | Event notification is done via callback, and the TPI Server is running in the connector process space. |
| PollQuantity | Full |
|
Event Table | Event status values | Partial | Event status is maintained via the location of the event information and the extension on the event file. |
| Object key | N/A |
|
| Object name | N/A |
|
| Priority | N/A |
|
Misc. | Archiving | Partial | The connector does not have an event table per se. It stores information about incoming documents and their status on the file system. |
| CDK method gotApplEvent | Full |
|
| Delta event notification | No |
|
| Event sequence | Partial | Maintained based on how they are received from TPI Server, not based on priority. |
| Future event processing | No |
|
| In-Progress event recovery | Full |
|
| Physical delete event | No |
|
| RetrieveAll | No |
|
| Smart filtering | N/A | Because we don't have an event table, we don't have any way of filtering out these 'duplicates'. TPI Server will partially take care of this functionality. |
| Verb stability | Partial |
|