A complete SugarCRM and Docusign integration which allows us to quickly pull data from SugarCRM modules like Account, Contact, Lead, Prospect, User, Quote and Contract and then send them out for signature directly from SugarCRM. The signed document's fields are then returned to SugarCRM and attached to the corresponding SugarCRM records. The signed documents are returned to SugarCRM and attached to the document envelope.
FAQ
[1] We are facing the Polling violation error while moving to the Production. How we can solve it?
The Docusign integration goes through different stages from Demo -> to Production.
Initially, when you start testing the integration, You will have the Docusign Demo account, kindly keep the environment in "Demo" during that time.
Once you have tested thoroughly and want to actually send documents for signature to customers, submit the Docusign integration for Production approval on your Docusign interface. Before submitting for "Production review" on Docusign, you have to follow the below steps in CRM.
(A) Please remove all the demo Docusign records from the CRM. (There can be a case where you have sent a document for signature, which is not being signed. So when you submit for review, Production environment API tries to get an update of that demo API record and could lead in multiple API call waste, and may result in polling violation rule of Docusign)
(B) Set both the Scheduler "Update Docusign document status" & "Get Docusign templates" to update the Docusign status and Template once a day. Or make those scheduler statuses to "Inactive".
(C) Change the environment to "Submit for Review".
(D) Make 20-25 successful Docusign API Calls(Send for Signature) while it is in "Submit for review" status.
(E) Once Docusign review has been passed then change the Docusign Environment to "Production" in the CRM.
[2] How do I migrate the integration to support oAuth2.0?
- Please download the latest package with version 3.0 or greater. If you have a customized package from the Urdhva Tech then reach them at on below address. They will look into it and if feasible provide you with the modified package.
Email:contact@urdhva-tech.com Skype:urdhvatech
[3] How do I switch to Docusign Production?
The Docusign integration goes through different stages from Demo -> to Production.
Initially, when you start testing the integration, You will have the Docusign Demo account, kindly keep the environment in "Demo" during that time.
Once you have tested thoroughly and want to actually send documents for signature to customers, submit the Docusign integration for Production approval on your Docusign interface. Before submitting for "Production review" on Docusign, you have to follow the below steps in CRM.
(A) Please remove all the demo Docusign records from the CRM. (There can be a case where you have sent a document for signature, which is not being signed. So when you submit for review, Production environment API tries to get an update of that demo API record and could lead in multiple API call waste, and may result in polling violation rule of Docusign)
(B) Set both the Scheduler "Update Docusign document status" & "Get Docusign templates" to update the Docusign status and Template once a day. Or make those scheduler statuses to "Inactive".
(C) Change the environment to "Submit for Review".
(D) Make 20-25 successful Docusign API Calls(Send for Signature) while it is in "Submit for review" status.
(E) Once Docusign review has been passed then change the Docusign Environment to "Production" in the CRM.
[4] We have purchased the Docusign integration from the SuiteCRM Store. Do we need to buy a Docusign License?
- You will have to purchase the plan from Docusign.
[5] While using the CRM PDFTemplate, we are getting the {DS BOX} variable into the Docusign document.
- Please make the font color white for the {DS BOX} into CRM PDFTemplate. Then it will not be shown in the Docusign document.
[6] Which field types support the Docusign API Library?
- The Docusign API client library supports text, checkbox, and radio types.
Saving Comment...
