Posts tagged PDF forms

10 Top Tips for using Mobile PDF Forms

Having worked with a few clients to deliver mobile PDF form solutions for tablet devices and using the Adobe Reader for Mobile we thought we would list 10 top features which can make your use of electronic PDF forms and PDF documents in general on Android and iOS useful.

This list is available from eformsfactory.com in this blog post.

Displaying PDF documents/forms from Adobe LiveCycle in the browser

Users of Adobe LiveCycle quite regularly interact with PDF documents. Some examples are:

  • Rendering customised documents for print purposes
  • Creating PDF forms for on- and offline use to collect data for further processing
  • Rendering pre-filled PDF forms to send out to customers/users for completion and physical signature etc.

In a lot of cases those PDF documents are what’s called an XFA-based PDF form/template. XFA is Adobe’s XML Forms Architecture and a proprietary technology to describe form information. I spare you the technical details, but essentially quite often those XFA-based forms get wrapped into a PDF document, this is done by rendering the XFA information over a PDF page background.


Read the issue and steps to fix it at this blog.

Adobe LiveCycle Designer book – 2nd edition released

JP Terry has done it again! JP is the CEO of SmartDoc Technologies and he’s released the second edition of his very popular Adobe LiveCycle Designer book. The first version sold over 11,000 copies! This edition has all-new sections of best practices for PDF forms and is up-to-date with Designer ES4 features.

Read about what is included and find a purchase link in this blog post.

Mobile forms Vs Pdf forms

Mobile forms component enables XFA forms on mobile devices. The same XFA form that can be used for generating pdf, can be used to generate html form as well. The html version should behave almost exactly same as the pdf version. XFA has a very rich support for scripting. It supports tons of APIs and almost all the properties are exposed via scripting interface. But as the famous 80-20 rule suggests our customers use only 20 % of that capability. The difficult part was to find those script constructs that are used in real world cases and prioritize them higher than the rest of the script constructs. We have run through the large collection of customer XDPs we have and generated the list of javascript constructs that people use. Interestingly, we found that usage to be less than 20%. Out of 2600 javascript object properties and APIs, forms were using around 200 constructs at least once. So we decided to prioritize based on it.  Mobile Form is covering that gap fast but there would be certain things that would never make sense in html or mobile world.



Read the complete post here.
Go to Top