Administration

enaio® service-manager: New Microservices

'applet' Service

The new service is integrated for HTML/JS/CSS front-end components.

The service is required for display components and is not configured via a YML file. For new installations, the components enaio® documentviewer, enaio® contentviewer and enaio® detailsviewer are automatically integrated via their home URLs in enaio® enterprise-manager. The home URLs must be adapted for updates.

'gateway-ng' Service

The new service can be integrated into the project for the OAuth2/ OIDC authentication method for enaio® webclient and enaio® webclient as a desktop application.

Restrictions apply to the integration.

If the 'gateway-ng' service is installed, it is not activated and must be fully configured for authentication before activation.

The previous connection of Keycloak as an identity provider via OpenResty for authentication using OpenID Connect/OAuth2 to enaio® gateway is no longer supported and will be replaced by the 'gateway-ng' service.

'ai-connector' Service

The new service integrates the Kairos AI cloud services. This allows invoice-specific index data to be extracted from PDF files and an invoice conformity check to be carried out.

The service can currently be integrated in enaio® capture-transfer-module.

The configuration data required to access the Kairos AI cloud services is available on request from OPTIMAL SYSTEMS.

New System Role for enaio® client

System role 'Client: Manage absences for workflows': Users with this system role can report workflow users present and out of office in enaio® client.

The dialog is opened in enaio® client via the ribbon tab ENAIO > Presence > Manage presence.

The system role is not assigned a user during the update.

Users with this system role must exist in the workflow organization in order to use this function.

enaio® administrator

Two-Factor Authentication

Two-factor authentication can be integrated into enaio®. It then applies to registration at enaio® client, enaio® administrator, enaio® editor, enaio® capture, enaio® editor-for-workflow and enaio® administrator-for-workflow.

Two-factor authentication follows login, which is configured via the login settings in enaio® enterprise-manager.

It is activated at enaio® enterprise-manager. It is configured user-specifically in the user administration of enaio® administrator.

Users need a TOTP authenticator app and enter the 2FA one-time password displayed there when logging in.

Confirming with a Password

For subscriptions, follow-ups, forwarding work items and scripts, users can be asked to confirm by entering their password. Confirmation must be made with the enaio® password if a login pipe is not configured.

Confirmation by password can be activated/deactivated across the board in enaio® administrator.

For new installations, the function is deactivated by default; for updates, the function remains activated.

The setting is only valid for enaio® client, not for enaio® webclient.

'De-Archiving' and 'Hash Check on Object Level' Automatic Actions – Limit on Queries

If a limit on queries is configured in the project, this limit also applies to the 'Dearchiving' and 'Hash check on object level' actions.

In the configurations of these automatic actions, the new parameter 'REQUESTROWSETLIMIT' can be used in the query file to change this value for the execution of those actions.

If one of the actions is executed and there are more hits than configured by the limit on queries, this is logged as a note.

'Media Dearchiving', 'Hash Check' and 'Signing' Automatic Actions – Maximum Number of Hits

The automatic actions 'Media dearchiving', 'Hash check' and 'Signing' are no longer limited by the setting 'Maximum number of hits' - default: 50000.

'Hash Check' and 'Hash check on Object Level' Automatic Actions

The signature check can be deactivated for the 'Hash check' and 'Hash check on object level' actions.

'User/Group Import' Automatic Action

Users whose accounts no longer exist or are blocked as a result of the import are automatically set to out of office for the workflow and, if necessary, the substitute is activated. Substitution is also automatically activated for deactivated workflow users.

Workflow roles and the integration of workflow users into the organizational structure can also be synchronized.

The activation of two-factor authentication is also exported and imported for users. The keys are not part of the data.

'Cache Maintenance' Automatic Action

In configurations that specify the minimum age as a criterion, the 'Cache maintenance' action deletes based on the last access time and no longer based on the creation date.

Dialogs in enaio® administrator

Configuration dialogs in enaio® administrator can be resized to any size. The selected settings are saved user-specifically.

enaio® editor

ModalDialog Add-on

The new ModalDialog add-on axaddbrowserdlg.dll provides a way to create customized and freely configurable modal dialogs. These modal dialogs enable the implementation of a wide variety of business processes and scenarios by flexibly integrating additional business logic for interaction with enaio® client and enaio® webclient.

