Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 34 Next »

Valid from TO BE UPDATED 2024

(warning) Always check: Breaking Changes / Deprecated Features 10.x

yuuvis® RAD core-service

The following features reduce administration efforts:

  • The REST-WS endpoint ./dms/{id}/children can be requested with nullvalues=true to get such properties in the answer as well. (internal: TUK-5709)

  • The REST-WS endpoint ../result/query provides the wildcard search for text-based parameters. (internal: TUK-5150)

  • The core-service setup asks for the license key to connect the License-Management-Service and whether metrics should be sent. Currently, these values can be entered in the ‘Systems’ view of the management-studio. (internal: TUK-5785)

yuuvis® RAD services

This update keeps the system future-proof:

The following features reduce administration effort:

  • 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 lists:

  • 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)

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 9.-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 UBL-XRechnung tags to the existing extraction tags beginning with FERD:. This allows the configuration of a single mapping in the designer that handles all three different e-invoice formats.

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)

  • 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)

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

  • The auto-complete field resolves the placeholders {clientlocale} and {schemalocale}which can be used for particular parameter values in the configured URL, e. g. (internal: TUK-5610):

    autocomplete/mycatalog?description=mydescr_{clientlocale}&myparam={schemalocale}

  • It is possible to configure in the extend.json file of the client to offer only object actions that can export a document file, like downloading it or sending it via email with attachments for users with a specific role. Without this configuration, all users are provided with these features which is the default. (internal: TUK-4525)
    Example configuration:

    { 
  "requiredRolesExport": ["myrole1", "myrole2"]
}

yuuvis® RAD management-studio

The following features increase the user productivity:

  • The user attribute salutation could be imported via ad-sync and written via API. This attribute can be maintained in the field 'Salutation'/'Anrede' of the create and edit form in the organization state. (internal: TUK-5597)

  • No labels