The behavior for downloads will change in the future: When downloading documents, a redirect to the dmsdocs app will take place. Client applications must be able to follow the redirect accordingly. The change only affects d.velop documents in the cloud (for now).

In the following, you will learn more details and what you may have to do for the change.

What will change technically?

When downloading documents via dms app, a redirect to the dmsdocs app will take place in the future. The actual download will take place via the dmsdocs app. The HTTP request to the dms app for the download will be answered with the HTTPS status code 302 Found. A relative URL to the dmsdocs app is specified in the Location HTTP response header.

The change only affects d.velop documents in the cloud (for now). Hybrid or on-premises systems are not affected. Nonetheless we reserve the right to make a change in hybrid or on-premises systems as well. You will receive a separate announcement in this case, though.

When will the change take place?

An exact date has not been set yet. We are currently expecting the change to take place in the second half of the year.

What do I have to do?

Depending on how you use or technically manage d.velop documents in the cloud, you need to take action for the change:

• Users: If you only work with the d.velop documents user interface in the browser, there is nothing else you need to do.
• App builders: If your apps download the documents via dms app through the backend (app-to-app communication), you need to take action. Make sure that your apps can work with the redirect.
• Administration: If you manage scripts that download documents via dms app, you need to take action. Make sure the scripts can work with the redirect.

Will there be a final announcement?

We will make a final announcement 4 weeks prior to the release of the change. If you need to take action, we still recommend that you make the necessary adjustments now.