edoc contract Administration Guide
edoc contract Administration Guide
Breadcrumbs

Install edoc contract app multiple times

You can install multiple app instances of edoc contract in edoc automate, e.g. to establish connections to different ECM repositories.

Enter an environment name for each app instance. The environment name is displayed to users per page and in the dialogs so that your users always know which environment they are in within the context of the application.

You can multiply the edoc contract app in various ways:

  • Duplicate app in edoc automate.

  • Create app as a new instance when importing into edoc automate.

Option 1: duplicate the existing app

  1. Copy the edoc contract app by clicking on Duplicate in edoc automate in the Available apps section of the app to be copied in the app-specific More actions menu.

  2. In the Duplicate App edoc contract dialog, enter a new name for the app or change the existing name.

  3. Activate the Create new instance entry under Instance.

  4. Click on Duplicate.

  5. Carry out the Composer installation in the new app instance under App details > Composer.

  6. Go to the administration of the MySQL database instance by clicking on phpMyAdmin in the App editor under App Details in the burger menu.

  7. Log in to the database instance app-server-mysql of the respective environment (e.g. master).

  8. Create a database for the new edoc contract instance. The default name of the database is edoc_contract. You must enter a new and meaningful name for your new instance.

  9. Create the required tables in the database with the appropriate SQL script:

    1. Click on Files in the app editor under App details in the burger menu to open the edoc automate file manager.

    2. Execute the SQL script in the path assets/sql/create.sql in phpMyAdmin.

  10. Change the configuration for the app_db data source and enter the newly created database in the app details in the Datasource section.

  11. Open the Variable section in the new instance of edoc contract in the App details in edoc automate.

  12. Enter a name for the variable app.instance_name and save the change.

  13. Go to Administration > Establish connection to the ECM system and change the parameters for d.velop documents.

  14. Change the configuration for the data source Content Service in the app details in the Datasource section and enter the parameters for the connection with d.velop documents.

Option 2: create a new instance when importing the app

  1. Import an edoc contract app by clicking on Import App in the Available Apps section on the edoc automate start page.

  2. Select the locally saved app file (*.eax) in the import dialog with Select App.

  3. Open the Instance tab in the Import App dialog.

  4. Select the Create new action under Choose instance action,

  5. Enter a meaningful name for the new app instance.

  6. Enter a suffix for the flows.

  7. Click on Import.

  8. Run the Composer installation for the newly created instance if needed.

  9. Go to the administration of the MySQL database instance by clicking on phpMyAdmin in the App editor under App Details in the burger menu.

  10. Log in to the database instance app-server-mysql of the respective environment (e.g. master).

  11. Create a database for the new edoc contract instance. The default name of the database is edoc_contract. You must enter a new and meaningful name for your new instance.

  12. Create the required tables in the database with the appropriate SQL script:

    1. Click on Files in the app editor under App details in the burger menu to open the edoc automate file manager.

    2. Execute the SQL script in the path assets/sql/create.sql in phpMyAdmin.

  13. Change the configuration for the app_db data source to the newly created database in the app details in the Datasource section.

  14. Open the Variable section in the new instance of edoc contract in the App details tab in edoc automate.

  15. Enter a meaningful name for the variable app.instance_name.

Tip

For better differentiation in the d.3one context actions, you can customize the titles displayed for an edoc contract instance.

  1. Click on Integrations in the app details of the app.

  2. Click on Edit for the respective integration.

  3. Change the text for the label displayed (e.g. Contract control (HR)) in the Captions section.

Import a new app version for all instances

If you want to import a new edoc contract app version, you must import the new app version in all existing instances.

There are different ways of importing, one for the original app instance and one for a subsequently created app instance (duplicate or new instance).

Import a new version into the original app instance

  1. Click on Import App in the app overview (start page) of edoc automate to open the import dialog.

  2. Select the locally saved app file (*.eax) in the import dialog with Select App.

  3. Open the Instance tab in the Import App dialog.

  1. Select the None action under Choose instance action to import the app version into the original app instance.

  2. Click on Import.

Import a new version into a subsequently created app instance

  1. Click on Import App in the app overview (start page) of edoc automate to open the import dialog.

  2. Select the locally saved app file (*.eax) in the import dialog with Select App.

  3. Open the Instance tab in the Import App dialog.

  4. Select the action Update <Name of the app instance> under Choose instance action to import the app version into the subsequent app instance.

  5. Click on Import.