How, if at all, do you guys get around the very limited support for XFA file types? I love how versatile XFA forms created in LiveCycle Designer can be, and I've created several very impressive forms, BUT I have to downgrade to static PDF because at least 1/3 of our clients cannot open XFA documents. From what I've found, there are some MAJOR limitations, like:
Why such limited support for this highly-functional file type? It's a shame to have developed something so powerful only to have to regress to the stone age of form presentation. For example, I set up an XFA form to operate like a web-based smart form, with "pages" the users navigates through. Unfortunately though, it cannot be used because at least 1/3 of our clients wouldn't even be able to open it. Very disappointing.
Views
Replies
Total Likes
I believe many third party implementations look to the PDF specification, which currently does not include the XFA extensions. Adobe has provided the following document to outline workarounds for this limitation
https://helpx.adobe.com/livecycle/kb/xfa-forms-firefox-chrome.html
Views
Replies
Total Likes
Even AcroForms have limited support in mobile versions of Reader. A few non-Adobe mobile viewers have better support, but none are as complete as the desktop versions of Reader. Most have no support.
It's hard enough for third-parties to get AcroForms to work on the desktop. PDF viewers from both Apple and Microsoft corrupt PDF forms in a number of ways. Others from Google (Chrome) and Firefox are lacking in a number of ways. Trying to include XFA support, especially for dynamic forms, would be significantly more complicated.
Views
Replies
Total Likes
That link contains the following:
Has anybody actually used this and, if so, what has been your experience?
Views
Replies
Total Likes