The AssureSign for Salesforce control supports mapping data from Salesforce objects to parameters used to populate data in an AssureSign Template. The AssureSign for Salesforce control can automatically pull specified Salesforce object field values from the page on which it resides by specifying these field names in parameter tags from within an AssureSign template.
This mapping process can always be done manually during the parameter population stage of the document setup process by selecting the desired field from the field list or by typing the desired value right into the parameter value textbox. However, for cases when the value of a parameter always relates directly to a field on a Salesforce object, this mapping process can be automated to save time.
This will be most useful for situations where multiple documents need to be sent and the same Salesforce object fields are always mapped to the same parameter fields in each document. Being able to use Salesforce object fields as parameters and automatically having these field values pulled from the Salesforce object will make the process of inputting new document parameters much less repetitive and will reduce the amount of time needed to submit a document.
Field mappings can be created by setting the "Tag" value of AssureSign template parameters with the appropriate "AssureSign Parameter Tag” for the field you would like to map.
To access a list of available Salesforce fields:
- Click the All Tabs arrow to bring up the list of available tabs.
- Click on the tab labeled AssureSign Setup.
- Click on the Integration sub-tab.
To select a specific Salesforce field:
From the Object browser, choose a Salesforce object from the list. The available Salesforce fields for that object will be displayed.
Find the field you would like to use from the list displayed.
NOTE: Nested parent object relationships for the currently selected object are shown in the list for the selected object as[Object Name] .
For example, a Contact belongs to, or is associated with, a parent Account, and the Account to which it is linked is identified by the Parent Account ID field. So to view the fields of an Account to which a Contact is related by a parent/child relationship:
- Choose a root object of [Contact]
- Select the [Account] object
NOTE: The list of available fields will vary based on the Salesforce object the AssureSign control is used with (the specific object page the AssureSign control is placed on). Consequently, use the tagging mechanism with care if you intend on using the same AssureSign template to send documents for multiple Salesforce object types.
Copy and paste the corresponding "AssureSign Parameter Tag" string, and – within the AssureSign site while editing the Template parameter which should receive the value – paste the value in the "Custom Tag" text box.
If the tag is correctly entered, the parameter field values will be automatically populated from the Salesforce object identified by the AssureSign Parameter Tag when submitting a new document through the AssureSign Salesforce tool as shown below.
Custom Object Field Mapping
If your organization uses custom Salesforce objects they will not show up in the object list on the integration tab shown above. Field mapping can still be set for fields on the custom object using the following syntax:
[object API name].[custom field API name]
EXAMPLE: A sample custom object field mapping may look something like this:
The object API name can be obtained by viewing the object in the custom object setup section. It may or may not contain a namespace prefix based upon your organizational settings.
Custom Salesforce Lookup Field Mapping
Salesforce lookup fields are fields that create a relationship between objects. They allow you to pull a value from one object into another. The images below show a lookup field on the Contacts object which pulls values from the Leads object.
If your organization uses lookup fields, the values in the fields can be pulled for object field mapping as well using the following syntax:
[object name].[lookup field pointer].[field]
The lookup field pointer is the API name of the lookup field, replacing the trailing c with an r. For instance, if the lookup field API name is namespaceLookupField01c then the lookup field pointer will be namespaceLookupField01r.
The field is the actual field reference you wish to pull the value from. If you wanted to pull the value you see in the textbox, field would be replaced with Name.