Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Introduction

This document covers the installation steps needed to install and configure the FuseIT S4S connector. A separate document is available for installing S4S ECM.

IMPORTANT: The connector has a number of install options and some may not be necessary for your requirements. Please see the Install Options notes below.

Audience

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 directly to the FuseIT S4S Packages installation and setup. It does not provide information on setting up and configuring Salesforce or Sitecore.

Install Options

The connector has a number of install options that you need to consider:

  • Basic Install: This is required. 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 typically execute this functionality in Sitecore using custom code (see examples in the provided Starter Kit and support documentation). Note that S4S pushes and pulls information to and from Salesforce after a Sitecore event (button click, page load, scheduled task etc.) has occurred.
  • Web Forms for Marketers: The Basic Install assumes your Sitecore installation has the Web Forms for Marketer package installed. You need to install Sitecore WFFM first then install the S4S Core package. If you are not using WFFM, see the following section on how to exclude WFFM.

There are two Submit Actions available for WFFM to push information to Salesforce. In the Sitecore tree these can be seen at

/sitecore/system/Modules/Web Forms for Marketers/Settings/Actions/Save Actions

The default S4S Save Actions are:

  • S4S Generic Mapping: Map 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: Map WFFM fields to a Salesforce contact or lead. Include in the push the Salesforce, Sitecore DMS analytics. This requires 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. See more about this in Section 9.9 of this document.

If one of these Save Actions is selected, the WFFM form will appear in the S4S Mapping wizard accessible from the Sitecore Start menu.

Additional custom Save Actions can be built to improve WFFM validation and functionality when connecting to Salesforce.

  • Security Connector: This is optional and requires a package be installed in Salesforce. This install lets users 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 stored in Salesforce but appears in Sitecore in the “salesforce” domain. After installing this option it is possible to control the Sitecore user membership information, profiles, roles and the Sitecore landing page directly from Salesforce. Note there are two ways to implement roles:
    • Single role using the Salesforce Account to specify the Sitecore role  
    • Multi-role using fields in the contact record to specify the Sitecore role

It is also possible to expose Salesforce Campaign Members as Sitecore users by setting up a separate domain for this provider. This functionality is provided for purposes such as reporting, emailing, etc and as such, these users are read only and are not used for authentication purposes.

  • S4S ECM: This is optional and requires a package be installed in Salesforce. The ECM functionality is detailed in a separate document. This install allows Salesforce Campaigns and associated member lists to be pushed to the Sitecore ECM module for processing and/or dispatch. It has a range of other features noted on the FuseIT website.

Excluding Web Forms for Marketers

The Basic Install of S4S assumes you have the Web Forms for Marketer package installed. If you are not using WFFM, you should remove WFFM from the installation package before installing S4S. To do this, open the core zip file and note the Web Form for Marketers item in the following node:

Sitecore For Salesforce-Core-1.7.13344.1.zip\items\master\sitecore\system\Modules

You cannot delete directly delete this item without a security message so extract the entire zip to a new unzipped Sitecore for Salesforce - Core-x.x folder then drill down and delete the WFFM item. Next delete package.zip out of the original zip file and drag the entire modified package.zip across to the original. Install the modified zip as normal.

  • No labels