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.
Users of Adobe LiveCycle quite regularly interact with PDF documents. Some examples are:
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.
Mobile Form rendition of an XFA form is almost similar to PDF Form rendition in terms of behavior and appearance. Some of the dissimilarities are discussed in Mobile Form Vs PDF Form post. In this post, I’ll discuss one key difference that a form designer should take care while designing the XFA Template and that is where it is so critical to preview your templates from the designer itself.
In this post, I’ll address a use case where in profile you want to access data from the rendered form. Sometimes, you might want to access metadata associated with the form. You can add metadata to the form using the Form Properties option of the File menu in LiveCycle Designer.
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.
An accessible form is one that a wide range of people can use, including those who may have disabilities that affect how they are able to interact with the form on the computer screen. For example, the form user may have a visual impairment or reduced mobility.
Mobile form uses ARIA html5 accessibility standard to support a number of features and capabilities that enhance the usability of forms for users with a range of disabilities, and assist form authors and create forms that are more accessible to people with disabilities.