Each unique form has its own one or more S4S Cloud Mapping ObjectMappings. This The mapping defines the overall settings for matching form submissions and creating or updating records in Salesforce.
...
Mapping Name | Give your mapping a descriptive name to help identify and distinguish it from others. |
Sort Index | Optional. When a form has multiple mappings, this gives a means of determining the processing order. |
S4S Cloud Identifier | A unique string that S4S Cloud can match against your form submissions to determine when to use this mapping. The easiest way to obtain this is by Capturing Form Submissions. |
Salesforce Object | The type of record that will be created or updated in Salesforce when this mapping is used. May be almost any standard or custom object. |
Handle Lead Conversion | When the Salesforce Object is set to Lead, S4S Cloud can automatically switch to Contact for converted Leads. Check this box to enable. |
Update Only | To disable creation of new records and only allow updating existing records (when found), check this box. To always force creation of new records, simply omit an ‘Identity Key’ field mapping. |
Identification Lookup | (Optional). If this mapping should generate Visitor records, select the lookup field on the S4S Cloud Visitor object that references the configured Salesforce object above (must match). |
Condition Matching | If the mapping has multiple conditions applied, S4S Cloud can require them all (AND) or any one (OR) to pass. |
| Info |
|---|
S4S Cloud includes lookup fields on the Visitor object for Lead and Contact by default. However almost any other standard or custom object may be used for Visitor identification; simply add a custom lookup field to the S4S Cloud Visitor object and it will appear here. |
...