Changelog 9.16 (LTS)

As a developer, I would like to use consistent API in order to work more efficiently.

All but four of endpoints in BpmProcessService use the path in form of /process/{processId}/activity/{activityId}, but four endpoints omit "activity". This should be changed to make the whole API more consistent.

Acceptance criteria:

• The following endpoints of in BpmProcessService should be consistent with other endpoints in service
  • GET /process/{processId}/{activityId} > GET /process/{processId}/activity/{activityId}/inboxitem
  • PUT /process/{processId}/{activityId}/lock > PUT /process/{processId}/activity/{activityId}/inboxitem/lock
  • DELETE /process/{processId}/{activityId}/lock > DELETE /process/{processId}/activity/{activityId}/inboxitem/lock
  • POST /process/{processId}/{activityId}/save > POST /process/{processId}/activity/{activityId}/inboxitem/save
• Existing endpoints remain functional, new endpoints are added
• Existing endpoints are marked as deprecated in release notes

As an administrator, I would like to control who can create and delete model groups in a yuuvis RAD system.

Acceptance criteria:

• The following endpoint inside BpmManagementService should be accessible only to users with privilege 'MANAGE_MODELS':
  • POST bpm/management/project (create model group)
  • POST bpm/management/project/<projectId>/subproject (create model group within model group)
  • DELETE bpm/management/project/<projectId> (delete model group)

As a modeler, I would like to be informed if a catalog in schema contains duplicate data values, in order to avoid ambiguity that can occur on client side. For instance, client-side scripts cannot differentiate between multiple entries that contain the same data value, resulting in a possibly erroneous execution.

Acceptance criteria:

• Validation issues a warning if a catalog contains duplicate data value
• The warning contains name of catalog and unique names of all data duplicates present in the catalog 

As a user, I want to be able to save my current locally saved settings centrally so that I can use them on another workstation as well.

Many users are working on virtual sessions that are always reset overnight so the users are losing their local settings.

Acceptance criteria:

• In the settings
  • the topic 'Local settings' with the buttons 'Save to system' and 'Load from system'.
  • After clicking 'Save to system' all locally saved settings are saved in the user service.
  • After clicking 'Load from system' the settings are read from the user service and are saved locally.
  • If no local settings are available the existing ones are always loaded from the user service and saved locally?
  • The settings are saved in a separate section for the user.

As a user, I want to be able to change the just new selected object type for a bundle of files in the in-tray so that I can correct my wrong selection.

Acceptance criteria:

• In the dialog that is opened after the object type selection a button 'Reset object type'/'Objektyp zurücksetzen' is offered in the dialog with the form.
• After pushing this button the rest endpoint ../prepare/id/dms:sysobject is called to reset the object type for this prepare object and the former dialog is opened again and a different object type can be selected.

As a user, I want to be able to configure a chart for a property of type datetime that shows the number of objects per day, week, month, or year, or as given in the standard so that I get a necessary overview for trends.

Acceptance criteria:

• The search API offers a new attribute 'histogram' that can be set to day, week, month, and year.
• For a property of type datetime the configuration form of the chart widget offers a new field 'Histogram'/'Histogram' with a selection list showing 'Standard', 'Day'/'Tag', 'Week'/Woch', 'Month'/'Monat', 'Year'/'Jahr', default is standard. A description is given: 'Determine the interval for the partial values.'/'Legen Sie das Intervall für die Teilwerte fest.'
• Depending on the selection the search API is called for aggregation with the selected histogram and the corresponding buckets are shown on the x-axis days:
  • for standard show the current buckets
  • for days show the labels in the format that comes from Elasticsearch: yyyy-MM-dd
  • for weeks show the labels in the format that comes from Elasticsearch: yyyy-ww
  • for months show the labels in the format that comes from Elasticsearch: yyyy-MM
  • for years show the labels in the format that comes from Elasticsearch: yyyy

As a user, I want to be able to upload data from a CSV file that I got as an export from an external data source and import its data into the form table so that I don't have to enter it manually.

Acceptance criteria:

