What benefits does Render New HTML service provide over the OLD RenderHTML service

[adeivasigamani]

Fellow Livecycle Developers,

in ES 3 and before we had renderHTMLForm service, that took two inputs 'Form and Form Data' with other optional inputs like CSS.

The output was a document object that merged the xml data with drop downs working perfectly fine with binded data pre-populating the drop down lists.

The new Forms service, takes the contentRoot, template, and dataRef or data as input and produces the XFA form as a HTML 5 form, but any drop down values that are indicated in the binding do not appear, only direct text bindings to fields work, is it possible to get the HTML as a document object like in the previous renderHTMLForms service, and how can we prepopulate the HTML 5 output with data and lists for fields like drop downs.

Please let us discuss the merits or the new HTML 5 rendering via CQ5 profiles over the earlier renderHTMLForms service, and how it can be used in real world scenarios.

Regards -

Ashok D

[adeivasigamani]

Also, If the use case is like as follows,

We have several fragments built on a common Schema and based on user selection the fragments are stitched using assembler services and a resultant XDP is produced on the fly (but not stored anywhere in the CRX), now that the Resultant XDP is to be rendered as HTML, how is it possible to use the Livecycle Forms service to produce the HTML,

we know that Livecycle Forms uses cq 5 profiles to render a XDP that is available in the repository with the following URL,

http://localhost:port/lc/content/xfaforms/profiles/default.html?contentRoot=repository///path_of_the...

Now that the XDP produced earlier in the use case on the fly is not stored anywhere and does not have a contentRoot parameter, how is it possible to convert the XDP to HTML 5 with the Livecycle Forms module.

Regards -

Ashok