Valid from 30 APR 2024

Always check: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/697368905

yuuvis® core-service

License Management

• After the installation or an update from version 9, a named license is assigned to the user 'root'. This license cannot be removed (internal: TUK-3665).

• The core-service generates a GUID for the environment when starting up the first time and creates the initial license file based on it. This license is of type PROVISIONAL with 5 concurrent users and an expiration date set to 1 month later. (internal: TUK-3662, TUK-3662)
  A system which is updated from version 9.x or earlier will contain a PROVISIONAL_UPDATE license (1000 concurrent users, 1 named user for root user, max. 200 object types, expiration date one month) which has to be exchanged with a PRODUCTION or TEST license.

• When the updated core-service starts, a new license file can be read, validated, and activated. This license file can be requested by OPTIMAL SYSTEMS days before the update by handing over the cluster ID of the system which can be found in the REST-WS interface in the Monitoring view System info. (internal: TUK-4105)

• An OS-internal tool with a CLI (command line interface) supports the creation of license files that are based on the initial license and the necessary parameters. A business process will be introduced for delivering requested license files. (internal: TUK-3663)

  • Three types of licenses are handled:

    • PROVISIONAL: This is a trial license for 1 month, 5 concurrent users ,1 named user (= root user), maximum of 5 object types.

    • PRODUCTION: This license is for productive use, has an expiration date in case of a subscription, and differentiates concurrent and named users.

    • TEST: This license is for test and demonstration use and has an expiration date that allows the use for one year.

    • After reaching the given expiration date, the system can be used for another 3 days. During this time, objects can be searched for and the document files can be downloaded but no new objects can be created or existing ones edited.

  • Later in time, a web portal will be available for the interaction between the requester and OS and if possible between an installed environment and the web portal.

• A new License menu item is added to the Monitor menu in the REST-WS interface where an administrator can download the saved license file, upload and activate a new one, and see current license details like (internal: TUK-3666):

  • the amount of available named and concurred licenses

  • how many concurrent licenses are currently in use

  • the expiration and grant date: when the expiration date is reached the users can search for documents and download the file but can't create new objects or update existing once until the grant date is reached

  • whether it is a PRODUCTION, TEST; or PROVISIONAL license

Click image to enlarge

Open

Type of license

• It is possible to compare the parameters of a new license file with the current one before activating it in the REST-WS interface. (internal: TUK-4256)

Click image to enlarge

Open

Comparing license parameters

• If a new license has a lower number of named users than currently assigned, it cannot be activated. (internal: TUK-4637)

• New REST endpoints are available with a Swagger UI that shows the license data as well and allows to download the saved license file and upload a new one.

Click image to enlarge

Open

License Service in Swagger UI

• A new REST-WS PUT endpoint ../organization/update/{userid}/named?state=true is available. It allows to change the status of the named license for the specified user. If the status is set to true and the amount of named licenses given in the license file is exceeded, an error is responded and the status is not changed. (internal: TUK-3665)

• The Sessions monitoring view of the REST-WS interface shows information about the active concurrent users. (internal: TUK-4092)

• In the license view of the REST-WS interface, it is possible to initiate a check for a new license against the License-Management-Service and to stage it. (internal: TUK-4268)

• It is possible to get a report about the revised logins for concurrent users who could not log in because no more licenses were available. (internal: TUK-4108)

• The core-service checks a login whether a concurrent user license is available and responds with an error if not.

• After having reached the expiration date, all users can log in for an additional 3 days, but cannot create objects or edit existing ones. Objects can be retrieved or downloaded. Only the root user can still log in. (internal: TUK-3672)

• It is possible to get a list of users with an assigned named license via the REST endpoint GET ../organization/query by using the new parameter namedlicense = true.  (internal: TUK-4098)

• Admin e-mails are sent in the last 30 days before the license expires at the interval defined in the scheduled task "System event information" in Management Studio.

Miscellaneous

• The new object right Share is introduced, so that the object action Share in the client is differentiated from the former coupled right Edit. After the system update, the roles have mapped the Edit right to the Share right. If you want users not to be allowed to share via the object action you have to adapt their relevant roles. (internal: ERA-9530)

