...
This information covers the installation steps needed to install and configure the FuseIT S4S connector. You should NOT install everything - several features are "either/or".
 | IMPORTANT: The connector has a number of install options and some may not be necessary for your requirements - many features are "either/or". Please see the Install Options below and/or the S4S Installation Chart. |
...
The audience for this section is developers and implementers with experience in installing and configuring Sitecore. Experience with Salesforce is not required.
...
...
IMPORTANT: This document assumes that you have experience in managing Sitecore. Please see the Scope notes below.
Scope
This section describes instructions that apply to installing the FuseIT S4S Packages and does not provide information on setting up and configuring Salesforce or Sitecore.
...
The basic install requires a package to be installed into Sitecore and some minor Salesforce customization. Once completed you can create, read, update and delete Salesforce objects from Sitecore (like Contacts, Leads, Opportunities, Documents, Cases or custom objects). You can execute this functionality in Sitecore using custom code (see the Starter Kit or examples in this document). Note that S4S typically pushes and pulls information to and from Salesforce after a Sitecore event (button click, page load, scheduled task etc.).
...
- S4S Generic Mapping: This Save Action maps WFFM fields to any object in Salesforce. For person objects you can use the wizard to automatically add a new Salesforce lead or contact to a Salesforce campaign.
- S4S Push Visitor: This Save Action maps WFFM fields to Salesforce Contacts or Leads only. This action pushes the form data to Salesforce, and the Sitecore DMS xDB data associated with the visitors visitor's activities on the website. This requires several custom receiver fields in Salesforce. When a Contact or Lead is pushed to Salesforce a “S4SPersistedLogin” cookie is also created on the client. You can use this to render a unique website experience if the visitor returns to the website.
In the Sitecore tree, Save Actions are installed at
...
If one of these Save Actions is selected, the published WFFM form will appear in the S4S Mapping Wizard which is accessible from the Sitecore Start menu. Additional Developers can build custom Save Actions can be built to improve WFFM validation and functionality when connecting to Salesforce. There is a See the dedicated section that discloses to learn more about the S4S Web Forms for Marketers functionality.
...
The Security Connector is an option that requires a package to be installed in Salesforce. This install lets users visitors log into the Sitecore website using credentials stored in a Salesforce Contact or Lead record. The Security Connector overrides the ASP.NET membership provider so user data is only stored in Salesforce but appears in Sitecore in the “Salesforce” domain. After installing the Security Connector it is possible to control the Sitecore user membership information, roles and profiles from Salesforce. Note there are two ways to implement roles - choose only one:
- Single role using the Salesforce Account to specify the Sitecore role. All contacts that belong to the Account will be Sitecore users in a Sitecore role with the same name as the Salesforce Account.
- Multi-role using fields in the contact (or lead) record to specify the Sitecore role. One or more Sitecore roles have the same names as selections in a custom multi-pick list in the Salesforce contact (or lead). Multi-role is more flexible than single role.
Campaign Members as Sitecore Roles
...