I've recreated the issue and it's understandable why it's working the
way it is but can understand the confusion with clicking twice. I'll
raise it with engineering and see if there is anything we can do
Once you have deployed the AEM Forms addon into AEM using package
manager you can go to
will allow you to import your XFA forms one at a time or if it's easier
for you zip up the XFA forms and upload the zip. You can use the forms
to render as PDF or HTML or use them as a Form Model to create an
adaptive form which is more suitable for mobile devices. If your xfa
forms are based on a schema you can also use the XSD as form m...
I think something was lost in communication/terminology here and I
apologize for that. You can continue to use LiveCycle Designer. What I
think was lost in translation was the fact that you're likely creating
PDF forms that you're making available on your website and the browser
vendors don't allow for the Adobe Reader plugin to be loaded.Your option
is to allow a customer to download the PDF form from Designer and in
some cases this user pattern isn't desirable. Adobe has provided a
What you can do is go to the properties of the adaptive form and
associate the XDP as the model. Then in the Adaptive Form add a verify
step, this will render the XDP. On the verify component there is a
configuration option to make it interactive.
Why are you placing instructions outside the form, I need more detail.
You could like do this with the guidebridge API but I'd need more detail
to make a recommendation. Correspondence management may be a better fit
here as well
What metadata are you trying to add is it consistent for all the forms?
When you add the XDP you could execute an AEM workflow to update the
content. Also you could just export all the XDPs, place them in a zip
file and just upload the zip through form manager
On the click of a button you can hide and show whatever panels you wish.
I'd suggest using rule builder to provide the guidance for you. You can
just drag and drop the functions you wish to occur and not worry about
the scripting. Select the button and it looks like a gavel to go to rule
builder from the context menu.
Put a script on the button to validate that the required fields are
filled. You may need two buttons, one that the user sees and clicks on
and once the validations are done it executes the click of the submit