yuuvis® services

License Management

• The login page of the gateway-service informs a concurrent user if login is not possible because no more licenses are available. (internal: TUK-3670)

O365 Integration

• Two new services are installed with the service-manager setup:

  • A dashlet-service offers the viewer component that is shown in the client.

  • The o365 service is the interface to the cloud-based OS service that transfers Microsoft Office to its O365 platform for editing.

Miscellaneous

• All services are updated to Spring Boot 3.2.3 to be future-proof.  (internal: TUK-4155, TUK-4375)

• After installation of the service-manager, the OCR service starts up using Tesseract. It is possible to configure that Abbyy Finereader is used instead of Tesseract. The trained languages which are supported after installation by default are the same that can be configured for Elasticsearch (see the packages for Europe & USA as well as for Asia).  (internal: TUK-3809)

• During the service-manager installation, the IP-whitelist is configured in the application-prod.yml instead of the dms-prod.yml, so it affects all services. (internal: TUK-2357)

• The search API supports metrics in sub-aggregations. How to do this and how the results look like can be read here: Useofsub-aggregationcombinedwithmetrics . (internal: TUK-3710)

yuuvis® RAD designer

License Management

• If the designer needs a connection to the backend a user account should be used with a named license to avoid login issues. If a connection is established and no further license is available no login is granted.

Miscellaneous

• In the roles section, an additional object-type right Share is introduced that provides control over who can share documents in a system. In version 9, the object action Share was offered to users with the right Edit. (internal: ERA-9530).

Click image to enlarge

Open

Share role

yuuvis® RAD client

License Management

• If a user without an assigned named license logs in and all concurrent licenses are in use, the user is getting a notice and will not be able to open the client. (internal: TUK-3668)

• The client shows a notification if a PROVISIONAL or TEST license is used. If the license has an expiration date, a notification with this date is shown during the month the license expires. (internal: TUK-4030)

O365 Integration

• If a Microsoft Office file should be previewed, the new O365 Integration services are supporting the user. In the preview area, a dashlet is offering the rendition that is based on Microsoft Office sources.

• Users with edit permissions for the corresponding object are offered an edit action that opens a new browser tab with the file opened on the Microsoft O365 platform. More users can enter and work collaboratively on this file. If the last user is closing this O365 tab the file will be saved back as a new version for the object. The client will refresh the object details, so the preview will show that new version as well.

Dashboards and Widgets

• It is possible to reset the dashboard to default. (internal: TUK-4671)

• The Hit list or hit count widget is split into two widgets: Hit list and Hit count. (internal: TUK-3934)

• In the Hit list widget, it is possible to determine the properties to be shown as the first, second, and third label. (internal: TUK-3627)

• In the Chart widget, two new chart types Line - straight and Line - curve are offered for a Property for aggregation that is of type date or datetime.  These chart types connect the dots with straight or curved lines. (intern: TUK-3911)

• The Chart widget can be configured with a selected Attribute for aggregation of type decimal by specifying an Interval size like 100.0 and a Starting point like 10.0 to be shown. (internal: TUK-3695)

• The Recently edited and created objects widget can be configured and the results previewed. It can be decided whether to show only the recently edited or the recently created objects or both, the number of objects to be listed, and the sorting can be reverted. (internal: TUK-4284)

• It is possible to set up Chart widget legends for the x-and y-axes as well as for the chart. (internal: TUK-4404)

• When creating a Chart widget with an Attribute for aggregation of type number, appropriate Starting point, Interval, and Partial values are offered. (internal: TUK-4322)

• The Chart widget supports sub-aggregations for Attributes for metrics of type number. The following Metric can be selected: Average, Maximum, Minimum, Median, and Sum. (internal: TUK-4469)

• For a Chart widget, the order of the partial values can be reverted. (internal: TUK-4469)

• For a Chart widget, a threshold can be set to not show counts that have less objects. (internal: TUK-4500)

