You can try writing a custom render process which can call "Render HTML" or "Render PDF" based on a decision point.
Thanks for the reply
Really nice suggession, but cud you pls give me some more clarity on how exactly I can do this.
Thanks again for your valuable time
If you use form guides, by default the workspace enable an option to view the PDF document.
But i'm not sure about HTML & PDF combination.
Are the users opening the form in Workspace?
It's easy to generate both an html and a PDF version from one form design, but to have them both associated with the same task would be trickier. Is that what you want to do?
yes Scott, but how can i achiev that please guide me
I guess it depends on how you want to present the choice of html/PDF to the user. One way would be to render the form as HTML for the task, and provide the PDF as an attachment. When they open the task, the form appears in HTML, but they could optionally open the attachment and submit the PDF. This would complete the task, but the HTML form would still be open in Workspace, which would probably confuse the user.
Another way would be to create a dynamic multi-page form - page one asks the user if they want HTML or PDF. When they submit that, the HTML or PDF form is opened. I'm not sure how to implement this. Hopefully other community members have some suggestions.