The PassThru and Self Service models are similar in that they enable a customer to host and control the steps of sending a Quik! form to DocuSign. The difference is that the Self Service model gives the customer 100% control over the integration with DocuSign via the QuikESignTransport project and the PassThru model only exposes control at the beginning of the transaction via a customer's web page that receives the form data and passes it through to Quik!.
The PassThru model works by passing data from the Quik! form to a web page that the customer hosts. We provide a sample page (see sample web page in DocuSign_PassThroughWS_SamplePartnerProject.zip) that the customer can use to build their own page or they can use the QuikESignTransport without modifying it.
Requirements
Modify the QuikESignTransport and the sample pass through web page to consume the RESTful web service for DocuSign (i.e. the new REST version of this service: https://websvcs.quikforms.com/Docusign/ESignWSVersion/5400/ESignForPartnersWS.asmx).
QuikESignTransport.PassThru Project
...
After hosting this sample project, or any similar one, into your server, set the URL in the SignURL property of the ESignTypeDocusign object. Below you can see the minimum code requirement
string domainPath = "https://your.domain.com"; ESignTypeDocusign docusign = new ESignTypeDocusign { SignURL = domainPath + "/sign/passthru", SignEnvironmentID = ESignTypeDocusign.SignEnvironment.DocuSignDEMO }; objQFE.SetESignType(docusign);
Note: "/sign/passthru" is the controller's method route. If the sample project is used as is, then that value must be set.