• In the Object count widget, it can be determined whether the number should be shown although it is 0. (internal: TUK-4446)

• The Task list widget is optimized regarding its look & feel and especially regarding the saving of its data. In version 9 that data was only stored in the local browser cache. So the data was not available on other workstations. The widget of version 10 saves data centrally now so that it is available on other workstations or browsers as well. However, when updating from version 9 to 10, the old data will get lost. (internal: TUK-4532)

• The Image widget is optimized regarding UX. (internal: TUK-4612)

Miscellaneous

• The Angular framework that is used has been upgraded from version 15 to 17, the 3rd party component ag-grid has been upgraded from version 22 to 31. (internal: TUK-4229)

• Beginning with this version, the object action Share is only offered to users if they have the new right Share. In version 9, this action was offered to users with the right Edit.  (internal: TUK-3243)

• In the hit list view, after saving the changed object metadata, the corresponding hit list row is updated. (internal: TUK-4044)

• In the search dialog, the order of the object groups can be changed by clicking on a forward or backward icon. This feature increases the productivity of the users who have many object groups and often have to scroll through the search dialog. (internal: TUK-3125)

• In the object details header, an icon indicates whether this object is part of an active process. (internal: TUK-3415, ERA-9583)

• The sorting for a form table as well as for the table in the edit dialog is remembered locally. (internal: TUK-2479)

• In the settings, the Cache part is removed and a Reset to default button is added to the part Local settings (internal: TUK-4399)

• Users can get specific information on how to fill a form field. This description can be changed via form script. (internal: TUK-4577)

• The responsiveness of the app bar is optimized. If the width of the browser gets smaller the symbols are vanishing: first, the license information, then the symbols near the profile image, and at the end the logo. (TUK-4769)

yuuvis® management-studio

License Management

• In the Organization view, the actions Assign named license and Remove named license are offered for a user who is not 'root'.

Click image to enlarge

Open

Assign named license

• If the given amount of named licenses is reached, assignment will not be possible (a notification is displayed).
  In the list of organization elements and in the header of the user details, a symbol is indicating an assigned named license. (internal: TUK-3665)

Click image to enlarge

Open

The certificate symbol indicates an assigned named license

• The operation License check supports continuous requests to the new cloud-based OPTIMAL SYSTEMS License-Management-Service. It queries whether a new license file is available for this system and informs you by email. This helps to shorten the process of adding a new license to the system, if allowed. (internal: TUK-4259)

• The new object right Share is shown in the table of object type rights within the user details. (internal: ERA-9530)

Valid from 28 May 2024

Always check: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/697368905

yuuvis® RAD client

• When creating a Chart widget with an Attribute for aggregation of type number, appropriate Starting point, Interval, and Partial values are offered. (internal: TUK-4322)

• For a line Chart, a number attribute can be selected for aggregation. (internal: TUK-4767)

• In the folder view, strg + left mouse click on a list item of Most recent changes or Latest edited opens it in a new browser tab. (internal: TUK-4826)

• The position of notifications is changed so they do not overlap the form buttons. (internal: TUK-3769)

yuuvis® RAD designer

• The new string property attribute Autocomplete allows the client to fetch catalog values from a custom microservice. This is an alternative to the string property with the attribute Dynamic list, which cannot be used for forms in some cases due to required client scripts.

yuuvis® RAD services

• Most of the services are updated to Spring Boot 3.2.5.

Data extraction of XRechnung files

• The extraction-service supports e-invoices of the format XRechnung version 3.0.1 in the syntax UN/CEFACT. (internal: TUK-3825)
  Remark: The syntax UBL will be supported with one of the next yuuvis RAD versions.
  XRechnung is compliant with the European Union standard EN 16931 and adds specific custom attributes for the exchange of e-invoices in Germany. For more information see the German FAQ platform:
  https://www.e-rechnung-bund.de/faq/xrechnung/
  The alternative to XRechnung is ZUGFeRD 2.2.0 which is supported by yuuvis RAD since version 9.0.

Hot Deployment

