I’ve a use case to generate editable pdf from a HTML5 form and I’m able to achieve it statically using com.adobe.fd.forms.api.FormsService.renderPDFForm(..). No issues here.
For another use case, I’ve a dynamic form where I’ve combined two static forms and put a dialog with radio buttons as front screen. It has some business logic written in both client side js & server side js. Now when I try to generate editable PDF using renderPDFForm(..), it doesn’t work as expected. The xml markup with data that is sent from the browser doesn’t merge correctly with the xdp. I think that is because of visibility rules set on each form in the designer. I tried to change the visibility rules and I could see the correlation between the xml data and server side properties set in the designer.
I can think of custom hacks to make it work but would like to understand if I’m doing something wrong fundamentally & if there is a better way to achieve this use case.
Solved! Go to Solution.
it should be possible but I think we need more information about your use case. These are HTML renditions of XDP layouts, not Adaptive Forms?
1) you say you create a static PDF from a HTML form which is editable? Do HTML form and PDF come from the same XDP?
2) What exactly do you mean with dynamic form? My understanding is a form that dynamically adds or removes sections depending on user input or data. How do you combine 2 static forms into the "dynamic" form?
3) What exactly is not "working as expected"? When the XML does not match it could mean that HTML and PDF renditions of an XDP are based on different layouts or your "combining" somehow changes things (SOM paths for example).
To simplify, lets take an example:
Does this make sense?