Migrate existing DocuSign Legacy Delivery Option to new DocuSign Delivery Option

In order to continue using the DocuSign Legacy app without interruptions you can switch to any of the new available authorization methods. For more information on how to switch your authentication method, refer to the DocuSign Legacy Integration topic. If you have been using the DocuSign Legacy delivery option, then packages that have been set up with that delivery option cannot be used or edited in Salesforce Lightning and the new DocuSign delivery option, often referred to as the DocuSign Apps Launcher (DAL). If you are looking to continue using a previously created DocGen Package with DAL, then those packages can be migrated using the steps outlined below. This will allow you to use any migrated packages with the DAL delivery option and using the Salesforce Lightning interface.

For information on the differences between DocuSign Legacy delivery option and the new DocuSign delivery option refer to Classic and Lightning differences in DocuSign Delivery options section.

Important: As of September 30, 2024 DocuSign is deprecating its legacy authentication methods: Legacy Authentication and Send-On-Behalf-Of (SOBO). These authentication methods were previously used to authenticate a DocuSign Legacy app integration for use with Nintex DocGen. While you can switch an older authentication method to a new authentication method to continue using existing delivery options in Salesforce Classic, in order to use DocuSign with Salesforce Lightning you need to add the new DocuSign integration for the DocuSign Apps Launcher (DAL). However, any existing Document Packages created using the DocuSign Legacy app integration will not work by default with DocuSign for Salesforce Lightning.

Convert existing Legacy delivery option to Lightning Designer

From the Salesforce Classic interface, it is possible to move a Document Package associated with the DocuSign (Legacy) delivery option from a Legacy delivery option to the new DocuSign delivery option for use within Salesforce Lightning.  It is important to note that delivery options using the new DocuSign integration can only edited and used in Salesforce Lightning, while delivery options using the DocuSign Legacy integration can only be used and edited from Salesforce Classic.

In order to convert an existing delivery option you first need to make sure you have done the following:

• Updated DocGen to the latest package release. For more information on the latest package release refer to DocGen Release Notes.

• Added a new DocuSign integration for the DocuSign Apps Launcher. For more information on how to add DocuSign integration refer to DocuSign Integration topic.

Note: You do not need to delete or remove your old DocuSign Legacy integration settings in order to set up a new integration for DocuSign Apps Launcher (DAL). Both integrations can be set up at the same time.

1. In Salesforce Classic, locate a DocGen Document Package that is currently using the DocuSign Legacy delivery option.

   1. How to identify a DocuSign Legacy DocGen Document Package:

      1. Open a Document Package.

      2. Scroll to the Delivery Options section and click Edit.

      3. In the Edit page check the Record Type field. If the Record Type field displays "DocuSign (Legacy)" then that means the package was created using the Legacy delivery option.

      4. Note: In order to see this Record Type you need to be on the newest version of Nintex DocGen. You cannot perform migration unless you have updated your package to the newest release.

2. In the Delivery Option details section, select DocuSign Legacy in the Delivery Package field.

3. In the Record Type field, click the Change hyperlink.

4. Select DocuSign in the options. The record migrates and is now usable as a DocuSign Document Package in the Lightning Designer.

   1. Once a Document Package has been switched to the new DocuSign option, the package will no longer editable in Salesforce Classic. However, once the package has been saved you can switch over to Salesforce Lightning and edit the Document Package as necessary.

5. Repeat the above steps for each Document Package that you would like to migrate to the new DocuSign delivery option.