SigningHub supports the mapping of specific fields for nine Salesforce entities. See the following table for the supported entities and their fields for mapping. Each entity in a column is followed by their supported fields:

Supported Salesforce Entities and Their Fields for Mapping

Fields 

Salesforce Entities

Opportunities

Campaigns

Leads

Accounts

Contacts

Quotes

Orders

Cases

Contracts 

Name1

Name1

Name1

Name1

Name1

Name1

Name1

Cell Number1

Name1

Close Date2

Is Active3

Email1

Account Number1

Email1

Description1

Order Number1

Description1

Start Date2

Description1

Actual Cost5

Address1

Site1

Title1

Email1

Account Number1

Contact Mobile1

End Date2

Quantity5

Budgeted Cost5

Annual Revenue5

Annual Revenue5

Phone1

Expiration Date2

Effective Date2

Contact Email1

Contract Number1

Is Private3

Description1

Company1

Billing Address1

Fax1

Fax1

PO Date2

Contact Phone1

Description1

Next Step1

Start Date2

Description1

Description1

Description1

Phone1

PO Number1

Closed Date2

Billing Address1

Lead Source4

End Date2

Fax1

Number of Employees5

Department1

Quote Number1

Is Reduction Order3

Created Date2

Company Signed Date2

Stage4

Expected Revenue5

Mobile Phone1

Fax1

Mailing Address1

To Address1

Shipping Address1

is Escalated3

Customer Signed Date2

Type4

Type4

Phone1

Is Partner3

Mobile Phone1

To Name1

Contract Name1

Comments1

Customer Signed Title1














Status4

Title1

Phone1

Lead Source4

Shipping Address1

Contract End Date2

Subject1

Shipping Address1












Website1

Shipping Address1












Shipping Name1

Billing Address1

Status4

Special Terms1

Lead Source4

Website1

Is Syncing3

End Date2

Priority4

Status4

Industry4

Type4

Tax1

Activated Date2

Case Origin4

Owner Expiration Notice4

Status4

Industry4

Total Amount5

Status4

Type4






Rating4

Rating4

Discount %5




Case Reason4

Clean Status4

Ownership4

Status4


Field Legends:

  • Field1 refers to the "Text" type fields. 
  • Field2 refers to the "Date" type fields.
  • Field3 refers to the "Checkbox" type fields.
  • Field4 refers to the "Select List" type fields.
  • Field5 refers to the "Number" type fields.



Add a field mapping

  1. Login into your Salesforce account with a "System Administrator" profile.
  2. Click the "App Launcher" icon in the top left corner and select "View All". 


  1. Locate and select "SigningHub Admin"





  1. The administration section of SigningHub for Salesforce will appear, click the "Document Fields Mapping".




  1. The "Document Fields Mapping" screen will appear. Click  from the grid header. 



  1. A screen will appear to input mapping details. Specify the details accordingly and click the "Save" button.
    See the below table for fields description.




Document Fields Mapping

Fields

Description

Entity Type

This drop down will list all those Salesforce entities which SigningHub supports for fields mapping. Select an entity (i.e. Opportunity, Contract, Leads, etc.) whose field is required to map with a document form field.

Entity Field

This drop down will list all the fields of selected Salesforce entity (above) which SigningHub supports for mapping. Select a field which is required to map with a document form field.

Form Field Type

This is the read-only field to display the type of entity field (selected above), i.e. Text, Checkbox, Date, Select List, etc. Ensure that the types of both the entity field and the document form field (with which mapping is required) are the same. 

Form Field Name

Enter the name of document form field (shown under the Field Properties dialog) that needs to map with the selected entity field (above), i.e. OppCloseDate. See the below heading as how to get a form filed name.
Whenever a PDF document with the same form field is shared from this (above selected) Salesforce entity, SigningHub will automatically pick its field's data and populate it in the respective form field of document.

Auto Sync

Tick this check box to update the mapped field (value) of Salesforce entity according to the changes done on the document fields content. In this way, when a Salesforce user changes the pre-populated content on the document form field, the same changes will be saved on the mapped field of Salesforce entity as well.



How to get a form field name?

  1. Open your PDF document in a PDF editor that supports form fields editing, i.e. Acrobat Acrobat DC.
  2. Select "Prepare Form" and edit the form field which is to map with a Salesforce entity field, and open the "Field Properties" dialog.



  1. Now look for the "Name" field inside the "Properties" dialog. You can also enter a customised name for a form field. Copy this name and enter in the "Form Field Name" field of the "Document Fields Mapping" screen above.
  2. When this document is signed, the Salesforce "Close Date" will be added to the "OppCloseDate" form field in the PDF


Field ​Mapping Rules:

  1. The names of document form fields (i.e. OppCloseDate, OppName, etc.) should be correctly specified against the Salesforce entity fields that need to be mapped. 
  2. The type of Entity field and the type of document form field with which mapping is required, should be the same, i.e. A 'Text' field should be mapped only with a 'Text' field, a 'Select List' field should be mapped only  with a 'Select List' field, and so on. 
  3. When ticked, the "Auto Sync" feature will work at the time of document sharing and document signing both.