I often work on LiveCycle projects where an application generates a
populated XFA form and then I have scripts occurring on the
initialization event to further utilize the populated data. The method I
have always done to accomplish this is to create a subform with
"mergefields"(textfields) containing data binding. When the application
loads data into the form, the scripts reference those mergefields and
further actions/calculations are done with the data in those fields. The
mergefields subform ...
Is it better form design practice to use subform/field borders or
lines/rectangles in forms. To me, it is easier to use borders of
fields/subforms. Is there any videos or literature on this? Thanks,
I have a lot of experience working with LiveCycle (AEM) Designer, as
well as working with a matter management product which populated XFA
forms. Very comfortable working with LiveCycle Designer and XFA forms.
Now, I have a potential long term project involving AEM Manager,
including working with XFA forms. Involves Workbench, workflows, HTML5,
may involve Adaptive forms later. No further information at this time.
Suggestions for getting up to speed really quick like a good video? Is
there a good...
Let's say I create an application which includes form designs on
LiveCycle Designer and I sell this application to customers. Do I need
to pay anything e.g. royalties to Adobe?How about if I create a form on
LiveCycle Designer and sell it standalone to customers? Does your
response hold true with Adobe forms?It would also be helpful to get
references to applicable adobe licenses etc. on this.Thank you.
GIven the support decisions for Adobe regarding LiveCycle (which I don't
really understand), if I make a form using Adobe LiveCycle will the form
continue to work properly for say the next three years? e.g. I design a
form with a bunch of subforms/sections appearing with text in each one.
The user makes selections on a set of checkboxes and only the selected
sections appear on the document - that excellent feature of Livecycle
which not only allows the subform to be visible or invisible, but
I like using LiveCycle Designer to make PDF forms. I want to use it with
organizations I work for to make fillable forms. But I am concerned that
the forms will "break" more easily than Acroforms. Generally - is this
concern of mine valid?-If I have a subform in a flowed form that is made
"visible" in certain circumstances, and "hidden" in others-using a
Adobe sold Designer? Is it less likely to work than similar