The table below summarises the properties (fields) available in the document and event indexes. Both indexes use properties from the associated worker and therefore share many of the same properties.
| Property | Document | Event |
| process_type_reference | • | • |
| process_type_name | • | • |
| owner_id | • | • |
| owner_name | • | • |
| worker_role | • | • |
| group_name | • | • |
| group_path | • | • |
| connection_name | • | • |
| connection_path | • | • |
| document_type_reference | • | |
| document_type_name | • | |
| document_received_timestamp | • | |
| document_date | • | |
| document_valid_from_date | • | |
| document_valid_to_date | • | |
| document_status_reference | • | |
| document_status_name | • | |
| document_key | • | |
| document_tag | • | |
| event_timestamp | • | |
| user_id | • | |
| user_name | • | |
| event_type_reference | • | |
| event_type_name | • | |
| status_reference | • | |
| status_name | • |
The properties are as in the original document and event messages, with associated workers.
document_tag is a break down of the document tags string, which is either a blank-delimited list of tokens or a JSON string.
As well as holding the full document key, the document key is broken down into each part. So "supplier/123456/nda" will be indexed as:
- "supplier/*"
- "supplier/123456/*"
- "supplier/123456/nda"
Group path is broken down in the same way.