Posts tagged XFA forms

LC Designer: Wrong variable getting deleted

If you are working on a form in LiveCycle Designer which has not just form variables but also object collections and/or script objects all those will be listed on the Hierarchy tab under Variables.
Issue: If you delete a form variable from the Form Properties dialog (File > Form Properties > Variables) the wrong one will get deleted if the variables are not sorted.

To resolve this issue read this blog post.

LiveCycle update: Forms, documents, and the Adobe Marketing Cloud

2013 was an exciting year for LiveCycle. I want to take a moment to update you on how we are continuing to invest and innovate in forms and documents, and provide an overview of our 2014 plans. In 2013, we introduced LiveCycle ES4, a major release that extends rich form and document experiences to mobile users. Shortly afterwards, we began integrating these capabilities into Adobe Experience Manager, enabling organizations to easily create, manage, and publish forms and documents in conjunction with a market leading web content management solution.

Arun Anantharaman, the Senior Vice President Adobe Digital Marketing Products, shares more about the 2014 plans, 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.

Decoding Mobile Form Html

Mobile Form generates html snippet from XDP template designed from LiveCycle Designer. In this post, we will decode the internal structure of the generated html snippet. Once you are familiar with the html structure, you can customize it at will.

Generally, Mobile Form generates an html <div> element for every object of XFA form maintaining the same hierarchical structure. Here is the html snippet source of the xfa form and the red lines shows the 1-1 mapping between xfa objects and html.



Read the complete post here.

Mobile Form profile

Mobile Form enables LiveCycle XFA forms on mobile devices. It does it by rendering XFA Form to Html5 document.

As per Sling website, Apache Sling is a web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. Sling applications use either scripts or Java servlets, selected based on simple name conventions, to process HTTP requests in a RESTful way.

Mobile Form has a service that generates HTML snippet from XFA form. That html snippet, along with the xfaform css and js, can be embedded into any web page.

To know how to do this, read the complete post here.

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.

LiveCycle Mobile Forms

One of the many new offerings in LiveCycle ES4 is Mobile Forms that is ability to display and fill forms on mobile devices like iPad and other tablets. Mobile forms uses the already stable and widespread html5 as its rendering format so practically, any device that supports html5 can show LiveCycle forms. With the explosion of mobile devices, our existing customers were looking for this component to increase their reach and not only that, it would also enable many new use cases. Mobile Forms plays key role in customer’s workflow and enabling that workflow step on mobile device will further reduce the time taken to complete the process.

Read the complete post here.

Flat PDF vs. XFA Form PDFs

A frequent mistake that is made is to assume that, since XFA Forms can be saved as PDFs, they will behave like any other PDF. Truth is: XFA PDFs and flat PDFs are entirely different beasts.

Read about the detailed differences here.
Go to Top