If you migrate your d.velop documents system, which you operate on-premises (locally), from the d.3ecm product line (deprecated) to d.velop documents (d.3one), you have to perform different steps in different apps one after the other:
-
In edoc content services: select the module with the ID d3one and set the parameter Feature.UseUUIDsForMapping to false in the DMS app at https://<d3one-host>/dms/config. For more details about the reasons see the edoc content services guide by searching for the parameter name.
Make sure to follow the instructions in the edoc content services guide to avoid an incorrect transfer.
-
In edoc automate in the edoc contract app: change the module ID for edoc content services in the app details in the Datasources section from d3 to d3one.
-
In the edoc contract administration: define the field mapping for the ECM categories in edoc contract again.
Once you have taken the appropriate steps in edoc content services and the DMS app, you can continue with the changes in the edoc contract app in edoc automate.
Here's how
-
Open the edoc contract app in edoc automate.
-
In the app details in the Datasources section, click on Edit for Content Service.
-
Change the ModuleId field from d3 to d3one.
-
Customize the access data to the ECM system as described under Install and uninstall edoc contract.
-
Go to the administration of the MySQL database instance by clicking on phpMyAdmin in the edoc automate App Editor under App detail in the burger menu.
-
Log in to the database instance app-server-mysql of the respective environment (e.g. master).
-
Remove the field mapping in the ecm_fields_to_contract_fields table.
-
Customize the mapping of the ECM categories as described under (v26.1.1-en) Configure the mappings for the ECM categories.