Skip to main content
S
Community Manager
SimonATSCommunity Manager
Community Manager
February 12, 2014
Question

Sending Adobe Acrobat Sign agreements from Custom Objects in Salesforce

  • February 12, 2014
  • 13 replies
  • 32020 views

In this tutorial, l I’ll go through how to:

  • set up a document template with text tags and add it to the SFDC library
  • create an Agreement template
  • create a customer send for signature button and add the button to a Custom Object page layout
  • create a merge mapping  to merge fields data from the Custom object into an EchoSign agreement
  • create a data mapping to map field data from the EchoSign agreement back into the custom object in SFDC

 

The tutorial is the attached PDF, the Word document is a sample template document used in this tutorial.

To download the attachments below, login the forum first, or use the link below.

 

Sending EchoSign agreements from Custom Objects in SFDC-Lightning edition.pdf

Sending EchoSign agreements from Custom Objects in SFDC.pdf

Your Custom Object document.docx

 

Note that older versions of these document use the old method to add custom links for custom buttons. Links should be updated like this example:

{!URLFOR('/apex/echosign_dev1__AgreementTemplateProcess', null, [masterId = Opportunity.Id, templateId='a024J000002LuyBQAS'])}

This topic has been closed for replies.

13 replies

Show previous replies
Janakanath
Janakanath
Participant
April 27, 2015

I ran into an issue when Sending from a Custom SF object.  I sent the file and when it returned to Data Mapping Failed.  Attempted to map to a related object reference which was not set on the agreement: Event_Detail__r Failed to map data field: System.NullPointerException Attempt to de-reference a null object (echosign_dev1) 613

When I look at the agreement template I have three options, Account,opp, and Contract.  But I am trying to reference it back to my Custom object.  I don't really know what to do next.

S
Community Manager
SimonATSCommunity ManagerAuthor
Community Manager
May 8, 2015

Jason,

I know this is a bit late, but check out the section in the guide on map data in agreement field. That's how you reference the agreement to your custom object.

B
BRC-Perc
Participant
May 29, 2014

Thanks for the instructions! Any advice for the button if it opens the agreement visual force page but includes the error "Invalid token"? I've checked the ID (it's the 15 digit ID from the URL of the Agreement Template record) Thanks!

S
Community Manager
SimonATSCommunity ManagerAuthor
Community Manager
May 29, 2014

Hi there,

Ensure there's no space in the link and don't forget the = where needed.

B
BRC-Perc
Participant
May 29, 2014

Yeah, no spaces, matches exactly except our custom object API name and our Agreement Template ID (that is the template ID you mean in the instructions, right? Not the Template Document?) Thanks!

A
Anonymous
March 18, 2014

Hi Simon,

Thanks for the guide. A few questions:

Where do we create the custom object? Is this necessary to do even if we've installed echosign into Salesforce?

You discuss it here:

Give the template a name first. Next set the master object. In this case it,it is the API name of the

custom object, in this case its myCustomobject__c.

Thanks,

Kai

S
Community Manager
SimonATSCommunity ManagerAuthor
Community Manager
March 19, 2014

Hi Kai,

The custom object is referring to a custom object in Salesforce. You only need it if you decide you need a custom object to hold your data in SFDC. if you are using standard Salesforce object like Account and Opportunity you can just add an EchOsign button to these.

In my example i called the custom object 'MyCustomobject'. in your Org you may have a custom object called 'Services'. In this case you'd add the following for the masterobject

Services__c

If you want to send from a standard object like Opportunity, then just add Opportunity as the master object on the EchOSign agreement template.

See also the EchoSign for Salesforce customization guide on how to setup templates.

Simon

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices