1. Download and install LiveCycle Designer. (Adobe LiveCycle ES2.5 trial version)

2. Select File then New from the meu items.

Select 'Use a Blank Form' from the options then click Next.

 

3. Drag and Drop the fields and objects that make up your form.

Add Objects To Your New Form In LiveCycle Designer.

Add Objects To Your New Form In LiveCycle Designer.

Add Objects To Your New Form In LiveCycle Designer.

And that’s all there is to creating your very first Adobe LiveCycle PDF Form.

This is  a very simple beginner example. For highly complex and professional PDF Forms contact me (Rod) at SwiftForms today.

Name:
Email:
Telephone:
How may I help you?

 

 

I have started adding my most recent PDF SwiftForms developed for various clients. You can open, view and test the functionality in the forms by clicking the ‘Examples’ button to your right.

If your organisation is looking for consultancy, advice and/or PDF Form development services please don’t hesitate to contact me by following the ‘Contact’ button to your right.

Rod

 

  • Intuitive – PDF Forms designed to flow logically from start to finish. Forms that only display relevant fields and hide those that aren’t relevant from the user filling the form.

 

  • Cost Effective – PDF SwiftForms™ Forms that remove many of the inefficient and costly elements associated with traditional paper based forms. The need to conduct large print runs no longer applies. The need to re-print if even a minor change is required along with disposal of out-of-date forms no longer applies. The need to pay staff to interpret near illegible hand written form entries and re-enter them into your systems no longer applies. The savings are many and the removal of significant problems associated with traditional forms are eliminated.

 

  • Accessible – PDF SwiftForms™ that are all developed with the goal of creating forms that are available to anyone who wants or needs to fill them in. Wherever practical within PDF Form development SwiftForms™ follow the United Nations G3ICT Accessibility guidelines and also develop to comply with any legislative requirements of the countries that SwiftForms™ will be hosted and used in.

 

  • Self Validating – PDF SwiftForms™ are smart forms because they are able to identify and alert the user filling them in when information is not what is expected. For example when someone enters a future date 01/01/2015 into a date field that requires their date of birth, a PDF SwiftForm will alert them to the error and return the user to the field so that they can immediately correct the mistake. This build in validation can check for correct formatting of email addresses, telephone numbers, check that required fields are not left blank and alert the user to a wide range of problems before the form is returned to your organisation.

 

  • Legible – Anyone who has received paper forms filled by hand understands the difficulty that is often experienced interpreting what has been written into the form. Every person has different handwriting and the process of deciphering what some handwritten text is meant to convey can be time consuming, fraught with error and costly inefficiency. Swiftforms™ return legible information that does not require re-keying by your staff improving quality and benefiting your bottom line.

 

  • Printable – At the root of PDF SwiftForms™ is fundamentally a PDF document. Although there is significant software based functionality embedded in the PDF document to enable the smart eform capabilities, at its basic level the document is still a PDF. This means that mo matter which operating system, device, screen resolution paper size or type, the printer you use or any other factor the document will appear and print the way it was intended to be seen.

 

  • Compatible – One of the several options for receiving your form data is as XML. Most modern systems are able to take a custom formatted XML document and import the data directly into existing databases or other systems. PDF SwiftForms™ provide other options for receiving your form data including as email messages, CSV files or or even the entire PDF document containing all of the saved entries.

 

  • Sign-able – If a hand-signed document is required a PDF SwiftForm™ will still provide an excellent solution that continues to provide many of the benefits listed above. Forms that require signature can be designed to validate prior to the print event being executed. This means that the form is forced to be as accurate as possible before the user prints, signs and post or faxes it back to your organisation.

 

  • Submittable – If a hand-signed document is not required and an electronic solution is suitable for your needs you also have the option with PDF SwiftForms™ to have data that is collected directly submitted to you as a custom formatted email, XML or directly into your database. Since the data is validated on the client (PDF Form) side of the process you can be confident that the correctly formatted information will be received no matter how you choose to receive it.

 

When establishing SwiftForms I wanted to have a very narrow focus. I wanted to do nothing other than specialise in the development of PDF Forms. I wanted to take great care with implementation of testing processes that would be continually refined ensuring delivery of the quality that our clients should be able to expect. I personally take the accesibility of your forms as seriously as the United Nations and many countries around the world do by following guidelines and ensuring legislative compliance.

I hope that this brief overview of SwiftForms provides your organisation with an insight into my philosophy and the product that you should expect to receive when you engage SwiftForms to develop new or convert your existing flat paper or PDF forms to dynamic PDF SwiftForms.

Rod Swift
Call, Fax, Skype or Email Me Today

See & Test Out Example PDF SwiftForms

 

 

 
  • First, thorough quality control and testing. Every SwiftForm that is developed in order to meet our strict testing process, must adhere to our proprietary 32point test checklist after EVERY adjustment, no matter how minor. This ensures the form that you receive is far less likely to cause you any headaches with bugs or other faults due to inadequate testing and oversight.

 

  • Second, accessibility. In order to pass the strict testing all of the PDF Forms that we develop must adhere to the guidelines set out by the United Nations, and any legislative requirements or best practice guidelines set down by the country that form will be operating in. Our experience developing PDF Forms that can be navigated and used by people living with a disability is a major consideration for our company when converting from flat PDF or paper forms to PDF SwiftForms.

 

  • Third, experience. With more than five years experience using Adobe LiveCycle to develop PDF Forms for Government agencies in Australia our combined knowledge, company resources and individual skills as PDF Form developers is second to none.

 

  • Fourth, focus. All SwiftForms does is create high quality PDF Forms and because of that narrow focus on one product and one technology we produce the highest quality forms for our clients.

 

  • Fifth, guarantee. I personally guarantee the PDF SwiftForm product deliverd to our clients. If for any reason they are not 100% satisfied with the form, even after make every effort possible to rectify anything that wasn’t to our customers expectation, I will provide a 100% refund. Therefore there is absolutely no risk to our clients. Receive a form that meets or preferably exceeds your expectations or your money back.

 

Contact me today to begin moving your PDF Form project forward.

 

Rod Swift

SwiftForms.com.au

 

 
W

PDF Forms

On March 25, 2011, in PDF Forms, by admin

Guidelines Topics Followed by SwiftForms™

  • Usability guidelines for online application forms
  • Overall customer experience
  • Make it easy for users to find the form
  • Create a good first impression
  • Encourage user trust
  • Encourage user interest and feedback
  • Create a flexible design which will support the needs of different users
  • Moving around the form (navigation, workflow & orientation)
  • Make it easy for users to understand the workflow and structure of the form
  • Make it easy for users to identify next steps (links and buttons)
  • Provide efficient navigation within the form
  • Provide users with a quick, efficient workflow
  • Reading the form (written content & language)
  • Style of language
  • Grouping of information
  • Make it easy to complete the content
  • Viewing the form (layout & presentation)
  • Page layout
  • Use of images
  • Readability
  • Accessibility
  • Appropriate use of colour
  • Interaction design
  • Error handling
  • Standards and other sources of information
  • Best Practice Checklists
  • Content
  • Form performance
  • Interaction design
  • Visual design

SwiftForms™