What I've been doing is create a script that takes the data from the form,
transforms it using View1.xsl (or a different one that I specifically
construct, depending on what I want), and then using WebDAV, puts the
resulting HTML document in a SharePoint forms library. It could be sent to
any web folder, though.
You have to do some tricky things for this to work (like write JavaScript
;^), plus you need some place to put the output HTML file. I'm using it to
create highly structured documents (like test specifications). The document
is authored using a pre-configured InfoPath template, and submitted for
review to a SharePoint team site. We comment on it for a while, the changes
are incorporated, then the final document is published to a permanent place
in SharePoint with the rest of the project documentation. The InfoPath form
itself is saved in a separate forms library where all the editing takes
place. What's "published" is an HTML version of the form that anyone can
read using a web browser.
I suppose this is pushing the envelope a bit for what most people use
InfoPath for, but it's way better than letting folks use Word to write
specs--for one thing, I can take the completed InfoPath form and generate a
set of test cases from it...or from test cases, I can generate test
automation code!
Regards,
Mike Sharp
