Improve documentation
Add properties mapping to Salesforce connector documentation
@@ -90,9 +90,26 @@ Salesforce REST API to retrieve the limits of the Salesforce API.
+
Both URLs are password protected by the Apache Unomi (Karaf) password. You can find this user and password information
in the etc/users.properties file.
-+
-. You can now use the connectors's defined actions in rules to push or pull data to/from the Salesforce CRM. You can
-find more information about rules in the <<concepts.adoc,Concepts>> and the link:getting-started.html[Getting Started] pages.
+
+You can now use the connectors's defined actions in rules to push or pull data to/from the Salesforce CRM. You can
+find more information about rules in the <<_concepts,Concepts>> and the <<_getting_started_with_unomi,Getting Started>> pages.
+
+==== Properties
+
+To define how Salesforce attributes will be mapped to Marketing Factory profile properties, edit the following entry using the pattern below :
+
+[source]
+----
+sfdc.fields.mappings=myMarketingFactoryProperty1<=>mySFDCAttribute1,myMarketingFactoryProperty2<=>mySFDCAttribute2
+----
+
+Please note that Salesforce needs the company and the last name to be set, otherwise the lead won't be created.
+An identifier needs to be set as well. The identifier will be used to map the Marketing Factory profile to the Salesforce lead. By default, the email is set as the identifier, meaning that if a lead in Salesforce and a profile in Marketing Factory have the same email, they'll be considered as the same person.
+
+[source]
+----
+sfdc.fields.mappings.identifier=email<=>Email
+----
==== Hot-deploying updates to the Salesforce connector (for developers)
