I am working on a process which flattens a reader extended form in the orchestration. In the reader extended form, some fields are bound to schema elements and some are not. When flattened, the fields having the binding retain their value and the other fields show blanks. Is there a way we can retain the values in the unbound fields as well after flattening the form?
Livecycle ES2...The user himself enters the values in the form, which has a submit button in it. I recorded the transaction as well and found that before entering the transformPDF service (which I am using to flatten the pdf), the form has the values in it, but at that step, the fields with no bindings lose their values. Please let me know if you need any further info.
Humm, I think I see the problem. TransformPDF doesn't really "flatten" the document, it re-renders it as a non-interactive document. That means that the data is re-merged with the form template. Since some of the fields aren't bound, then they don't get populated by the re-render.
Unfortunately there's not much you can do with the data bound as it is.
I suppose you could remove the schema from the form and then you would get all of the data. Then you could apply an XSLT to the form's data to "convert" it into a schema compliment format