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 17 Next »

Introduction

This information covers the installation steps needed to install and configure the FuseIT S4S connector. Separate information 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 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 to installing the FuseIT S4S Packages and does not provide information on setting up and configuring Salesforce or Sitecore.

S4S Installation Overview

Basic Install

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 pushes and pulls information to and from Salesforce after a Sitecore event (button click, page load, scheduled task etc.).

IMPORTANT: The basic install assumes your Sitecore installation has the Web Forms for Marketer (WFFM) package installed. You need to install WFFM first, then install the S4S Core package. If you are not using WFFM, see the section below on how to exclude WFFM.

Web Forms for Marketers (WFFM)

If you have the Sitecore WFFM module installed and you want to push WFFM form data to Salesforce, S4S has a mapping wizard to make this easy.

When creating the Sitecore WFFM form choose the required custom Save Actions to push the form data to Salesforce. The installed Save Actions are:

  • 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 data associated with the visitors 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

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

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 custom Save Actions can be built to improve WFFM validation and functionality when connecting to Salesforce.

Security Connector

The Security Connector is an option that requires a package to 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 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:

    • 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).  

Campaign Members as Sitecore Roles

Another option is 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. More comprehensive and bi-directional functionality is provided by the S4S ECM module. 

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 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.

S4S ECM Installation Overview

This S4S Email Campaign Manager is a paid option that requires a package be installed in Salesforce.  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.

  • No labels