Datovka issueshttps://gitlab.nic.cz/datovka/datovka/-/issues2017-07-21T14:40:32+02:00https://gitlab.nic.cz/datovka/datovka/-/issues/305Records Management Service Logo not Shown2017-07-21T14:40:32+02:00Karel SlanýRecords Management Service Logo not ShownSteps to reproduce:
0. Ensure that the connection to records management is disabled and restart the application.
1. Set the connection to records management service.
2. Observe that records management column width in message view if not...Steps to reproduce:
0. Ensure that the connection to records management is disabled and restart the application.
1. Set the connection to records management service.
2. Observe that records management column width in message view if not set properly.
3. Call update records management information action.
4. Observe that the model does not use the downloaded service logo.4.9.1Karel SlanýKarel Slanýhttps://gitlab.nic.cz/datovka/datovka/-/issues/306Message Model not Erasing Record Management Data2017-07-21T14:40:26+02:00Karel SlanýMessage Model not Erasing Record Management DataSteps to reproduce:
1. Ensure that the connection to records management is enabled and some messages have been uploaded to the service.
2. Disable the records management service.
3. Re-enable the service.
4. Observe that the model shows...Steps to reproduce:
1. Ensure that the connection to records management is enabled and some messages have been uploaded to the service.
2. Disable the records management service.
3. Re-enable the service.
4. Observe that the model shows old data even though the records management database has been erased.4.9.1Karel SlanýKarel Slanýhttps://gitlab.nic.cz/datovka/datovka/-/issues/301HTML tags are shown in account info2017-07-20T11:06:37+02:00Martin StrakaHTML tags are shown in account infoHTML tags are shown in the account info. In section privileges when user has restricted privileges. Example below:
Oprávnění:
````
Omezený přístup<li>- stahovat a číst došlé DZ</li><li>- stahovat a číst DZ určené do vlastních rukou</li...HTML tags are shown in the account info. In section privileges when user has restricted privileges. Example below:
Oprávnění:
````
Omezený přístup<li>- stahovat a číst došlé DZ</li><li>- stahovat a číst DZ určené do vlastních rukou</li><li>- vytvářet a odesílat DZ, stahovat odeslané DZ</li><li>- načítat seznamy DZ, dodejky a doručenky</li><li>- vyhledávat DS</li>
````4.9.1Karel SlanýKarel Slanýhttps://gitlab.nic.cz/datovka/datovka/-/issues/296Records management API: Filtering in the hierarchy doesn't return subnodes of...2017-07-18T16:17:11+02:00PavelRecords management API: Filtering in the hierarchy doesn't return subnodes of the found nodeWhen filtering the nodes (see upload_hierarchy in https://gitlab.labs.nic.cz/labs/qdatovka/wikis/records-management-api) in order to send data message to an external service, the filtering does not work as expected.
Problem is, user gen...When filtering the nodes (see upload_hierarchy in https://gitlab.labs.nic.cz/labs/qdatovka/wikis/records-management-api) in order to send data message to an external service, the filtering does not work as expected.
Problem is, user generally knows the name of a **node**, but wants to attach the message to a **subnode**. When filtering using name of node, the app is not returning the subnodes of the found node (just the node itself).
--
Example: there is a client (i.e. node) named **Iva Fišerová** with records (i.e. subnodes) named **Právní poradenství**, **Spor o 400.000,- s Alenou Holaňovou etc.**. Client is searching using the name of the client (Česká pojištovna), but then expects the app to show him all the subnodes (records where he can actually upload data messaged.
![Snímek_obrazovky_2017-07-07_v_16.07.25](/uploads/69ebfd8bf8569e490f0b218996aeecb6/Snímek_obrazovky_2017-07-07_v_16.07.25.png)
![Snímek_obrazovky_2017-07-07_v_16.07.13](/uploads/45767ccf778109cfd424b5496b2ee621/Snímek_obrazovky_2017-07-07_v_16.07.13.png)
In the example below, when searching for Prvni Klient, I should get all Prvni klient, Prvni spis, Druhy spis nodes. I am now getting just Prvni Klient.
`
{ "name": null, "id": null, "metadata": [], "sub":
[
{ "name": "Prvni Klient", "id": null, "metadata": ["jednicka", "12582"], "sub":
[
{ "name": "Prvni spis", "id": "af51ef52yx", "metadata": ["jednicka", "v supliku"], "sub": [] },
{ "name": "Druhy spis", "id": "af51ef52yz", "metadata": ["jednicka", "taky v supliku"], "sub": [] }
]
},
{ "name": "Druhy Klient", "id": null, "metadata": ["jednicka", "12582"], "sub":
[
{ "name": "Dalsi spis", "id": "aabbccddee", "metadata": [], "sub": [] }
]
}
]
}
`4.9.1Karel SlanýKarel Slanýhttps://gitlab.nic.cz/datovka/datovka/-/issues/297Records management API: subnodes are not sorted alphabetically2017-07-18T16:16:58+02:00PavelRecords management API: subnodes are not sorted alphabeticallyWhen filtering among nodes, on the first level (or level zero), the nodes are sorted alphabetically.
On the second level (subnode level), they are not sorted.
IMHO they should be sorted as well as the API does not give any option to sor...When filtering among nodes, on the first level (or level zero), the nodes are sorted alphabetically.
On the second level (subnode level), they are not sorted.
IMHO they should be sorted as well as the API does not give any option to sort it on our side (the same way as they are on the first level)
![Snímek_obrazovky_2017-07-07_v_16.12.17](/uploads/cec787205161f644a5c9d8e34e06198e/Snímek_obrazovky_2017-07-07_v_16.12.17.png)
*First level is okay*
![Snímek_obrazovky_2017-07-07_v_16.07.25](/uploads/afff1cb0f5b6a9ba9ce4cb2ea13e331a/Snímek_obrazovky_2017-07-07_v_16.07.25.png)
*Second level is unsorted*4.9.1Karel SlanýKarel Slanýhttps://gitlab.nic.cz/datovka/datovka/-/issues/298Adapt to Modifications in ISDS Interface2017-07-17T14:57:48+02:00Karel SlanýAdapt to Modifications in ISDS InterfaceChanges to ISDS interface [are scheduled][].
Modifications to libisds have already been uploaded to upstream and libisds-0.10.7 has already been released.
Make modifications to Datovka sources to accommodate the changes:
* [x] Update ...Changes to ISDS interface [are scheduled][].
Modifications to libisds have already been uploaded to upstream and libisds-0.10.7 has already been released.
Make modifications to Datovka sources to accommodate the changes:
* [x] Update library building scripts.
* [x] Add conversion code to newly added types.
[are scheduled]: https://www.datoveschranky.info/-/zmeny-v-aplikacnim-rozhrani-isds4.9.1Karel SlanýKarel Slanýhttps://gitlab.nic.cz/datovka/datovka/-/issues/299Windows build script redesign2017-07-13T16:22:20+02:00Martin StrakaWindows build script redesignWindows build script redesign.Windows build script redesign.4.9.1Martin StrakaMartin Straka