... | ... | @@ -93,22 +93,20 @@ The records management service application will write files in a usual temporary |
|
|
Calling Datovka with `--compose` option will:
|
|
|
1. When Datovka is already running then all required data are passed to the main Datovka process.
|
|
|
|
|
|
1a. The invoked Datovka process will check the supplied arguments for basic sanity and if no errors (e.g. unknown arguments) are detected then all data are going to be passed to the already running Datovka process. The main process will collect the data and notify the user about any potential error (e.g. non-existent file). The command with `--compose` will terminate before actual sending of the data message.
|
|
|
1a. The invoked Datovka process checks the supplied arguments for basic sanity and if no errors (e.g. unknown arguments) ha been detected then all data are going to be passed to the already running Datovka process. The invoked process exist successfully if no errors have been detected. The invoked Datovka process terminates before the actual sending of the message.
|
|
|
|
|
|
2. The command with `--dlg-send-msg` will start the Datovka application when it has not been running. In this case it is perhaps better to create a new main process and pass the data in a same way as in the first case. This will allow the user to lave Datovka running after the message has been sent instead of terminating the whole application.
|
|
|
1b. The main process will collect the data and notify the user about any potential error (e.g. non-existent file). A pre-filled send message dialogue window is presented to the user.
|
|
|
|
|
|
**Question for Singlecase:** Would you prefer a blocking send message operation in GUI? This means that the application in the second case would block the command line `--dlg-send-msg` command until the message has been sent and the invoked Datovka process has been terminated.
|
|
|
2. The command with `--compose` option will start the Datovka application when it has not been running. The started process does not create a separate child process to detach from the calling environment. It is left to the calling environment to detach the newly created process. The calling environment must assure that the Datovka process is left running in order to let the user to finish the sending operation.
|
|
|
|
|
|
### Handling Return Status
|
|
|
2a. After Datovka starts, the supplied parameters are checked for basis sanity. If errors are detected the the application exists with an error.
|
|
|
|
|
|
Datovka will only return a status whether a new message dialogue was successfully created to the calling application. The calling application should notify the user that all data have been passed to Datovka or whether an error occurred. On error occasion Datovka will generate a brief error description into standard error output.
|
|
|
2b. After the application GUI starts the send message dialogue is presented to the user. The user may be warned about any potential error (e.g. non-existent file).
|
|
|
|
|
|
### Passing Sent Data Message into the Records Management Service
|
|
|
|
|
|
The user is going to be provided with an option to upload the created data message back into the document service.
|
|
|
2c. The application does not terminate by itself when the send message dialogue is confirmed by the user and the message has been sent.
|
|
|
|
|
|
In such case the sent data message is needed to be downloaded immediately after it has been successfully sent. This is because we need to obtain a ZFO with necessary timestamps.
|
|
|
### Passing Sent Data Message into the Records Management Service
|
|
|
|
|
|
This would generate additional traffic of downloading data back from ISDS and then sending them to the records management service. (We may also be able to download the delivery info ZFO but this will most likely contain only delivery data and no acceptance times because the delivery info is going to be downloaded immediately after the message has been created in the ISDS.)
|
|
|
The user is provided with an option to upload the created data message back into the document service.
|
|
|
|
|
|
The user will be before sending the message notified about this conditions and after confirming the dialogue he will be asked for the location of the newly created data message. After selecting the location all operation will proceed. |
|
|
\ No newline at end of file |
|
|
In such case the sent data message is needed to be downloaded immediately after it has been successfully sent. This is because we need to obtain a ZFO with necessary timestamps. |
|
|
\ No newline at end of file |