DocuSign Production

[shaun-technovation]

• Update email address documents get sent from
• Go Live process:
  • https://developers.docusign.com/docs/esign-rest-api/go-live/

[shaun-technovation]

I was briefly reviewing the go-live process and it mentions that it can take up to 3 business days to complete.

So, I decided to get started on it. I'm following along with this document: https://developers.docusign.com/docs/esign-rest-api/go-live/

I completed this step:

1. Request a Go-Live review in eSignature Admin.

The review passed and the next step I'm stuck on is:

3. After passing this automated review, the key's status changes to Review Passed. Next, you must confirm the decision to Go-Live and select a production Docusign account into which to promote the key. Each integration key in the production environment must belong to a paid or a partner production Docusign account. You can choose an account with a different email address than the one associated with your developer account, if needed. The integration key will be tied to that account for management purposes, but after promotion, the key can be used to make API calls against any account.

We need to "Select the Go-Live account", which would be our production Docusign account. I don't have access to this account. The steps to select the go-live account (copied from the document linked above) are:

• Open the Apps and Keys page in your developer account.
• Next to the integration key you want to promote, select Actions > Select Go-Live Account.
• You are prompted to choose a production account. Click NEXT.
• In the login window that appears, log in to the production account you want to use to manage the integration key using your production Docusign account credentials (not your developer account credentials).
• After logging in, you will be prompted to accept the developer terms and conditions. Note that you may need to enable pop-ups in your browser.
• Next, you will be prompted to select a production account to use to promote the key.
• Go-Live process: Select a production account into which to promote your app.
• After selecting a production account, the key's status will change to Pending Approval. You do not need to take any action at this point. Your key willbe promoted within three business days of reaching this status.

Notice the last bullet point says:

Your key will be promoted within three business days of reaching this status.

[shaun-technovation]

@dboyer

Sorry, I forgot to tag you on this one. I need help w/ the go-live process^. Someone needs to "select the go-live account"^ or I can do it too if I get access to production Docusign.

[shaun-technovation]

Just going over the Go Live FAQ, and it mentions:

The automated process can take anywhere from a few hours to three business days. If your integration completes 20+ transactions in 24 hours that comply with Docusign's resource limits, in addition to having an active live Docusign account and administrator access to the account, the process can take as little as a few hours.

We made 20+ transactions in a 24 hour period^. Anywho, hopefully we'll fall in the "takes as little as a few hours" category.

[shaun-technovation]

We're all set for now!

I was able to link/use our production account for the go-live account. While I was logged in to our production account I also setup the webhook and copied the necessary production keys.

We can use the production keys on QA to test out a real document, or we can just wait until we deploy and test out a real document on production too.

Nothing left to do with this one until we test out a real document to make sure everything is hooked up correctly. Moving this one to the QA column. 👍

[shaun-technovation]

I realized I forgot one key, the client secret. I was able to get it, I logged back into our production account (didn't require 2fa) and grabbed it, then logged out.

Also, all the settings/keys have been added to Heroku for Production.

[shaun-technovation]

Ran into a few more issues getting Docusign to work on Production, documented below. But the summary is that everything has been resolved and we are now able to send documents from our Docusign production account.

JSON::ParserError: 809 was being caused because we were hitting the wrong URL, I added /restapi to DOCUSIGN_API_BASE_URL to resolve this.

[DOCUSIGN] Error sending document - The specified Integrator Key was not found or is disabled. Invalid account specified for user. I double/triple checked our config settings and found DOCUSIGN_API_ACCOUNT_ID had the wrong value, after updating that, that resolved this error.

[DOCUSIGN] Error getting an access token - invalid_request and [DOCUSIGN] Error sending document - One or both of Username and Password are invalid. Invalid access token I refreshed our access token to resolve these errors. These errors are most worrysome b/c the same thing is happening on QA. The access tokens should be getting automatically refreshed. I'm not sure what is going on, but we'll definitely want to keep an eye on these error messages.