... | ... | @@ -105,6 +105,18 @@ could be interpreted in the following manner: |
|
|
+- "Dalsi spis" [ Has an id. No additional data for filtering are provided. Only the name is used for filtering. ]
|
|
|
```
|
|
|
|
|
|
> Datovka 4.13.0 introduces a new optional function. The user is free to choose whether to automatically upload newly downloaded messages into the records management service. In such case the following sequence of actions is triggered:
|
|
|
|
|
|
1. The user invokes the Synchronise Account/Synchronise All Accounts/Download Message Content action.
|
|
|
2. After successful synchronisation (message download), Datovka sends the a [Request for Storage Hierarchy](https://gitlab.labs.nic.cz/datovka/datovka/wikis/records-management-api#request-for-storage-hierarchy-upload_hierarchy).
|
|
|
3. The record management server sends a response containing the requested hierarchy. Additional data containing case identifiers ('jednací čísla', 'spisové značky' in Czech) are sent inside the hierarchy.
|
|
|
* The response contains the following optional entries:
|
|
|
* `case_id` - contains a list of strings. The list may be empty or it must contain only non-empty strings. All entries within this list must be unique - no string is allowed to be repeated in this list. Every string represents a single case identifier as **used by the user** of the records management service.
|
|
|
* `court_case_id` - contains a list of strings. The list may be empty or it must contain only non-empty strings. All entries within this list must be unique - no string is allowed to be repeated in this list. Every string represents a single case identifier as **used by the opposite party**.
|
|
|
4. Datovka scans the obtained hierarchy for case identifiers. If Datovka finds an unambiguous corresponding case identifier in the newly downloaded messages then the corresponding data messages are uploaded into the document service via [upload_file](https://gitlab.labs.nic.cz/datovka/datovka/wikis/records-management-api#upload-a-zfo-file-into-the-storage-upload_file).
|
|
|
* If there is only one hierarchy entry containing a `case_id` which holds a file mark that matches **our case identifier** (`dmRecipientRefNumber` or `dmRecipientIdent`) of the newly received message then this message is going to be automatically uploaded into the records management service. (I.e. the respective case identifier must be uniquely associated to a single hierarchy entry, but this hierarchy entry may contain multiple file marks.)
|
|
|
* If there is only one hierarchy entry containing a `court_case_id` which holds a file mark that **your case identifier** (`dmSenderRefNumber` or `dmSenderIdent`) of the newly received message then this message is going to be automatically uploaded into the records management service. (I.e. the respective file mark must be uniquely associated to a single hierarchy entry, but this hierarchy entry may contain multiple file marks.)
|
|
|
|
|
|
### Upload a ZFO File into the Storage (`upload_file`)
|
|
|
|
|
|
Uploads a given (ZFO) file into a given place in the storage hierarchy. A JSON document is sent via a POST request. The JSON document from the response contain the id of the stored file, description where the ZFO file is stored (i.e. all locations) or an error description.
|
... | ... | |