AEM Forms 6.1 FP1 introduces these new features: https://helpx.adobe.com/content/help/en/aem-forms/6-1/whats-new-fp1.htmlto upgrade to FP1 - the installation instructions applicable to your environment can be found here : https://helpx.adobe.com/aem-forms/6-1/upgrade.htmlin some cases you can direct...

You will have to make sure that your version of designer is either AEM Forms 6.0 Fp1 or more recent than that.I believe this does not work on ES4 or previous versions.

i would say, keep them both within a single subform, and then play with subform's pagination.This way, even if your text field needs to expand, it will not jump pages alone, rather the whole subform will shift, and the explanatory text will always hold it's position within the subform. Although with...

i think you need to un check the "Allow page breaks" option for the text field.then you need to review if that text field is wrapped in a specific subform. If so then the subform pagination should be able to deal with this.It can help you make sure that in case of overflow where the text field shoul...

In LiveCycle designer you have a master page that governs the orientation.In your case, apparently you need 2 master pages. 1 which is potrait and other which is landscape.Both the master pages will have a content area defined in them, which refers to the region within which content can be placed.Le...

As stated by Magus069‌, it's better to have a delete button with each row, since that simplifies your script for deletion (it's pretty much repetition), and secondly having individual delete buttons, give users the power to choose which row they specifically want to delete.

another way could be , keep the actual form pages hidden at start, and only show a single page which has scrolling text box containing EULA, with Accept and Reject buttons. IF someone rejects, you can keep the rest of the form hidden or show message boxes to force EULA acceptance.If someone Accepts ...

I'm pretty sure this was working in the AEM 6.0 FP1 release when i tested it, and i doubt if there have been any major changes since then.can you validate of the value of the pagezerocontent variable is actually a valid rich text as specified on the page zero documentation page ?.. try starting off ...

radzmar‌ - interesting question. I never actually tried that.The LiveCycle server has it's own reader extensions service, and i know that does not affect the pagezerocontent property.In theory even if you do the reader extension from Acrobat or LC server, that is simply adding some metadata and repa...

You can;t force them, but you can try to educate them.basically if a form cannot be viewed in non Adobe viewers/readers, it would still show a page (a.k.a pagezero) which shows a default message.You can customize that page to inform users that XFA forms dont work in other readers.customization help ...