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.
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
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.
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!
Ensure there's no space in the link and don't forget the = where needed.
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!
Oh, I solved it. It wasn't the custom button URL--it was a malformed variable in the body of the agreement template email. Thanks for answering so quickly. I really appreciate it!
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.
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.
thanks for the nice explanation.
I was trying to add 'Data field mapping' for Agreement form fields to Salesforce records. Below are the steps i followed
Created a new record from 'Echosign data mappting' tab and selected an agreement for "Import fields from" . When i click the 'Import from fields" button, it is giving error:The call to the EchoSign web service call to retrieve the agreement document key returned an error message 'null' and error code 'INVALID_API_KEY'
When i click the 'add mapping' button, and selected 'Echo sign form' field, then nothing is enabled to input or select a value for 'Source value' option.
Hi Simon, Thanks for your helpful guide, however, I am seeing an error with my custom object:
System.NullPointerException Attempt to de-reference a null object (echosign_dev1) 405
In my Agreement Template, I specified Master Object Type "InstProds__c", the API name of my custom object "Installed Product".
Results vary based on my Merge Map, where I am not clear on use of this section:
Map Salesforce Product Line Items Fields to Adobe Document Fields
If I leave Selected Object without selecting a reference object, I get the above null pointer exception.
If I Add a Field Mapping, and choose Selected Object, Installed Product (Reference), it gets into an endless chain of references, as shown in this image. How is this supposed to work?
Did you ever get an answer as to how the field works? i am trying also to display opportunity products fields on my documents, but nothing happens no matter how many times i try.
product Line items come from the Opportunity, so that can only work when sending from an opportunity using opportunity as the master object in the Agreement template record. see also the relevant chapter in the customization and install guide on product line items. (starting page 29 and starting at point 7 on page 32 of the v17 guide, the guide is linked under the resources tab in the esign services admin tab (again assuming v17 or older is being used))
So in your case don't add anyhing there. Only use "Map Salesforce Object Fields to Document Fields", leave product line items alone when using custom objects as master object.
hanah, see the reference to the guide above.
I'm trying to get the information from 2 custom objects to create Adobe Document. It is not working for me could some one please explain me. Thanks a lot.
The custom protest is alluding to a custom question in Salesforce. You just need it in the event that you choose you to require a custom protest hold your information in SFDC. on the off chance that you are utilizing standard Salesforce protest like Account and Opportunity you can simply add an EchoSign catch to these.
In my illustration, I called the custom question 'MyCustomobject'. in your Org, you may have a custom protest called 'Administrations'. For this situation, you'd include the accompanying for the master object
On the off chance that you need to send from a standard protest like Opportunity, at that point simply include Opportunity as the ace question on the EchoSign assertion format.