Blog
Home/

OLD DS DEV SPOT - DO NOT USE

Matthew Lusher

Matthew Lusher

Sr. Programmer Writer

Summary1 min read

Jim specializes in Salesforce integrations, leveraging Docusign's eSignature REST API to customize document workflows.

Developer Spotlight: James Gordon, Cloud Notions

Developer Spotlight: James Gordon, Cloud Notions

James Gordon is a graduate of Indiana University and the Auburn University MBA program. He's worked as a business analyst, developer, project manager, and architect over the last 20 years, in several technology ecosystems: .NET, Java, Oracle, Adobe, Salesforce, and others. Currently he is a Systems Architect at Cloud Notions, a Salesforce.com consulting partner agency.

Docusign is one of the top apps on the Salesforce AppExchange, so Jim has worked with Docusign at many clients. A common project might be a custom Visualforce page that uses complex Apex logic to adjust the eSign template, recipients, or payments tags. For example, if the contract is a renewal with no balance due, Jim's Apex logic might remove the Docusign Payments portion of the template. Another recent project included using Apex code to call the Docusign eSignature REST API to reach into previously signed documents and extract signer-entered text fields to create additional records in Salesforce.

When Jim isn't building something awesome, he enjoys reading and spending time with his wife and daughter. He also has a newfound passion for mountain biking, so you will often find him on riding local trails. You can reach Jim on LinkedIn.

Matthew Lusher

Matthew Lusher

Sr. Programmer Writer

More posts from this author

Related posts

  • API Success

    Docusign for Salesforce: How to Create a Lookup Relationship Between Docusign Status and Salesforce Objects

    Jesse Morgan

    Jesse Morgan