How does it work?

S4S uses a single license to access the Salesforce API and then caches the collected data for use with a .NET application. The S4S connector is essentially a wrapper for the Salesforce API with a number of additional features to facilitate the rapid development of Salesforce application.

Sitecore for Salesforce Security Connector (SC)

Look at the associated diagram when applying these use cases:

Use Case A – A Salesforce user creates a Contact in Salesforce and assigns login credentials to the Sitecore CMS website

• In Salesforce, a user creates a Contact in an Account.
• In the Sitecore section of the Edit Contact page, the user is allocated CMS login credentials.
• The Contact is made aware of the credentials by email or other means.
  

Use Case B – An anonymous user logs in to the Sitecore CMS website using credentials set up in Salesforce

• An anonymous user who, in Salesforce, is a Contact with assigned credentials, logs in.
  
• In the Sitecore CMS, the user navigates to the Edit My Details page and updates his/her profile details.
  
• Updated details are passed to Salesforce via S4S and the associated Contact is updated.
  

 

 

Sitecore for Salesforce Data Connector (DC)

Look at the associated diagram when applying these use cases:

Use Case C – An anonymous user gets a list of Salesforce documents

• An anonymous or authenticated user navigates to the Documents page.
• Page event causes S4S to call Salesforce and ask for the a document list (from the Documents tab).
• The list is placed into a cache on the Sitecore CMS web site.
• The required data from cache is rendered to the users screen.
  

Use Case D – An anonymous user views a document listed on the website's Documents Page

• Customer A comes to the web site for the first time and registers on the registration form.
• Using S4S, Lead L is created in Salesforce using the registration details.

  

Sitecore for Salesforce Report Connector (RC)

Coming soon ...