Administration

enaio® 9.10 »

System Roles for enaio® client

The following system roles are new:

  • Client: scan documents.

    This new system role simplifies the administrative aspect of handling licenses. Every enaio® client was assigned a scan license at startup; now the new system role is checked first.

    Every user with the system role 'Client: Start' receives this system role after updating.

  • Client: show the number of objects in the register tree.

    This display can be deactivated by removing this system role since the display of the number of objects in the register tree does not fully analyze the rights system.

    Every user with the system role 'Client: Start' receives this system role after updating.

System Role 'Client: Export Objects'

The system role 'Client: Export from hit list' has been renamed: Client: Export objects. It is now also required for exporting images from image modules.

In addition, system roles cannot prevent actions for documents opened in external applications.

System Role 'Editor: Define Visibilities'

This system role is required for setting up specialist administrators in enaio® editor.

Every supervisor receives this system role after updating.

Specialist Administration for enaio® editor

You can set up specialist administrators to edit the object definition, including the customization of the database in enaio® editor. Specialist administrators can be granted access to single or multiple cabinets. Within these cabinets, specialist administrators can create, edit, and delete objects and make the necessary adjustments to the database.

Cabinets other than the ones assigned will not be shown. Specialist administrators who have opened enaio® editor lock access to the object definition. The object definition is only shown to other users in enaio® editor as read-only.

Reference catalogs referring to other cabinets are shown, and changes to the catalog data are allowed and are applied universally. Add-ons related to other cabinets can be created. Languages cannot be added, and database indexing cannot be performed.

Specialist administrators can be created by users with the system role 'Start editor' and the new system role 'Editor: Define visibility' in enaio® editor.

enaio® Outlook Add-In NG

Attachments: attachments can be created as documents separately from the e-mail.

Workflows: workflows can be started from the add-in. The configuration takes place via the configuration file ems-prod.yml: the input parameters of a workflow are assigned to extraction fields of the e-mail.

The configuration of a workflow integration has the following structure:

mapping  
emsTyps:  
...  
workflows:  
- name: "wfname"

Configuration section for the workflow model.

familyId: "GUID"

Specification of the GUID of the workflow family.

The GUID is entered in the properties dialog of the workflow family in enaio® editor-for-workflow.

fileTarget: INFO

Entry for the file:

INFO: The e-mail is placed in the file.

NONE: The e-mail will not be included in the file.

inputVariables: List of input parameters of the workflow to which data is assigned.
-name: "parameter1" Name of the input parameter.
 extractionName: "OS:Subject" Name of the data to be assigned for the 'extraction' service.
-name: "parameter2" Name of a further input parameter.
 extractionName: "OS:MailFrom" Name of the data to be assigned for the 'extraction' service.
-name: "parameter3" Name of a further input parameter.
 extractionName: "OS:MailCc" Name of the data to be assigned for the 'extraction' service.
 defaultValue: "noCc" Assignment of a default value that is only entered if assigned data for the extraction is not available.
-name: "parameter4" Name of a further input parameter.
 fixedValue: "fix" Assignment of a fixed value instead of an extraction value.

Login Dialog

The default is the Windows user name is used in the login dialog of enaio® client. As an alternative, this can be prepopulated with the user name of the last user at the workstation. To do so, the file as.cfg from the \etc directory of the data directory in the [SYSTEM] section is appended to include the following: STORELASTLOGINUSER=1

Help Desk Address for enaio® Outlook Add-In NG

enaio® Outlook Add-In NG allows users to send information via e-mail in case of errors. An address that is prepopulated can be entered in enaio® enterprise-manager for this feature: Server properties > Category: General > General parameters > Help desk e-mail address

enaio® administrator

Filter: user management dialogs have been enhanced with filters so that the desired entry can be found faster in long user and group lists.

Sorting: settings in dialogs for sorting can be personalized and saved. The feature is activated via the menu Tools.

enaio® editor

Hierarchy catalog: the keyboard control for configuring hierarchy catalogs, especially for moving entries, has been expanded.

Multiline: rights group control fields have been expanded to included the property 'multiline.'

Other: the former database type 'm/w' for 'male/female' has been expanded to include 'd' for 'other.' The change is made automatically in an update.

Archiving

The microservice 'archive' was introduced with 9.0 for archiving via 64-bit servers. The microservice is now also available for 32-bit servers and can be integrated with the following archiving solutions:

iCAS / HCP-Archive / Cloudian HyperStore / Dell EMC ECS / S3 (AWS)

AD Synchronization

The new attribute 'ADSync' was added for objects with the 'Role' class ' in enaio® editor-for-workflow in order to simplify workflow assignments.

Rights Group Fields

Fields are checked for clauses when converting the rights group add-ons via the automatic 'rights group conversion' action – axacrgcnv.dll – and they may not be offered for conversion.

LDAP-S

SSL can be used for the connection in LDAP configuration contexts.

Core Services

SQL: core services no longer execute SQL. The current exception to this is still enaio® appconnector with few call ups.

Tomcat: the Tomcat servers integrated into the core services have been upgraded to the latest version.

enaio® watch-dog

The administrative component enaio® watch-dog, used to control the FineReader integration, is no longer needed and no longer installed.