Backwards Compatibility

The DMS Mobile DESK can also connect to older agents. This ensures that new versions of the app can be released without having to update all agents immediately. In this case, the app will simply display a warning that some features may not be fully available:

You are connected to an outdated server interface. To ensure the application behaves as expected, please contact your administrator to update the interface (On-Premise-Agent) to at least version …

As soon as the agent is updated, this warning will disappear automatically.

Known Issues with Old Agents

Unfortunately, it is often very difficult to guarantee 100% backward compatibility. Although we do our best, we do not always succeed. Below are the points where we are aware that backward compatibility with an old agent is not given.

Agent v1.1.36: Uploading New Document Versions Fails

The DMS Mobile DESK prevents uploading documents with unknown file extensions. Unfortunately, the on-premise agent in version 1.1.36 incorrectly checks the file extension based on the document title instead of the file name. In a newer version of the app, the title is determined from the file name without the extension. As a result, the agent in version 1.1.36 can no longer check the file extension and does not allow the upload. The user sees an error, and the agent log mentions an unauthorized file extension.
As long as the agent has not been updated, this problem can be worked around by manually adding the file extension to the document title when uploading in the app.

Agent v1.5.30: Loading Errors with DMS 7.5

The DMS Mobile DESK is particularly slow in connection with DMS 7.5 and shows errors when searching and opening files and documents. The reason is the use of the overloaded DMS API method ValueStore.GetKeys(ids) to detect active co-authoring sessions, which was only introduced with DMS 7.6.302. From version 1.6, the DMS Mobile DESK ignores this method when using DMS 7.5.

Agent v1.8.10: Connecting to SQL Server Without Explicit Certificate Trust

The STP.Documents On-premise-Agent connects to the SQL Server to store its connection data. Before version 1.9, this was possible without explicitly trusting the SQL Server’s certificate. Since the SQL Server is usually installed with a self-signed X.509 certificate, the agent’s ConnectionString must be slightly adjusted after updating to version 1.9. The ConnectionString is located in appsettings.json in the program directory (C:Files (x86)AGDocuments OnPremise Agent). Here, the additional parameter TrustServerCertificate=True must be specified. The ConnectionString then looks like this:

{
    ...
    "ConnectionStrings": {
        "AgentDb": "Server=...;Database=...;User=...;Password=...;TrustServerCertificate=True"
    },
    ...
}

If the agent is newly installed, this parameter is included automatically. Only after an update from an earlier version must it be added manually. After adjusting the ConnectionString, the agent service must be restarted once.
In rare cases, the installer may complete the update process but not update all files in the program directory. In the log file in the program data directory (C:AGDocuments OnPremise Agent), you may then see MissingMethodExceptions. In this case, the agent must be reinstalled. First, the configuration file appsettings.json should be backed up. Then the agent must be uninstalled. Afterwards, the old program directory should be removed so that no DLL files remain. Now the agent can be reinstalled. Finally, the backed-up configuration file can be restored and the agent service restarted once. The agent should now start with the known configuration and connect to the cloud as usual.

Other Known Implications

In rare cases, the introduction of a new feature affects already known and familiar functions. Below are the points where we are aware that backward compatibility is not given.

Downloading and Uploading No Longer Available to All

Downloading and uploading documents was available to all users in an earlier version of the app. In a newer version, feature permissions were introduced, so these functions can only be made available to certain users. To protect law firm documents and in view of prominent data protection guidelines, these new feature permissions were not automatically assigned to existing users.
The administrator can grant and revoke these permissions at any time in the Cloud UserManagement.

Tasks No Longer Available to All

Working with tasks was available to all users in an earlier version of the app. In a newer version, feature permissions were introduced, so these functions can only be made available to certain users. For a more granular rights profile, these new feature permissions were not automatically assigned to existing users. External users, for example, should not automatically receive these rights.
The administrator can grant and revoke these permissions at any time in the Cloud UserManagement.

winsolvenz Participants No Longer Available to All

Participant information from winsolvenz was available to all users in an earlier version of the app, regardless of whether they were authorized in winsolvenz. In a newer version, a feature permission was introduced, so this function can only be made available to certain users. For a more granular rights profile, this new feature permission was not automatically assigned to existing users. External users, for example, should not automatically receive this right.
The administrator can grant and revoke this permission at any time in the Cloud UserManagement.

Co-Authoring No Longer Available to All

Joining active co-authoring sessions was available to all users in an earlier version of the app. In a newer version, a feature permission was introduced, so this function can only be made available to certain users. For a more granular rights profile, this new feature permission was not automatically assigned to existing users. External users, for example, should not automatically receive this right.
The administrator can grant and revoke this permission at any time in the Cloud UserManagement.