Trouble Linking DocuSign with Document Templates (Migrating from HR Document Templates)

[Josue H]

Hi,

As part of the migration to the Document Templates due to the deprecation of the HR Document Templates, we are working on migrating our existing integration with DocuSign to leverage the new Document Templates

framework.

In our current setup, documents are configured using PDF Document Templates, and each one is linked to a corresponding DocuSign template—established via the integration. For HR Cases, the process is seamless: the system references the template and redirects the user to sign the document through DocuSign.

However, we are now encountering an issue:
When creating new Document Templates, we do not see any option to enable DocuSign as a signing method. Additionally, we are unable to associate any of our existing DocuSign templates with the new Document Templates.

To date, we have successfully installed and updated the following plugins:

• Document Templates (sn_doc) V 26.4.2
• Document Template Integration with DocuSign plugin (sn_dt_docusign) V 1.6.3
• DocuSign eSignature Spoke (sn_docusign_spoke) V 4.0.3

Currently our instance release is Yokohama.

We would greatly appreciate any insight from those who have gone through this transition or are familiar with the required setup.

Is there a configuration step we may have overlooked?
Thank you in advance for your support.

[Abbas_5]

Hello @Josue H,

Please refer to the below link:
https://www.servicenow.com/docs/bundle/xanadu-employee-service-management/page/product/human-resourc...

If it is helpful, please hit the thumbs up button and accept the correct solution by referring to this solution in the future it will be helpful to them.

Thanks & Regards,

Abbas Shaik

[Josue H]

Hi @Abbas_5 ,

Thank you so much for taking the time to share the documentation — we truly appreciate your support!

We’ve already reviewed that section, but unfortunately, the “Signing Type” option to point to DocuSign type doesn’t appear in our instance, which prevents us from proceeding with the document migration as outlined.

We’re currently investigating whether there’s a missing configuration or additional requirement on our end. If you’ve encountered a similar situation or have any further suggestions, we’d be very grateful.

Thanks again for your help!

Best regards