Integrate DocuSign API with Force.com using REST Web Services

Ramanathan Pachaiyappan, ON24 INC, Senior Software Engineer@rpachaiyappan

Safe harborSafe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other litigation, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

Agenda

1. Why E-Signature for Contracts?

2. Docusign Integration Options

3. Signing Process

4. Discuss Force.com REST Implementation

5. Demo

6. Q&A

Why e-Signature for Contracts?

Traditional Signing – Manual, Time consuming, Scanning/Fedex, Numbers

messed up, Accessibility, Tracking, Visibility & Archive Issue

E-Signature – Simple, Faster, Access Any Where, Reporting, Visibility, Better

ROI, Contract Archive & Search

Types of Signing – Contracts, NDA, Embedded Signing, Job Applications, Real

Estate, etc

We will be focusing on Contract Signing aspect only*

Docusign Integration Options

Use AppExchange package (most popular out of the box solution)

Want a custom workflow with easy of use, consider API Integration (Medium/Large Sales organization)

API Options – SOAP API (been there for while) & REST API (new still beta)

Apex REST

Introduced in Summer 11 release, supports XML, JSON, REST

Comes with Native JSON Parser, Ability to De-serialize by passing Apex Object, Methods to build REST JSON Request (like Java JSON)

Annotations to mark a Apex Method as Web Service Resources (@HttpGet, @HttpPost, @RestResource). Class/Method should be declared Global, Be cautious of Nested Structure Depth (Recursion, Governor Limit)

Apex Javascript Remoting is another cool feature in apex useful for communications between your controller & JavaScript

E-Signature Process*

1. Create and Send Envelope From Envelop (Document based method)

a. Create Envelope with recipients (One or more party involved in signing)

b. Rendered dynamically generated Contract PDF, Create Tab (Place where people sign/initial)

c. Send Envelope by changing Status to “Sent”

2. Track Envelope

3. Void, Re-send, Re-Assign Envelope as needed

4. Templates – Ability to customize look and feel of e-signing email message

5. Security –secret code for singers, phone verification etc

* We will be covering only subset of Docusign API relevant to this session .

Tab, Custom Field

Tab• Placeholder to tell Docusign where signature field or dynamic fields (date) located in

the Document. Example: Sign Here Tab, Date Tab, etc• Tab type enumerations – SignHere, Date, Initial etc• You can force recipient to sign in their respective Tabs easily (using Tab ID/Recipient

ID)

Custom Field• Nice option if you want to tie your envelop with specific information which can be used

later for retrieval, etc.• Example: ContractId, AccountId can be linked with Document using Custom Field.

Demo & Discuss Code

Docusign Connect*

1. Docusign PUSH Update message instead of Poll for collecting Document Status

2. Docusign pushes Document status message upon view, sign, reject, void, etc to your

application

3. Message Style - An XML POST consisting document status to your web application

URL, configured via Docusign Console

4. Salesforce Docusign Connect – We have configuration option available to update

Salesforce custom object with Envelope Status (using Docusign Console)

Docusign Connect Configuration

Summary

a. SOAP API is a good proven option as well, it provides strong data binding, easy to use once you

understand the concepts.

b. REST API got multiple purpose if your considering mobile integrations its comes very handy

c. Docusign released support for base64 very recently (after I reported them issues with REST), the

original demo was bit lengthy, with Base64 support now it looks simple and equivalent to SOAP API

features

d. We have covered one particular Use Case only, Docusign got lot more potential, feel free to explore

them.

Demo & Resources

Demo - Walk through One Click Contract e-Signature

Resources:

Source Code (REST) – https://github.com/ramanathansj/sfdc-docusign-rest

For Salesforce Developer Account, Downloading Apex/Visualforce guides, Questions/Community

http://developer.force.com/

Docusign SOAP & Rest API Resource

http://www.docusign.com/developer-center

Demo Account

https://demo.docusign.net/Member/MemberLogin.aspx

Docusign IODocs (Try before build)

http://iodocs.docusign.com/

Thank You!

Q&A!

Click icon to add picture

* Nandri picture courtesy from internet