Plugin / Gravity Forms Salesforce Add-on

Changelog

3.1.2

• Added: Web-to-Lead setting to choose date formats for date fields (mm/dd/YYYY or dd/mm/YYYY)
• Added: gravityforms_salesforce_object_added_updated action after entry is added or updated in Salesforce using the API
• Fixed: Gravity Forms warnings in admin
• Fixed: Link to API settings when in API Feed configuration

3.1.1 (February 17, 2015)

• Fixed: Warning in Gravity Forms 1.9 about Add-on requiring an update
• Fixed: Loading order of settings tabs

3.1 (December 1, 2014)

• Thank you to @zmonteca for this update. The great new functionality was added by him!
• Added: Use of Sandbox constant
• Fixed: Whitespace consistency
• Fixed: Lots of logging updates for verbosity
• Fixed: Do not process inactive feeds
• Fixed: Ability to sort the order of feeds list
• Fixed: Feed select boxes are all sorted alphabetically now
• Fixed: Localization functionality – added Text Domain information
• Added: Romanian translation – thanks @ArianServ!
• Added: Feed Primary Keys can now be used to update previous records properly.
  • For example, “Form A” has two SF tables worth of data — Contact & Address. You can create an Address feed and a Contact feed. If the Address feed is ordered before the Contact feed in the feed list, you can use the Contact feed’s Primary Key to map to the Address Primary Key. This is helpful to map true relationships in Salesforce.
• Added: Any feed can map foreign keys to Primary Keys, thus mapping rich relationship in SF.
  • For example, Form B has five dependent Salesforce tables worth of data — Contact, Opportunities, Opportunity Contacts, Contact, Tribute. Now you can create a Contact, have it linked to Opportunities. But also create a second Contact and map that as well as the Opportunity to a custom Tribute table. It’s very fancy – see the Frequently Asked Questions for more information.

3.0.6.3 (September 12, 2014)

• Fixed: Removed field var_dump

3.0.6.2 (September 5, 2014)

• Fixed: Issue saving Web-to-Lead settings for Gravity Forms 1.8.10 or higher. Thanks, @twiginteractive
• Fixed: An issue with the OAuth library clashing if the same library is used elsewhere. Thanks, @JasonTheAdams
• Confirmed compatibility with WordPress 4.0

3.0.6.1 (August 18, 2014)

• If you haven’t read the 3.0.5 notes, please do so!
• Fixed: Issue with refreshing Salesforce authorization token

3.0.6 (July 19, 2014)

