B
Bill N.
I have a .Net web app that invokes a published InfoPath 2007 form. The end
user fills out and digitally signs the form, then submits it to a web
service, which among other actions, saves the form's XML to a DB and makes a
copy of the form XML available for download. I'm using the Source
querystring parameter and a custom redirector ASPX page to get back to my web
app on close...this works well for me so far.
I need to provide a viewing capability to the end user that shows the
signature. The view1.xsl is not displaying the signature despite my using
that workaround (i.e. including the <?xml-stylesheet type="text/xsl"
href="view1.xsl"?> instruction in the XML). The rest of the form displays
properly. I need this in order to support a large user community without
InfoPath. I also have an ESign requirement to make the saved XML file
available to the end user for storage on their PC. (Another way to express
this problem is: I want to display a *filled out and signed form stored as
XML* in the browser, but the XSL doesn't do so.)
Right now I'm working this problem as an XSL issue. Is this the right way
to proceed, or am I missing something?
user fills out and digitally signs the form, then submits it to a web
service, which among other actions, saves the form's XML to a DB and makes a
copy of the form XML available for download. I'm using the Source
querystring parameter and a custom redirector ASPX page to get back to my web
app on close...this works well for me so far.
I need to provide a viewing capability to the end user that shows the
signature. The view1.xsl is not displaying the signature despite my using
that workaround (i.e. including the <?xml-stylesheet type="text/xsl"
href="view1.xsl"?> instruction in the XML). The rest of the form displays
properly. I need this in order to support a large user community without
InfoPath. I also have an ESign requirement to make the saved XML file
available to the end user for storage on their PC. (Another way to express
this problem is: I want to display a *filled out and signed form stored as
XML* in the browser, but the XSL doesn't do so.)
Right now I'm working this problem as an XSL issue. Is this the right way
to proceed, or am I missing something?