• The service-manager setup offers a hot deployment of the managed services. This means that if only the managed services have to be updated, it is no longer necessary to stop the service-manager first. So there is no real downtime in this case. The administrator is informed whether the service must be stopped or not. (internal: TUK-4643)

Valid from 25th June 2024

Always check: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/697368905

yuuvis® RAD client

• In the object aspect Summary, the context fields of the folder are shown. (internal: TUK-3494)

• The condition of the accordions in the object Summary is remembered. (internal: TUK-5005)

• In the Bar chart widget, the min and max values are shown in the chart if the 'Attribute of aggregation' is of type number. (internal: TUK-4453)

• For a Saved search, information in the deletion dialog is given if used in a widget. (internal: TUK-3447)

• A referenced object can always be edited in a folder view. (internal: TUK-5041)

• It is possible to localize the system and template metadata on the client-side. (internal: TUK-745)

yuuvis® RAD designer

• Project-Language setting is not copied along with other parts of the project. (internal: ERA-9818)

yuuvis® RAD management-studio

• A visual representation of a process model shows the status of process instance.

yuuvis® RAD services

• The client-service offers an endpoint for the new auto-complete form field that uses plugins that return the requested lists. (internal: TUK-4742)
  See the following documentation: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/829849601
  Outlook: Beginning with version 10.10, the client will request this endpoint for form fields of type string and a configured attribute 'URL for auto-complete service.

yuuvis® RAD core-service

• The root user always has a named license. It is not counted as part of the used named licenses. (internal: TUK-4968)

• The license file contains the orderid of the customer. (internal: TUK-4981)

• The performance of the core-service is improved because the type definition no longer uses the resource table. (internal: TUK-4453)

• The level of detail in a response of a process history query can be controlled with an additional parameter (internal: ERA-9934). Please see the breaking changes for further details.

• Reactivated users are removed from the inactive group after user-synchronization. (internal: ERA-9770)

Valid from 18th July 2024

Always check: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/697368905

yuuvis® RAD core-service

• The core-service setup asks for the license key needed for communication with the License-Management-Service. (internal: TUK-4638)

• If the core-service starts and the database cannot be connected, the service shuts down and the Windows service-manager indicates this status. (internal: UK-2243)

yuuvis® RAD services

• The search-service supports hit scoring for multi-value fields, too. (internal: TUK-5056)

• In the service-admin interface, the messaging-service status indicates the reach of the store limit size of the database in its Swagger-UI. (internal: TUK-5166)

• Once the service-manager has been installed, the web resources are referenced by the path variable enaio.data.path instead of the actual path in the servicewatcher-sw.yml file. (internal: TUK-4754)
  For the client, the new configuration looks like this:

  - name: client type: webresource path: ${enaio.data.path}\webresource\public\client\client.zip

yuuvis® RAD client

• The client is upgraded to Angular 18. (internal: TUK-5029)

• In the compare area of the version view, information about changed table data is given. (internal: TUK-5025)

• In the version view, the aspect ‘Signature' is shown if the abstract object type 'yuvsigning’ is part of the schema. (internal: TUK-5164)

• The search dialog opens with the last used search aspect, e.g. with ‘Document file’. This helps the users to see which parameters they have used to get the current hit list. (internal: TUK-5181)

• In the search dialog, it is possible to move an object type group to the first or last position with one mouse click. (internal: TUK-4126)

• In the object history, an inactive user is indicated by the crossed-out name. (internal: TUK-5163)

Valid from 20 AUG 2024

Always check: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/697368905

yuuvis® RAD client

• The form offers the new field control auto-complete as an alternative to the dynamic list control. (internal: TUK-19)

• When releasing a document lock, a security dialog is offered to inform who locked it and when. (internal: TUK-5231)

• The search dialog shows the total number of documents taken from the aggregation header. Now the user can see better which object types are derived from an abstract one: when checking an abstract object type, only numbers for the derived object types are shown. (internal: TUK-5299)

• When dropping a file on the client, the favored folders and the recently opened folders are offered as filing destinations. (internal: TUK-4217)

