Valid from

...

• The search-service API can be requested to return the technical catalog entry id or data. (internal: TUK-5711)

• The signing-service sends admin emails with the affected objectId and a URL for opening it in the client. (internal: TUK-5577)

• It is possible to activate the used context path for specific gateways so that services not supporting the context path can use a gateway without the activated context path. With this feature, the configuration of the context path in the extend.json file of the client is no longer necessary. (internal: TUK-5873)

  • The parameter server.servlet.context-path must no longer be configured in the application-prod.yml. For each configured gateway, the gateway-service sets the new request header x-os-context-path with the server.servlet.context-path value read from the file gateway-<profile>.yml. (internal: TUK-5897)

This feature supports users in optimized handling of objects listed in the CSV export of their hit listsThese features increase the productivity of the users:

• The search API provides the CSV export with a column with the URL to the document if the request parameter withurl=true is set. The default is false without this column. (internal: TUK-2723)
  The export with URL can be requested by a user for his current hit list.

• The structure service supports conditions for tables. These leads also resolve the references given in table cells so that more objects will be listed in the object details aspect References.

This feature supports the extraction of data from all e-invoice formats allowed in Germany beginning with the mandatory electronic interchange on the 1st of January 2025:

• The extraction-service also supports e-invoices based on the new ZUGFeRD version 2.3 and Factur-X 1.0.07. (internal: TUK-5900)
  Info on FERD

• The extraction-service supports e-invoice files of format XRechnung 3.0.1 in the syntax UBL 2.1 (internal: TUK-4100)
  This is the third step in supporting e-invoices. The extraction from ZUGFeRD formatted e-invoices is supported since yuuvis® RAD version 98.-16 LTS, from Factur-X 1.0.06 and XRechnung 3.0.2 with Syntac CII (UN/CEFACT) since yuuvis® RAD version 10.4.
  An additional configurable mapping file is introduced that maps the new The most useful UBL-XRechnung tags attributes are mapped to the existing extraction tags attributes beginning with FERD:.
  An additional configurable mapping file invoicemapping.lst for invoices can be provided. This allows the configuration of still missing attributes of the e-invoice files. The attributes in this custom file overwrite the attributes of the standard configuration.
  The new endpoint ../extraction/api/info/mapping list the current mapping configuration of a single mapping in the designer that handles all three different e-invoice formats.including the configuration of the invoicemapping.lst. This helps to check the completeness of the possible attribute which can be used for mapping the corresponding values to object properties in the designer.

• The extraction-service supports the extraction of table data in XML files. The row number beginning with [0] is added to the table column attribute. The standard mapping for invoices of the Format ZUGFeRD, Facut-X, and XRechnung is extended with the most useful columns. Others can be added to the configuration file invoicemapping.lst mentioned before. (internal: TUK-5976)

This feature supports administrators in setting up the repository-manager service:

• The rmalink-service can connect to an SAP instance by automatic certificate activation or without using any certificate. Manual activation of certificates is the default behavior. (internal: SAP-2934)
  Active SAP certificates can be deactivated through the Swagger endpoint. (internal SAP-2941)
  We strongly recommend the use of certificates for security reasons.

yuuvis® RAD client

The following features increase the user productivity:

• The search form field of the types user/group, dynamic-list and auto-complete provides the following operators (internal: TUK-5594):

  • = (equal) for the known search to find objects containing the entered term

  • ≠ (not equal) to find objects not containing the entered term

  • Out of scope: Searching in tables. This will be implemented in a future version.

• The user is asked whether to export the CSV data of the hit list with the URL to the object. (internal: TUK-2723)

• The CSV import for object table data recognizes the column separator to be used. (internal: TUK-6001)
  Before this optimization only the separator ; was used.

• In the Inbox filter, the model selection dialog offers a flat and sorted list instead of a tree. This leads to less mouse and keyboard use. (internal: TUK-5698)

  Additionally, the technical name of a model is shown in brackets below the localized one. This can help to differentiate models with the same localized name.

• The primary button of a just-opened security dialog is always focused and the focus keeps in the dialog when pushing the tab keys. (internal: TUK-5839)

• In the structure tree section, references are only nodes shown when objects for them are available. If no object is available the complete section isn’t offered.

The following features extend the catalog features and match specific data export compliance policies:

...