Current DocuSign subscribers upgrading their Enterprise databases to either v.98F, .99C or 23.1 must update integration configurations for both DocuSign and Enterprise.
For the DocuSign Integration to operate with v98F/.99C/23.1 and future releases, administrators must:
- Confirm the Base URL in Enterprise database(s).
-
Update existing DocuSign Sandbox Configuration.
-
Update and Provide Consent for Existing DocuSign Integration Configurations in Enterprise.
DocuSign integration end users are also required to Provide Consent before sending envelopes. Users must have their own DocuSign account and login credentials using the email address associated with their Enterprise User ID.
Confirm Enterprise Database Base URL
Before updating the DocuSign Sandbox configuration, confirm the Base URL in Enterprise. To locate and confirm the Base URL:
- Click the Edit Site Configuration link from the Main Menu. The Edit Site Configuration window opens.
- In the Base URL field, enter your Enterprise site URL (i.e, https://YourSiteDomain.ungerboeck.com/prod or https://YourSiteDomain.ungerboeck.com/test, etc.). If it already exists, no action is needed.
- Click OK.
Update Existing DocuSign Application Configuration for Sandbox Integration Configurations
To update an existing DocuSign Integration Sandbox environment configuration:
- Sign in to https://account-d.docusign.com. The Home screen displays.
- Click the Settings Tab.
- In the menu, click Apps & Keys.
- Click the Action button for the sandbox application to update. The Action Menu displays.
- Click Edit. The application information page opens.
- In the General Info section, copy or note the Integration Key. It is needed for the Enterprise Configuration.
- In the Authentication section, click Add Secret Key. When first added, the Secret Key will display in its entirety. Once the configuration is saved, it is masked.
- Copy or note the Secret Key. It is needed for the Enterprise configuration.
- In the Additional Settings section, click Add URI. A new field displays.
- Enter the Redirect URI. The Redirect URI consists of the Enterprise database URL to which you are connecting your sandbox environment, followed by the DocuSign callback of /api/ElectronicSignature/DocusignAuthCallback. (Example: https://YourSiteDomain.ungerboeck.com/test/api/ElectronicSignature/DocusignAuthCallback).
- Click Save to close the page. You may choose to leave the page open for reference until the updates are complete.
NOTES:
- It could take up to 5 minutes for DocuSign to register the new Redirect URI.
- For Production and Production BYOE integration configurations, the system provides the Integrator Key and Client Secret Key. The fields do not display.
- For Production and Production BYOE integration configurations, the Momentus team will update the customer Redirect URI.
Update and Provide Consent for Existing DocuSign Integration Configurations in Enterprise
IMPORTANT: When updating an existing DocuSign configuration, you must have Environment field and, for Sandbox configurations, the Integrator Key and Client Secret Key fields populated before providing consent. If they are not, the configuration will not save.
To update and provide consent for existing DocuSign Integration configurations in Enterprise:
- Click the Electronic Signatures Configuration link from the Main Menu. The Integration Configurations | Electronic Signatures page opens.
- Select the configuration to update.
- Right-click and click Edit. The Edit DocuSign Configuration window opens.
-
Enter the following information:
-
For Sandbox environment configurations:
- Confirm population of Integrator Key field. If it is blank, copy the Integration Key from the General Info section of the Sandbox application information page in your DocuSign account and enter it here.
- Enter the Client Secret Key copied from DocuSign configuration information page. If the field does not display on the window, add it to the layout.
-
For Production environment configurations, there is no information needed. Proceed to the next step.
-
For Sandbox environment configurations:
-
For version 2023.1, click Provide Consent. A browser window opens with a DocuSign Login page.
- For versions .98F and .99C, click the Tools menu at the top of the window. Then click Provide Consent.
-
Before clicking 'Provide Consent', confirm you are not logged into DocuSign to avoid errors.
- Enter the email address used for your DocuSign account and click Next. This email must match the email associated with the Enterprise user’s User ID.
- Enter the Password used for your DocuSign account and click Log In. A message displays confirming the authentication was successful. If you receive any messages other than a successful one, please contact Momentus Customer Support Services.
- Click OK on the message to close the browser window.
- On the Edit DocuSign Configuration window, click Refresh to update the account field.
- Click OK to save and close the window. Do not click Cancel or this will invalidate the consent.
End User Provide Consent to Allow for Sending Envelopes
The first time a user attempts to send a document for electronic signature, following the updates to the integration configurations, they will be prompted to Provide Consent.
When the prompt displays:
- Click Provide Consent. A browser window opens with a DocuSign Login page.
- Enter the email address used for your DocuSign account. This email must match the email associated with the Enterprise user’s User ID.
- Click Next.
- Enter the Password used for your DocuSign account.
- Click Log In. A message displays confirming that the authentication was successful. If you receive any messages other than a successful one, please contact Momentus Customer Support Services.
- Click OK on the message to close the browser window.
Once consent is provided, continue with the envelope sending process as normal.
Notes:
- Providing consent for different Enterprise users using the same Docusign account will create conflicting tokens. Each user should have their own DocuSign account using the email address associated with their Enterprise User ID.
- If a user does not trigger the integration by sending a document for electronic signature for 30 days, the token will expire and they will be required to Provide Consent, again.
Comments
0 comments
Please sign in to leave a comment.