• If you haven’t read the 3.0.5 changelog notes, please do so!
• Added: Enabled Merge Tag field value support (issue #97)
• Added [API Add-on]: “Form Title” as an option for mapping form fields
• Fixed: Form details were not being properly passed (issue #94)
• Fixed: DaddyAnalytics API names were incorrect for the API integration
• Fixed: PHP warning about calling static functions
• Added: Additional Debugging

3.0.5 (June 26, 2014)

• !!MAJOR UPDATE!! Please read through the changes below.
• API Add-on Changes
  • You will need to update your settings after installing the plugin.
  • The Add-on no longer requires your Salesforce Security Token and Email.
  • The API Add-on now REQUIRES PHP 5.3 If your website is running PHP 5.2, the API plugin will no longer work. This is necessary to improve security.
  • Added debug and error logging support (using the Gravity Forms Logging Tool)
• Web-to-Lead Add-on
  • Now supports mapping Address 2 fields
  • Fixed issue with some leads not being added; this was likely because of the time it took to submit a lead to Salesforce.
• Daddy Analytics integration – the Add-on now works great with Daddy Analytics. What is Daddy Analytics? It allows you to track your leads from their original source, and with that information, you can get true marketing ROI.
• Changed how the plugins are loaded – there’s now a “Salesforce” setting in the Gravity Forms Settings page. Go there to enable or disable the different plugins. There are no longer multiple visible plugins for this Add-on.
• Added translation If you want to help translate the plugin, please submit your translation here](https://www.transifex.com/projects/p/gravity-forms-salesforce-add-on/).

3.0.4 (June 26, 2014)

• Fixed: Threw invalid API warning if settings hadn’t been saved.
• Added: Localization strings
• Fixed: Both Integration Methods were showing in the Settings menu

3.0.3 (June 20, 2014)

• Fixed: Finally nailed the OAuth Refresh Token flow. It’s all working nicely now.

3.0.2 (June 4, 2014)

• Fixed: is_plugin_active() not defined fatal error on activation

3.0.1 (May 11, 2014)

• Modified: Hide Daddy Analytics custom API Name settings, unless the gf_salesforce_custom_da_api_names filter returns true.
• Fixed (API): Return false in get_api() method when settings are empty.

2.6.4.1 (March 19, 2014)

• Fixed (API Version): Entry update improvement when set to manually export to Salesforce
• Removed: Unused plugin-upgrade.php file

2.6.4 (February 20, 2014)

• Fixed (API Version): Live Remote Field Mapping improvements
  • Fixed endless spinning
  • Empty options are better managed; shows “No Picklist Fields” message
  • Now shows an error message if the field cannot be used for Remote Field Mapping
  • Static PHP warning fixed when WP_DEBUG enabled

2.6.3.4 (February 20, 2014)

• Added (API Version): new hook “gf_salesforce_show_manual_export_button” to disable “send to salesforce” button/checkbox

2.6.3 to 2.6.3.3 (February 14, 2014)

• Web-to-Lead: Re-added the functionality to show the “Salesforce enabled” icon in the forms list that indicate active feeds are enabled for that form.
  • Integrated that method into the KWSAddon class
• Web-to-Lead: HotFix: Check for correct Add-on class name (KWSGFAddOn2_1)
• Web-to-Lead: Fix: show multiple “Salesforce enabled” icons in the forms page

2.6.2 (February 11, 2014)

• API Version: Added a check to make sure server supports SOAP
• API Version: Added a filter to override the SOAP check. Use add_filter( 'gf_salesforce_soap_is_available', '__return_true'); to force loading even if a SOAPClient class does not exist.

2.6.1.1 (February 6, 2014)

• Added: Add a new filter gf_salesforce_format_date to change date format for Date field type before exporting to Salesforce

2.6 & 2.6.1 (January 23, 2014)

• Added: Manual export of leads – a new setting in the Form settings configuration that prevents all entries from being sent to Salesforce; only manually-approved entries may be sent.
• Added: $feed and $api variables into the gf_salesforce_create_data filter, so that additional things can be done in $merge_vars based on the feed options, and $api can be further tweaked (setAssignmentRuleHeader) based on the feed object name. Thanks, @sc0ttkclark!
• Fixed: PHP static method warnings
• Fixed: Supports paths outside of standard WP plugin directory structure

2.5.3

• Fixed: Minor PHP static method warning
• Fixed: Dates now export properly in API and new Web-to-Lead Addon

2.5.2.1

• Fixed: Minor PHP static method warning

2.5.2

• Added “Upsert” functionality – if an object (Lead or Contact for example) already exists in Salesforce, update it rather than creating another object. Configure this setting at the bottom of existing Feeds.

2.5 & 2.5.1 on January 7, 2014

• Web-to-Lead: Completely re-wrote the add-on to provide full Feed capability. See the FAQ to learn how to set up the new feeds: “Web-to-Lead: How do I convert my existing form configuration to Feeds?” (Requires Gravity Forms 1.7+)
• Web-to-Lead: Added integration with the Gravity Forms Logging Tool
• Web-to-Lead: Added option for Salesforce debugging emails, which are very helpful!
• API: Added a filter gf_salesforce_enterprise to use the Enterprise Client instead of the Partner client. Thanks, @sc0ttkclark

2.4.1

• Added more filters: gf_salesforce_mapped_field_name, gf_salesforce_mapped_value, gf_salesforce_mapped_value_{$field_name}. Thanks, @sc0ttkclark!

2.4

• Added filters to modify connection details. See the FAQ item “How do I modify the Soap, Proxy, WSDL and connection settings?”
• Updated to latest Salesforce PHP Toolkit library

2.3 & 2.3.1 & 2.3.2

• API
  • Now fully supports custom objects!
  • Fixed error with endless spinning when choosing “Select the form to tap into”
  • Fixed a few PHP notices
  • Now supports line breaks in submitted content
• Web to Lead
  • Fixed issue on Form Settings page caused by Gravity Forms 1.7.7 update.
  • Now properly handles data with ' and " – no longer adds slashes

2.2.7

• Updated Web to Lead
  • Fixed Lists input type
  • Fixed issue where checkboxes and multiselects were being added as Array

2.2.6

• Updated Web to Lead to work with Gravity Forms 1.7+ form settings screens

2.2.5

• Fixed Web to Lead picklist functionality. Thanks, Ryan Allen!

2.2.4.3

• Fixed issue that should never have happened, but did: the “Gravity Forms Not Installed” message showed up for an user on the front-end of their site and prevented them from logging in.
• Fixed admin PHP Notice when gravity forms is not activated

2.2.4.2

• Fixed one more issue with “Array” as submitted value when using select dropdown lists and Salesforce Field Mapping. Note: after updating the plugin, you may need to re-save your affected forms.

2.2.4.1

• Fixed issue introduced in 2.2.4 that prevented options from being editable when Salesforce Field Mapping was not enabled.

2.2.4

• Fixed issue with selecting Live Field Mapping where object information wouldn’t load if there was an apostophe in the field name or description.
• Improved Live Field Mapping display: disabled fields stay looking disabled on form save.
• Fixed issue where Live Field Mapping would not send form data properly. This was caused by the plugin wrongly assigning “inputs” to the fields, causing the field IDs not to match upon submit.
• Fixed version number on Gravity Forms Salesforce Web to Lead Add-On so that it won’t always seem like there’s an update waiting.

2.2.3

• Fixed issue where Web to Lead Form Editor would no longer load if Salesforce API plugin was enabled and not configured. As reported here and here.
• Fixed issue where Salesforce Fields disappeared when mapping fields using the Salesforce API plugin, as reported here. Thanks to @gmcinnes for the fix.
• Improved XML validation by escaping XML characters < ' " & > and also removing UTF-8 “control characters”. Should solve the issue reported here in regards to “PHP Fatal error: Uncaught SoapFault exception: [soapenv:Client] An invalid XML character (Unicode: 0xb) was found in the element content of the document.”

2.2.2

• Added Edit Form and Preview Form links to Salesforce.com Feeds list
• Fixed issues with array processing with new _remove_empty_fields and _convert_to_utf_8 methods

2.2.1

• API: Made live updating optional with radio button
• API: Added cache time dropdown
• API: Refreshes transients when changing cache time
• Web to Lead: Fixed issue where Salesforce icon wouldn’t show up on load in Edit Form screen
• Web to Lead: Salesforce icon now shows properly on Edit Forms screen

2.2

• Added Salesforce picklist value mapping with Checkbox, Radio, Drop Down, and Multi Select fields. This feature dynamically pulls in fields from Salesforce so you don’t need to re-create them. The downside? You need to modify default fields, field order in Salesforce.
• Added fixes provided by gmcinnes: Make sure new error email functionality catches exceptions, Don’t send empty fields to Salesforce, and Make sure to send zeros to Salesforce

2.1.1

• Fixed issue reported here with fatal error

2.1

• Fixed: Added support for multiselect fields other fields with multiple responses
• Added: Entries now get assigned a Salesforce ID that link directly to the Salesforce contact or object (API plugin only)
• Added: Notes are now added to Entries with the success or error messages from exporting to Salesforce (API plugin only)
• Added: You can have Salesforce export errors emailed to you when they occur (API plugin only)

2.0.2

• Fixed issue with HTML encoding to fix SOAP fatal error. Thanks, gmcinnes!

2.0.1

• Renamed the plugin files so that you wouldn’t need to re-activate.

2.0

• Added API plugin. A complete rewrite; switched to SOAP API. Will require re-configuring the plugin.
• Renamed 1.x plugin “Gravity Forms Salesforce Web to Lead Add-On”

1.1.3

• Fixed issue with latest Gravity Forms preventing Salesforce checkbox from showing up – thanks Michael Manley!

1.1.2

• Fixed issue where entered Salesforce field mapping labels were being overwritten by auto-labeling.
  • Added filter gf_salesforce_autolabel to turn off auto-labeling by adding add_filter('gf_salesforce_autolabel', '__return_false'); to your theme’s functions.php file.
  • Made auto-labeling much less aggressive: now only matches exact matches for First Name, Company, etc.
• Added support for checkboxes and other multiple-item fields using implode() PHP functionality: lists will be converted to comma-separated values.

1.1.1

• Fixes issue where all forms get submitted to Salesforce, not only enabled forms (reported on support forum).
• Added a new filter to modify the lead source gf_salesforce_lead_source, as requested here. Passes three arguments: $lead_source, $gf_form_meta, $salesforce_data.

1.1

• Added support for Custom Fields (view the FAQ here, or the Gravity Forms Salesforce Add-on Settings page for this plugin)
• Improved authentication check in the settings page – no longer creates a blank lead.
• Fixed some PHP notices

1.0

• Launch!