How Adobe FormsCentral Saved My Project

Adobe FormsCentral, one of their growing number of apps at Acrobat.com, has been on my review list for some time but didn’t have a great angle to write about until recently. Adobe FormsCentral literally saved a recent project of mine, and I was surprised how its strengths dovetailed with the technical issues I was facing.

The project objective was straightforward:

  • Build an online registration form
  • Include payment integration with PayPal
  • Send email notification to the user and the client on submission
  • Store registration data or send it via email to the client

The client’s website is constructed with Ning, which made its name as a social community builder but now is a blend of that and a typical content management system. Unfortunately, Ning’s backend is fairly difficult to work with unless you are doing basic CSS or HTML changes. The Perl script that we used last year to submit the form data was not allowed by Ning, effectively scuttling our existing solution. I was worried that Ning would force the form to be hosted elsewhere until I thought about FormsCentral, which has a few characteristics that made it ideal for this job:

  • A robust set of form elements covered all the inputs I needed.
  • The ability to embed my form on any webpage with an iframe let me put this form on a Ning page with no problem.
  • The FormsCentral service handles all the notifications and submission data storage, so I didn’t have to write code to handle it myself.
  • Multiple user accounts through FormsCentral meant that my client could run reports and check registrant data as easily as I could.

FormsCentral comes loaded with 50 templates for various industries, but I only needed five text fields so a blank template was adequate. In the Design tab, I was able to make fields required, limit the total characters, include help popups and restrict input to certain types like text, number or email. These are all typically included with forms services like FormsCentral. The one design feature that is completely absent is the ability to dictate design with CSS, which I’d normally use to design a web form. I understand Adobe’s focus on non-programmers, but CSS could really make it easier to apply design elements throughout forms.

The Options tab pretty much covered the rest of my project requirements. I created a Submission Receipt that is sent to all users after they complete the form. I also set up a notification to be sent to the client and myself after every submission, though I was a bit disappointed my client had to create an Adobe ID and log into FormsCentral in order to be added to the notifications list. I also noted that I couldn’t create my own HTML email template to be used for notifications or receipts.

Payment processing is also set up in FormsCentral’s Options tab. Configuring PayPal payments with this form was the most difficult step to master. Registering the PayPal account with the form is easy enough but connecting the form fields to the purchase functionality can be confusing. In the Payment Processing settings, I had to specify the purchase field, quantity field, price and description. The user selected their quantity in a particular field on the form, so that was used for the quantity field. (I also could have set it for exactly one item, which is helpful in some situations.) The purchase field is what confused me because, in this case, the form’s Submit button is also considered a valid purchase field. It was what I needed for this project.

FormsCentral forms can be distributed up to three ways:

  • An HTML page hosted at FormsCentral. An example is https://adobeformscentral.com/?f=zGP2-N2bVVS-pV5I4D7hMQ.
  • A PDF form with interactive form fields. This can be submitted by the user when offline, and the data is stored locally until an Internet connection can be made.
  • Embedded via iframe into an HTML page. The embed code looks like this:


script type=”text/javascript” src=”https://formscentral.acrobat.com/Clients/Current/FormsCentral/htmlClient/scripts/adobe.form.embed.min.js”>
script type=”text/javascript”>
var fzGP2_2dN2bVVS_2dpV5I4D7hMQ = new ADOBEFORMS.EmbedForm({formId:”zGP2-N2bVVS-pV5I4D7hMQ”, server:”https://adobeformscentral.com/”, width:640, showHeader:false, transparent:true, widthAfterRedirect:640, heightAfterRedirect:400});
fzGP2_2dN2bVVS_2dpV5I4D7hMQ.display();

You can see some embedded parameters, such as background color, form width and the iframe size after the form is submitted and a redirect URL is specified. (I didn’t use this because FormsCentral lets you show a confirmation message after submission.)

The View Responses tab is where the client and I could see the submitted data. Everything is stored, and PayPal even returns the transaction ID and total dollar amount to FormsCentral so the payment data is complete. A report can be exported from the File menu within FormsCentral, or you can view the Summary Report tab to see some charts based on your data. These did not help me much because most of my data was non-numerical, and the charts can only display data as a full count or an average. My client and I focused on the View Responses tab, which had all the data we required.

The Ning platform could accept FormsCentral’s embed code since it’s pure HTML, and the form itself worked perfectly. This got us around the limitations imposed by Ning and also provided me the data handling that I normally would have executed with my own scripts. Ultimately, FormsCentral gave me more tools with less work and helped both me and my client be more efficient. FormsCentral does have its limitations, mostly imposed by the product’s emphasis on the non-programming user. However, FormsCentral is designed for projects like this one and I was lucky to consider it!

FormsCentral can be run as a 30-day trial for 99 cents or paid monthly for $14.99 per month. This allows up to five forms and up to 500 responses. An annual rate of $143.88, recently reduced, provides 5,000 responses per form with unlimited data storage and unlimited forms. Note that the Acrobat.com apps, including FormsCentral, are not included in Adobe’s Creative Cloud product.