The presentation I have given at DreamForce about how eSignature can transform your business processes. It concentrates on the top three use cases that organizations should look at first and describes how DocuSign helps you implement those.
2. Synopsis eSignatures are transforming business processes all over the world. What are the most effective ways to keep agreements in the cloud? We will go through the patterns for implementation and deployment on Sales Cloud and force.com platform.
30. Automate Sending Envelopes Prerequisites A customizable system Standard contracts Access to a developer team Value Proposition Make sending for signature a one step process Increase compliance Integrate with existing workflow
31. Download Documents and Status Prerequisites Document storage – File server, CRM system or a database Value Proposition Push data collected during signing to another data store Get instant updates from our service Use your own CRM or imaging system to manage docs Integrate with existing workflow
32. Embedded Signing Prerequisites A customer facing website Access to a developer team Value Propositions Signers never have to leave the customer portal Instant status updates and document Instant data updates from DocuSign to the customer’s database Tight integration with existing workflow
33. Manage User Rosters Creating Users with CreateAccount API Send on Behalf-Of One global user
34. DocuSign Marketplace Listing of applications that add value to the DocuSign service Being included in the DocuSign Marketplace gives you access to reviews, download statistics and greater visibility Getting certified gives you the option of being included in the DocuSign Marketplace!
35. Certification: Why? Important change from the demo environment to production environment Need to ensure that the behaviors that occur in development are sustainable and scalable Confirm that the application complies with certain guidelines and standards Most of all, we want to position you for success!
36. Certification: When? When certification is necessary Your integration with DocuSign is near complete, Your product is ready to go live, and You are certain that there will be no major behavioral changes to your integration with DocuSign When certification is not necessary You have made small changes to your integration, or You have made changes to parts of your product that do not affect the integration
37. Resources to Get You Started SDK: https://github.com/docusign/DocuSign-eSignature-SDK Dev community: http://community.docusign.com API guide: http://www.docusign.com/p/APIGuide/APIGuide.htm Code walkthroughs and information posts: http://www.docusign.com/blog/category/devcenter/ DevCenter: http://docusign.com/devcenter Twitter: @DocuSignAPI
Notas del editor
All the API and UI goes to the same business objectsAll the data is normalized by DocuSign CoreYou can start the transaction with one entry point and then use a different interface to manage and retrieve
- Sending and Signing function groups work together – you cannot use the signing group without the sending groupAll other function groups may be used independently to manage different parts of the DocuSign processCommon patterns are…
Call out the ability to create drafts and why this would be desirable (embedded sending)Note how the managing function group is one of the most powerful but most neglectedEmphasize post-processing capabilities and implications on guidelines (multiple downloads)Talk about administrative function group and applicable scenarios
Marketplace is the list of "Certified Applications" that's a benefit of having your application certified. Get exposure to the full set of DocuSign usersGet reviews and ratings from users on the world’s only eSignature marketplace
Some of the common questions are: "but my application is really tiny, why do I need to certify?" "my application is just for me, can I just use it on my account?"