Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Adobe Summit 2023 [19th to 23rd March, Las Vegas and Virtual] | Complete AEM Session & Lab list

Documents as User service output


Not applicable
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.


3 Replies


Not applicable
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.


Not applicable
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


Not applicable
Hi Lee

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



The ultimate experience is back.

Join us in Vegas to build skills, learn from the world's top brands, and be inspired.

Register Now