table 1 fixed
| Attribute | Type | Required | Description |
|---|---|---|---|
| queues | list | false |
IDs of queues where the duplicate detection should be performed. You can assign the extension to multiple queues and specify numerous actions for different queues in one instance. If not present, the duplicate detection will be performed on all the queues to which the extension is assigned unless `excluded_queues` is set. |
| excluded_queues | list | false | IDs of queues where the duplicate detection won't be performed. This parameter cannot be set along with the `queue_ids`. |
| trigger_events | list | false |
List of Rossum events that trigger this configuration. Corresponds to selected hook events. If not specified, the duplicate detection will be performed for all allowed `trigger_events`. Possible values: - `annotation_status` - `annotation_content` |
| trigger_actions | list | false |
List of Rossum actions that trigger this configuration. Corresponds to selected hook actions. If not specified, the duplicate detection will be performed for all actions relevant for a selected `trigger_event`. Possible values: - `changed` - `initialize` - `updated` - `started` - `confirm` - `export` - `user_update` |
| statuses | list | false |
List of annotation status-couples in the format `\{previous status\}.\{current status\}` or `\{previous status\}->\{current status\}` defining when the processing of logic should start. If not present, duplicate detection will be performed for all allowed status changes. |
| logic | list | true | List of logic objects. More details are in the section below. |
Updated 12 months ago