In terms of technology, modal dialogs behave like a web page in a WebControl/iFrame based on HTML5, JavaScript and CSS. For these customized solutions, enaio® services and project-specific services can be accessed to analyze, structure and process index data and workflow data.

The 'MDA' license is required for the ModalDialog add-on.

We offer the ModalDialog API for communication between modal dialog and enaio®. The ModalDialog API encapsulates the respective APIs of enaio® client and enaio® webclient and thus enables a joint implementation. Special events and methods arrange for the exchange of information and offer various interactions.

The ModalDialog add-on can be integrated on forms and also on workflow forms:

• enaio® client

  • The ModalDialog add-on can be assigned to a text field. URL, localizable window titles and localizable tooltips are specified via EXTRA entries.

    This integration can only change the data of the add-on field.

  • The ModalDialog add-on can be called via script. For example, via an OnClickItem/ButtonClick event using a button on the form.

    All fields of the form can be changed with this integration.

• enaio® webclient

  • The ModalDialog add-on can be called via script.

    Assignments to a text field are not yet supported by enaio® webclient.

The documentation for enaio® editorand enaio® editor-for-workflow contains examples of configurations for the ModalDialog add-on.

The ModalDialog API documentation also contains a demo project that you can integrate into development or test installations in order to test and analyze ModalDialog add-on functions.

The ModalDialog add-on is not yet available for enaio® mobile and enaio® webclient on mobile devices.

WWW Add-on

The maximum number of characters for fields with the WWW add-on is no longer limited to 255 characters. The maximum number now depends on the permitted field size of the database used.

Treeview Add-on

The Treeview add-on can be localized in the languages of the object definition.

Quickfinder Add-on

The execution of the Quickfinder add-on can be configured in an extended way. Previously, the search was carried out automatically. Now you can also configure that the search form is opened with all configured entries or empty.

For enaio® webclient this function will only be available with a subsequent service release.

The following add-ons of the connected object type are also supported: date add-on, database add-on, user add-on, rights group add-on, SQL add-on, fieldmapping add-on and treeview add-on.

'Webcontrol' Dialog Element

The WebView2 control provided by Microsoft is integrated with this version. This enables complex HTML integration on forms, for example enaio® documentviewer.

'Graphic' and 'Static text' Dialog Elements

The names of the 'Graphic' and 'Static text' dialog elements no longer have to be unique on forms.

The unique internal name must be used for use in scripts.

Logging

Logging has been extended.

• Channels can receive the 'LogLongTerm/permanently open file' property. The log file thus remains open throughout the component's runtime and enables faster logging.

• Filters for logging can be set up. This allows logging to be filtered to relevant log entries as soon as they are written.

The default values of the channels have been increased: LogMaxFileSize, LogHighWater, LogLowWater.

enaio® editor-for-events

Scripts are loaded by enaio® editor-for-events directly from the database when they are opened and no longer from the client cache. The scripts are also saved directly in the database.

enaio® client continues to load scripts into the client cache at startup. Updating the cache requires a restart of enaio® client.

enaio® directory-sync

enaio® directory-sync has been extended and can also synchronize data with LDAP systems in addition to Entra ID.

The functions for synchronizing workflow data have also been extended.

The application to be integrated was renamed for enaio® directory-sync. Configurations must be adapted accordingly. Include enaio-directory-sync.exe instead of enaio-aad-sync.exe.

enaio® directory-sync will replace the automatic action 'XSLT directory synchronization' in a future version.

enaio® repository-manager

enaio® repository-manager has been updated and must be reinstalled and reconfigured.

With the new version, KGS components are no longer used and the ArchiveLink and ILM connections are split into two separate services.

Windows Certificate Manager

Certificates can be integrated with version 11.10 via the Windows certificate management.

DMS Service: New Endpoints

The DMS service has been updated to version 6.4. It contains new endpoints for managing notes and links.

The full-text search now supports facets and parent conditions. Content files of several objects can be loaded as a ZIP archive or as a PDF file.

Parallel Archiving via the 'archive' Microservice

When setting up a virtual archive for the 'archive' microservice in enaio® enterprise-manager, the number of threads can be used to specify how many channels are used to transfer documents between the server and microservice in parallel.