Open Documentation Menu

Configuring the d.3 repository

The basic connection and configuration data for the d.3 system used is stored in the d.3 repository area.

Please carry out the following steps to configure the d.3 repository:

  1. Open the d.3 repository area.

  2. Select the relevant repository.

  3. Transfer the API keys of an administrative user and a service user. You have direct access to the configuration interface of the API keys of d.ecs identity provider via a corresponding context action.

  4. The administrative user requires the "Administrator authorization" authorization in d.3 so that, among other things, value sets can be synchronized. The service user requires the "Service user" authorization for background tasks. In addition, both users must receive all access rights to the document types and categories created by dbs | case manager via an authorization profile after they have been created.

  5. Fill in the prefix for the internal case number.

  6. Accept the configuration by clicking on Save.

Note

The configuration can be temporarily adopted by clicking on Live. After restarting the dbs | case manager, all settings since the last save time are discarded.

Note

If you start several dbs | case manager instances and both work with the same d.ecs terms instance, you must define different prefixes, as the deadlines are only linked to the case via the case number and this must therefore be unique.

Preparing the d.3 repository configuration

The API keys of an administrative and a service user are required in the configuration of the d.3 repository. A context action offers the option of jumping directly to d.ecs identity provider and configuring the API keys. If you require further information, please refer to the d.ecs indentity provider documentation.

Preparing the d.3 database for search queries

When searching in the d.3 system, some searches may be case-sensitive. This occurs, among other things, when searching for organizational units and manifests itself, for example, when using an Oracle database in that the search is always case-sensitive.

Advanced repository configuration

After you have configured the access to the d.3 repository, you can use the document management to create the categories, datasets and advanced properties in d.3. If necessary, you can configure extended properties for other database fields.

This is how it works

  1. Open d.3one and log in as a technical administrator.

  2. Select the tile Configuration.

  3. In the Administration area, select Document management.

  4. Create the respective value sets, extended properties and categories.

  5. If you already have existing value sets, extended properties or categories in your d.3 system, assign the respective entry to the existing d.3 entry. To do this, select the item Existing <type> and then select the relevant entry in the selection. Please note the information below.

  6. Exit edit mode in d.3 admin or close d.3 admin.

  7. Apply your configuration by clicking on Save. The current processing status is displayed in the respective areas. If you continue to see entries, you must configure them correctly and save them again.

  8. You can now continue with the configuration of authorization profiles in d.3 admin.

Note

As an administrator, you can perform the following actions in the document management:

image2019-6-11_17-14-15.png Use this action to display hidden content. In the document management, successfully linked properties are hidden and only configuration items with errors or warnings are displayed.

image2019-8-30_14-24-18.png Click on this symbol to download the current configuration as an XML document.

image2019-6-11_17-13-44.png Click on this icon to download the INI file that you need for the hooks. Place this file in the folder in which the dbs | case manager hooks are stored.

image2019-6-11_17-17-19.png Click on this icon to discard all unsaved changes.

image2019-8-30_14-25-8.png Click on this icon to reload the d.3 configuration. If, for example, a new extended property has been created in d.3 admin, this property only appears after this button has been clicked.

image2019-8-30_14-27-22.png Here you create the default dossier scheme.

image2019-8-30_14-27-53.png In order for the case overview to display the list of cases, the assignments must first be transferred to the DMS app. Click on this symbol to create the assignments automatically.

Note

If you use existing extended properties, you should ensure that you only use properties that are of the "date and time" data type, especially for date properties. It is possible to select properties of the "Date" data type. In this case, however, no time is saved and 00:00:00 is always assumed instead.

Warning

All extended properties must be assigned to different d.3 properties so that the assignments can be created successfully. The DMS app does not allow different source properties to point to the same target property. The logged-in user also requires the appropriate rights to be able to save these assignments.

If you have added further properties to the document type Case in order to be able to use them via the extended master data area, you must first reload the d.3 configuration and then save it. Then transfer the configuration to the DMS app.