• The dashboard provides users with the role Use signature statistics with the widget Signature statistics which shows the count of signatures provided by the statistics endpoint of the signing-service (see below). (internal: TUK-5239)

yuuvis® RAD services

• The client-service is supported by an auto-complete plugin for a hierarchical list based on a JSON file (see client feature). (internal: TUK-5062).
  See the documentation: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/839286803

• The signing-service offers a statistic endpoint with the count of signatures for given document types, signature types, and a time range. In the case of a given attribute for aggregation, its values and counts are listed. Only users with the role ‘Use signing statistics’ can request this endpoint. (internal: TUK-4492)

• For higher security, only users with the privilege 'Manage system settings' can request the signing-service endpoints for status and refresh. (internal: TUK-4776)

• If configured, the signing-service starts a BPM process if the signing process is completed (yuvisgstatus = signed, experid, revised, and error). Such a process can be used for an object at the end of the signing process.
  If the parameter process-after-completion in the signing-prod.yml file is set to the BPM project name the signing-service starts this process. The simple standard process "Signing-finalization" is provided. It finalizes the object if the status is signed, and for each status an info task is sent to the requester. (internal. TUK-5246)
  See the documentation: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/447184897/General+Configurations+for+Signing#Post-processing

• If configured, the signing-service sends an email to the administrator in error cases, e.g. if the post-processing workflow could not be started or the signing platform was not reachable. (internal: TUK-5289)
  See the documentation: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/447184897/General+Configurations+for+Signing#Error-notification-via-email

• The search API supports the search for objects not containing the given value. The new attribute usenot can be used in the filter section as described in the documentation. (internal: TUK-4591)
  https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/319620127/Search+Service+API#Example%3ASearchingwith%22usenot%22infieldsoftypestring%2Cnumber%2Canddate

• The search API supports the date ranges tomorrow, nextweek, nextmonth, nextyear, thisquarter, lastquarer, nextquarter. It also supports ranges with a number following the syntax ‘prefixnumberpostfix’, with prefix = last/next and postfix = days/week/months/years. Examples: next7days, last3months. (internal: TUK-5316)

yuuvis® RAD core-service

• The core-service setup asks for the license key which is needed for communication with the License-Management-Service. (internal: TUK-4638)
  The entered key can be changed later in the management-studio.
  See the documentation: https://help.optimal-systems.com/yuuvisRAD/v100/admin/en/administration/installation/inst_license_admin.htm?Highlight=%22license%20key%22

• If the lock document is released by a different user, a history entry is written. (internal: TUK-5147)

Valid from 17 SEPT 2024

Always check: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/697368905

yuuvis® RAD client

• In the Inbox, the action menu for the task list is introduced, providing the action Return all accepted tasks. After execution, other users can work on these returned tasks. Currently, the users have to click many times to return all the tasks. The action menu can be controlled by the use of the keyboard, especially opened by the shortcut Strg -> Strg -> t (for task actions). (internal: TUK-1929)

• In the Inbox, it is possible to show the preview of a document file that is part of the process file within the task form table edit dialog. Currently, users must close the dialog to see the document in the inbox. (internal: TUK-2072)

• The operator list for a search form field of type date and datetime is extended with the operators ... (more). It supports simple time-range searches with placeholders. In this case, fields of date or datetime can be searched with yesterday, today, tomorrow, this week, last week, next week, this month, last month, next month, this quarter, last quarter, next quarter, this year, last year, and next year. Searches with such a placeholder can be saved and reused. (internal: TUK-3244)

• The operator list for a search form field of type number is extended with the operator ≠ (not equal) to find objects not containing the entered term. (internal: TUK-5443)

• The form field of type organization supports the search with the placeholder #currentuser# which can be reused in shared saved searches. (internal: TUK-4065)

• In the case of a search with a datetime property, this field is handled as a field of type date if the operator is '=', like the users practice it with the basis parameters Created and Edited. (internal: TUK-5313)

