Upgrade Guide
Upgrade process from v7 to v8. Conditional on SigningHub 10 requirements.
The new SigningHub for SharePoint 8 is released alongside SigningHub 10. This updated SharePoint integration features a complete redesign aligned with the architecture and user experience improvements introduced in SigningHub 10. The result is a more seamless, intuitive, and tightly integrated solution.
This guide will help you to upgrade your app from version 7.9.3 to 8.0.0.
Compatibility with SigningHub
7.x.x
up to 8.6.0
8.x.x
from 10.0.1
The SharePoint Integration App version 7.9.3 is compatible with SigningHub versions up to 8.6.0. If you are upgrading to SigningHub 10.0.1, you must also upgrade the SharePoint Integration App to ensure compatibility.
Migration
There is a strict compatibility requirement between SigningHub 10 and SigningHub for SharePoint 8. This means that once you upgrade to SigningHub 10, the older SharePoint integration (v7.x) will no longer function.
Therefore, it is essential to upgrade the SharePoint integration to version 8 before or alongside the SigningHub 10 upgrade.
Handling In-Progress Workflows from v7
While upgrading, it is important to account for workflows initiated using SigningHub for SharePoint v7. These workflows still need to be completed and saved back into SharePoint, even after the platform is upgraded to SigningHub 10.
To support this, a migration-specific update of the SigningHub for SharePoint v7 Proxy has been released. This updated proxy is compatible with SigningHub 10 and ensures that workflows started in the v7 environment can be finalised correctly.
Warning. The previous SigningHub for SharePoint version 7 needs to be kept installed alongside the new proxy update, and kept installed while workflows from v7 are still in progress.
Even if the old application no longer works, it holds the connection configuration between the Proxy and SharePoint.
Once workflows are completed the Proxy and the old integration can be uninstalled.
Components of SigningHub for SharePoint v7
SigningHub for SharePoint v7 consists of two distinct components:
SharePoint App: A client-side application embedded within SharePoint, responsible for displaying the user interface.
SharePoint Proxy: A server-side component that handles workflow completion and ensures signed documents are saved back to SharePoint, even when the SharePoint App is not active.
⚠️ Note: The SharePoint Proxy component has been removed in SigningHub for SharePoint v8. The updated version is solely intended to support migration scenarios and should be retained only until all workflows initiated in v7 are completed.
Proxy Update
The proxy service was configured as auto-pull app to automatically completed documents back to the specified Sharepoint location.
To maintain workflow continuity and prevent data loss, a new proxy service patch compatible with the SigningHub 10.0.1 version has been introduced.
SigningHub.com
For clients using SigningHub.com, the Proxy will be updated automatically without the need to take any action.
SigningHub On-Premise Deployments
The proxy needs to be updated by the system administrator. Please refer to the Community Portal or contact support to get the latest version.
Follow the v7 guides to install the update Proxy installation.
New SigningHub Webhook
During the migration two different SigningHub webhook notifications will be running:
SharePoint Proxy v7 Migration Patch. Will be notified of events regarding workflows started by the previous version of the integration.
SigningHub for SharePoint v8. Will be notified of events regarding workflows initiated on the newest version of the application.
For compatibility purposes the SharePoint Proxy v7 Migration Patch should use the same webhook as it has always been using, under SigningHub Settings > General > Advanced > More.
The new SigningHub for SharePoint v8 is required to use the webhook defined under SigningHub Settings > Enterprise Configurations > Settings > Integrations .
Integration Settings
Settings are not carried over from v7 to v8. Settings will need to be reconfigured. Please follow the manual to set up the Integration settings.
Last updated