Rendering XDP as HTML field Patterns num{(zzzzzzzzzzz9.99)}

[Bonao94]

Hi, I am rendering a XDP document as XHTML with renderHTMLForm 'transformTo' => 'XHTML' . The field Type="Numeric Field" and the patterns num{(zzzzzzzzzzz9.99)}. These settings works fine on a PDF but it does not work when render as HTML. The PDF version prevents the users from inputing numbers only. The XDP version rendered as HTML form is allowing the users to input anything on the field.

Any idea will be helpful on how to prevent this?

[Suvrat]

Hi,

You might want to check out the ES4 offering of the HTML5 rendition of the XFA forms. Please see http://helpx.adobe.com/content/help/en/livecycle/help/mobile-forms/introduction.html for more details. Do notice that while the documentation calls the html5 rendition as Mobile form, but there is really no stopping in the XDP to render on any browser that supports html5 including Desktop based.

I understand that this may not be the answer you are looking for. But, ES4 has done much more to support the XDP capabilities in html rendition than the earlier versions.

[adeivasigamani]

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,

http://localhost:port/lc/content/xfaforms/profiles/default.html?contentRoot=repository///p ath_of_the_xdp&template=templateName.xdp&dataRef=http://xmlPaTH

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.