• Prerequisites:
  • The column separator in the CSV file has to be the semicolon ';'.
  • The sequence of the columns must be the same as in the schema, which means that their types must match.
    • The column names can differ. 
    • The CSV file can have more or less columns than are in the table. 
  • The decimal separator must be that of the set definition language.
  • The catalog value must be in the set definition language.
  • In the case of an organization field, the user name must be the login name.
  • A date must be in the ISO format for example the 1st of December 2023 -> 2023-12-01.
  • An id-reference must be 32 characters long.
• There is an icon for uploading a file.
  • A tooltip shows 'Imports table data from a CSV file'/'Importiert Tabellendaten aus einer CSV-Datei'.
  • The dialog shows only files in the CSV-format.
  • If more than 5.000 rows are contained an error message is given:
    EN: "The import is not possible because the file contains more than the allowed 5.000 rows.
    DE: "Der Import ist nicht möglich, da die Datei mehr als 5.000 Zeilen enthält."
• If this is clicked a dialog for selecting a CSV file is opened. One file can be applied.
• The rows read are appended. Data from a column is copied to a column in the same sequence.
  • All field types are supported, and special validations are given as described below. 
    • integer only allows digits
    • decimals need to be formatted in the definition language that is set for the user of the client
    • date and datetime must be in ISO format, for example, September 27, 2022 at 6 p.m. is represented as 2022-09-27 18:00:00.000
    • catalog values must be in the definition language that is set for the user of the client
    • reference values must contain 32 characters
    • organization: login name of a user or the name of an organization is accepted.
• After the import the following is reported:
  • The number of rows that were added. Cells that could not be imported are listed:
    EN: 'Incorrect values which cannot be imported:'
    DE: 'Inkorrekte Werte, die nicht importiert werden können:'
  • Row number, CSV column name, table column name, and the incorrect value that is not taken over.
• The table shows the imported values and the form offers the save.
  • The table data can be edited.
• The data can be saved.

As the system-responsible, I want the messaging-service to be updated to Spring Bott 3.1.5 to keep the service infrastructure future-proofed.

Acceptance criteria:

• The following dependency is set for the messaging service and with this, the service works as before.

<!-- https://mvnrepository.com/artifact/org.apache.activemq/activemq-broker -->
<dependency>
    <groupId>org.apache.activemq</groupId>
    <artifactId>activemq-broker</artifactId>
    <version>6.0.0</version>
</dependency>

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.

Acceptance criteria:

• Tukan-Team
  • index-service, CAMEL
  • search-service, CAMEL
  • OCR-service, CAMEL
  • extraction-service, CAMEL
  • message-service (waiting for updates here)

As an administrator, I want to be supported by a custom application list in the service-manager that let me see the uptime if a service again and offers me to directly restart a service.

Reason: Breaking change in Spring Boot 3.0.x where the uptime is no longer shown in the list 'Applications' but only on the wallboard.

Acceptance criteria:

• In the appbar of service-manager interface there is a new button 'Uptime list) that offers the uptime in the application list as well as the restart icon.

As a user, I want to be able to determine the partial values of my charts so that I can differ from the default of 10 if necessary.

Acceptance criteria:

• In the hitlist and char configuration there is the field 'Parts'/'Teil' with the description 'Determine the maximum number of partial values for the chart'/'Legen sie die maximale Anzahl Teilwerte des Diagramms fest'. The default is 10, also if no value is entered, the minimum is 3, the maximum is 20, in case of an error this info is shown:
  EN: "Enter a valid number between 3 and 20"
  DE: "Geben sie eine valide Anzahl zwischen 3 und 20 ein"
• The value of this field is used for the parameter "size" in the aggregation request

As a programmer, I want the search-service API aggregation buckets for codesystems to return the localized value instead of the technical value as it is supported by the core-system API so that the users will see the labels in their language.

Acceptance criteria:

• The reported aggregation bucket-keys for codesystem keys and 'types' are in the language of the requesting user.
  • The charts in the client are showing the localized labels for the selected codesystem (catalog) property and the 'Type'.

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.

Acceptance criteria:

• Tukan-Team
  • search-service, CAMEL
  • extraction-service, CAMEL