The renderHTMLForm service returned a HTML object, that we can open in a browser, the new HTML render service available in ES4 in the Process Management (System) application takes taskContext object that has FormURL as input and returns a url string like this lc/content/xfaforms/profile/default.html?contentRoot=.....&template=......
now my question is in my case,
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,
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.