There are several modules in Drupal that act as a way to integrate Salesforce and Webform. Ideally, we'd only have one, but this page attempts to point them out and highlight some differences. At some point, perhaps for Drupal 8, we'll be able to merge all of these.
We can't merge this functionality into the Saleforce API module because the maintainers believe it should be in another module. See #1101632: Include webform support for details.
Feature | Salesforce Webform Integration | Salesforce Webform Data Integration | Webform / Salesforce Integration | Salesforce Webform Map | Salesforce Webforms |
---|---|---|---|---|---|
Created | 2009-04-26 | 2008-08-21 | 2012-08-30 | 2014-09-09 | 2014-07-10 |
Drupal 7.x | |||||
Drupal 6.x | |||||
Users (as of 2016-06-20) | 0 | 207 | 20 | 5 | 269 |
Last update | 2013-10-01 | 2013-03-05 | 2015-12-28 | 2014-09-15 | 2016-06-17 |
Maintenance Status | Minimally maintained | Actively maintained | Minimally maintained | Minimally maintained | Actively maintained |
Development Status | No further development | Under active development | Maintenance fixes only | Maintenance fixes only | Under active development |
Documentation | None | README | None | README | Web |
Salesforce API versions | 2 | 6.x-3.x: 3, other branches: N/A | 2, but code for 3 exists | 3 | 3 |
Webform versions | ? | ? | ? | ? | 3, 4 |
Issues about module duplication
- In the Salesforce Webform Integration issue queue:
- In the Salesforce Webform Data Integration issue queue:
- In the Webform/Salesforce Integration issue queue:
- In the Salesforce Webform Map issue queue:
- In the Salesforce Webforms issue queue:
Blog posts related to the above modules
- Drupal-Salesforce Integration: A State of the Union, pt. 1
- Salesforce with Drupal in Three Easy Steps
- Integrating Drupal Webforms with Salesforce
Module-specific background and notes
Salesforce Webform Integration
To be filled in.
Salesforce Webform Data Integration
To be filled in.
Webform/Salesforce Integration
From the project page:
This project was created out of need for Webform and Salesforce integration for D7. Neither Salesforce Webform Data Integration nor SF Webform accomplished this for D7 at the time.
The main difference between this module and Salesforce Webform Data Integration is how they handle Salesforce submissions - this module relies on Salesforce API module while Salesforce Webform Data Integration requires downloading and including the Salesforce API toolkit.
Salesforce Webform Map
The module was created, because what was needed by the client in question was a possibility to setup the mappings themselves and no other module was stable enough at the time to work with salesforce suite. It is a very simple module, which just pushes the salesforce data to an entity. Especially the use case of anonymous vs. authenticated responses and having the form node itself be the campaign was missing at the time this module was written.
It might be that Salesforce Webforms solves this now in a better way, however this is just a 160 lines of code module which uses the normal entity mappings of Salesforce Suite, hence it can be used to create complex scenarios in a programmatic way. It is especially powerful in combination with entityform.
Salesforce Webforms
This module was created because of a need to drive select lists within the webform from Salesforce picklists, as well as pushing the collected data into Saleforce objects.
Key features:
- Leverages the Salesforce Suite project for connecting to Salesforce
- Picklists and multi-select picklists can be exposed as select lists on webforms presented to end users.
- Dependent picklists are supported, allowing the range of possible values to be filtered based on a controlling list, defined in Salesforce. If no valid options remain, the entire control is automatically hidden.
- Picklist values can be filtered by the form administrator, eliminating otherwise valid values. This can be useful if some picklist options are available to internal users within Salesforce, but should not be presented to end users of the Drupal form.
- Multiple Salesforce objects can be created/updated from a single form
- If multiple objects are created/updated, then the ID of earlier objects can be used in subsequent objects. For example, if a form creates a contact, and a support case for that contact, then the newly created contact ID can be automatically associated with the new case.
- Key fields can be specified to allow updating of existing records rather than creation of new records, where possible
- Data written to Salesforce can be combined from multiple webform fields, using the same pattern used when using webform email templates.