• The responsiveness of the Quicksearch widget on the dashboard is optimized, its vertical scrollbar has a better contrast and works only for the object type groups. (internal: TUK-5529)

• The chart widgets Pie and Ring can be configured concerning whether the numbers of the partial values are shown in the legend. (internal: TUK-5403)

• The language files for Chinese, Japanese, Korean, and Thai are installed with the client. (internal: TUK-5551)

yuuvis® RAD services

• The search API provides the possibility to search with a placeholder #currentuser# in the case of an organization field. (internal: TUK-5402)

Valid from 15 OCT 2024

Always check: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/697368905

License Management

• The license file can contain a parameter for a maintenance expiration date. This parameter is shown as information in the license view of the REST-WS interface.

yuuvis® RAD client

The following feature reduces administration effort:

• Chinese, Japanese, Korean, and Thai can be selected as the application language in the settings. (internal: TUK-5545)

• When a user logs in to the client for the first time, the browser's language is set as the application and definition language if it matches an available language, otherwise the configured default language is set. After an installation, English is the default language (see ‘“fallback: true” in the installed main.json of the client). (internal: TUK-5727)

The following features improve the user productivity:

• The search form field of the type catalog provides the following operators (internal: TUK-5390):

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

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

• It is possible to filter the inbox by a process model. (internal: TUK-4379)

• When hovering over a search form field label, the cursor changes and indicates the user can click on it. This helps especially new users to find the search for Without value. (internal: TUK-5555)

• The formatting for the title and description resolves the properties of the type set if configured in the designer. Users will see the set values in brackets in the header of the object details like in the result list, e. g. “Involved areas: [Japan, Germany]”. (internal: TUK-5395)

yuuvis® RAD services

• All services are upgraded to Spring Boot 3.3.x to keep the system future-proof. (internal: TUK-5117)

  • Version 9.16 LTS microservices are upgraded too.

The following features reduce administration effort:

• The index-service is optimized for processing a batch of objects. Before this optimization, the batch processing was not completed if one object couldn’t be indexed due to an error. Now one message for each of the other objects is created for indexing so only the incorrect single objects are left. (internal: TUK-5159)

• The gateway-service supports the login and logout with native OAuth2 connection and is released to be used for Microsoft Entra ID (Azure) and Keycloak. The former installation and configuration of OpenResty is no longer necessary. (internal: TUK-5489)

Valid from 13 DEC 2024

Always check: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/697368905

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)

This feature extends the support of e-invoice processing:

• Extracted e-invoice line item data can be mapped to object table data. (internal: TUK-6015)
  The mapping can be configured in the designer for a table column via an Alias setting:

  Open

  

  Set up a mapping with an extraction parameter for an e-invoice like ZUGFeRD, Factur-X, or XRechnung of the syntax CII or UBL

yuuvis® RAD services

This update keeps the system future-proof:

• All services are updated to Spring Boot 3.3.5. (internal: TUK-5987)

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)

These features increase the productivity of the users:

• The search-service 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 extends the conditions for table columns. These leads also resolve the references given in table cells so that more objects will be listed in the object details aspect References. (internal: TUK-6018).

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 8.16 LTS, from Factur-X 1.0.06 and XRechnung 3.0.2 with Syntac CII (UN/CEFACT) since yuuvis® RAD version 10.4.
  The most useful UBL-XRechnung attributes are mapped to the existing extraction 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 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, Factur-X, and XRechnung is extended with the most useful columns. Others can be added to the configuration file invoicemapping.lst. (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 rendition-plus

• Beginning in January 2025, business partners must exchange invoices electronically in specific formats like ZUGFeRD, Factur-X, or XRechnung. In the case of the XML-based invoices, an example e-invoice converter for the rendition-plus is provided on the developer portal. If users want to preview such invoices, the readable PDF rendition will be shown instead. See the documentation on how to install this converter and how to configure the client to preview the PDF rendition for such XML invoices.

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 remains in the dialog when pushing the tab keys. (internal: TUK-5839)

• In the structure tree section, references are only displayed as nodes when objects for them are available. If no object is available the complete section is not offered.

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