I've been using Dynamic Forms 2.3 on a large Enterprise level internet site for over 3 months till I was able to begin testing the 2.5 beta.
Our site receives over 100k uniques every month, and is setup in a web farm behind a load balancer. Two instances of IIS running both connected to the same SQL DB on a separate machine. The only reason I mention this is because Dynamic Forms 2.5 installed and worked flawlessly in this environment. So, I am assuming that those sites with running on a shared hosting environment with a single IIS instance would have the same experience.
9 days ago I received the 2.5 beta. I rolled the dice, and did an install directly over my current 2.3 install after backing up the database.
Once installed I went to the home page of our site, and surfed around a bit to look at a conversion form I had setup on every page of our site. Everything looked intact, and from there I tested the form. Logged in, and the form data had been recorded from my post as it had with 2.3.
My reason for inquiring - begging rather - about the beta was the HTTP Post ability. My company uses Salesforce.com as their CRM, and the ability to post directly to the Web2Lead CGI was what I was most excited about. Up to this point, each lead would convert into XML, and then I would do a daily import to Salesforce. This was a pain as I'm sure you could imagine. Even after importing the leads from an Excel or XML file I would have to delete each entry in "View Form Results". Not a big deal, but when you have over 300 leads per day it can be 10 minutes of annoyance. Note: The beta build I am using does not have a "Delete all Records" option. Perhaps the RC will.
Now onto the HTTP Post. Salesforce has an old fashioned HTTP CGI that post all of your new leads via web forms to your CRM account. From there you can view form information, and assign it to Sales people and convert each account. Here were the steps I took to make this work.
First make a hidden field with your Salesforce OID. The default value needs to be setup to your precise OID. Nothing more, nothing less.
Create all fields used in your web2lead form in DF 2.5.
Textboxes for user input, pick list for selections, and there are a few choices for radio buttons/check boxes/yes no pick lists.
I use each of these in my form, or at least experimented with them. Here's how I did it.
For radio buttons, just chose yes or no as labels. Set a value of 1 for yes, and 0 for no answers. Same goes for checkboxes and drop-downs.
Salesforce will automatically know how to interpret these during the HTTP Post.
The syntax for converting field name in DF 2.5 to Salesforce is quite simple. First specify the name of the Salesforce fields, and then the DF field name. Here is my entire Salesforce post in all of its glory:
oid=$(oid)&first_name=$(first_name)&email=$(email)&company=$(company)&phone=$(phone)&00N40000001Myq5=$(time_in_business)&00N40000001NAB5=$(accept_cc)&00N40000001NABA=$(over_5k)&00N40000001NABF=$(res_bar)&00N30000000cNn7=$(requested_amount)&00N40000001NnBD=$(merchant_acct)&00N40000001NnBN=$(inc_help)&00N40000001NnBI=$(credit_repair)&00N40000001Nncw=$(lower_rate)
I have also included a few screenshots of my different question event triggers. Certain field options show based on previous questions and how they were answered.
I have required field checked for every field in the form, and Dynamic Forms has handled each flawlessly.
Completion events include creating an XML file, Posting to Salesforce, Inserting to SQL and redirecting to a thank you page based on a selection made in the form.
To say I am happy with this module would be a gross understatement. I'll keep everyone posted and answer any questions I can. This post is about my experience with the HTTP Post ability of 2.5. I have much to say about other topics as well.
Also I want to give a big thanks to Chad for helping me out, and providing me with the beta. I can't thank you enough buddy. You've saved me hours of work every week!
Click images to enlarge
Click Image to Enlarge
Click Image to Enlarge
|