Key | Subject | Description |
---|
TUK-3268 | It is possible to configure a 'Hit list' widget and place it on a dashboard | As a user, I want to be able to configure a widget that shows a specific hit list or its number on my selected workspace so that I get the information every time when I open my workspace. Acceptance criteria: - There is an item 'Hit list or hit count'/'Trefferliste oder Trefferanzahl' in the widget selection list. A click on this item opens a dialog where the following can be configured:
- A saved search can be selected. After the selection the next configuration is possible. Unless no search is selected
- the information 'Select a saved search.'/'Wählen sie eine gespeicherte Suche aus.' is shown in the preview area
- the widget can not be saved.
- The title of the selection dialog is 'Object property selection for sort by'/'Auswahl der Objekteigenschaft für die Sortierung'
- In this case of a folder, the file properties are not shown.
- The properties are listed alphanumerically.
- The name of the saved search is shown in the header of the widget. As long as no saved search is selected this header does not show a text.
- It is possible to decide whether to show the hit list or the hit count.
- The corresponding hit list is shown for the hit list mode
- It is possible to configure the number of objects that should be listed.
- It is possible to configure the property for sorting and whether it should be sorted ascending or descending.
- The used widget on the dashboard offers
- to open the search in the result list state
- to refresh the list.
- The widget can be re-opened for editing.
- In the case of 'Show only total amount' the number is shown in the preview area.
|
TUK-3270 | The service infrastructure is based on Spring Boot 3.1.3 | As the system responsible, I want the microservice infrastructure to be based on Spring Boot 3.0.x so that we get support during the next 12 months |
TUK-3302 | The request signatures dialog is optimized | As a user, I want to be able sign a document file advanced and qualified as well if this capability is enabled in the DocuSign account of my company. As a user, I want to be supported by a better user experience when I have requested signatures so that I better understand the way to enter data. Acceptance criteria: - For entering the list of signers the corresponding list component of the yuuvis components library is used:
- Instead of a form table an individual form control is offered that supports to add signers to list, delete one, or edit one.
- A checkbox is offered with the label:
EN: 'Sign in parallel' DE: 'Parallel signieren' Default is unchecked for sequentially, the selected value is remembered locally.- If in parallel all signers get the signing order 1 otherwise the number 1 to n in the sequence given in the dialog.
- The email subject and message are offered at the bottom
|
TUK-3487 | The agent-, client-, and signing-services are based on Spring Boot 3.1.3 | As the system responsible, I want all microservices to be based on Spring Boot 3.1.3 and CAMEL 4.0.0 so that we get support during the next 12 months |