3 Replies Latest reply on Oct 23, 2007 11:33 PM by (Nico_Meier)

Documents as User service output

(Nico_Meier) Oct 23, 2007 2:31 PM

Hello ES forum!

I think I've a comprehension problem (at least I hope so) regarding the user service, especially the input and output is confusing. Can anybody approve or disprove my follwoing conclusion: "The input of the user service can be a pdf or xdp form. The output of the user service is always xml data (form data)."

Does that mean that I'll never get the PDF form back from the user? What if the Workspace user places a signature or some annotations on the form? How do I get this additional information?

By the way: This was possible in LC 7.2 using a document variable as in- and output of the User QPAC.

Regards,
Nico

1. Re: Documents as User service output

(Lee_Sutton) Oct 23, 2007 4:50 PM (in response to (Nico_Meier))

The output from the user depends on what your "Submit" button has been designed to do. By default it will be set to return the data of the form but you can change the properties of the submit button on the form to return the PDF itself.

If you receive a PDF and not the XDP data you will need to use the importData and exportData functions to get data in and out of the form. A few more steps are required to work with PDF's when compared to XDP.

If you want to use a DigSig on your form then you will need to submit a PDF.
Like Show 0 Likes(0)

Actions
2. Re: Documents as User service output

(Lee_Sutton) Oct 23, 2007 4:52 PM (in response to (Nico_Meier))

FYI, your form in the workflow should be a "Document Form" and the input / output will be the root of the variable, ie: /process_data/yourdocvar
Like Show 0 Likes(0)

Actions
3. Re: Documents as User service output

(Nico_Meier) Oct 23, 2007 11:33 PM (in response to (Nico_Meier))

Hi Lee

excellent post, great help. It works excactly that way. Have a nice day!

Thanks,
Nico
Like Show 0 Likes(0)

Actions

Go to original post