In addition to edoc workplace, you can also use d.ecs task (feature Tasks in d.velop documents) to process your tasks.
Things to know
Before you establish a connection with d.ecs task in d.velop documents, you must ensure the following:
-
A valid X.509 certificate is required for the TLS-secured connection. The certificate must come from a trustworthy certification authority (CA) or, in the case of self-signed certificates, be stored in the edoc platform certificate store. The host name specified in the certificate must match the destination host (Common Name or Subject Alternative Name).
-
You must use a technical administration user in d.velop documents for d.ecs task who has his own API key.
-
You have already created a working repository.
-
You have already established a connection to d.velop documents in edoc documents in order to transfer the documents to d.velop documents.
For your on-premises environment of d.velop documents, you need the edoc-taskconnect service to establish a connection between d.ecs task (feature Tasks). The service is automatically provided with edoc workplace.
Before you start, you must ensure the following in d.ecs http gateway for your on-premises connection:
-
Register the edoc-taskconnect service as an app in d.ecs http gateway.
-
When registering the service in d.ecs http gateway, enter the name edoc-taskconnect under App.
-
Also enter the destination URL (Destination URL) of your installation. Example: <https://<edoc platform URL>/edoc-taskconnect
Once you have completed the registration in d.ecs http gateway, you can create as many connections to d.ecs task as you like. You can then assign these connections to your workflows.
The following functions are available in edoc workplace under d.ecs task > Connections:
-
You can edit connections at any time, e.g. to change the API key.
-
You can delete connections if the connections are not assigned to a workflow.
For more information see: Map d.ecs task workflows in edoc workplace