Nov 23 2020 07:54 AM
Hello!
We have been testing the Universal Print feature in combination with pull-print scenario. It worked, basically, all things considered. But we also wanted to test the document conversion and this particular feature failed.
We enabled the feature under the corresponding section in the Universal Print management view. We have also configured the virtual printer (used for pull-print) to accept only PDF as content type.
Still, when we spooled a print job using a Windows client, the job data remained in OpenXPS format.
Is something wrong with our approach / configuration? Or is the document conversion not supported yet?
Does anybody tested this and can confirm that it works?
Mar 09 2021 06:15 AM - edited Mar 09 2021 06:34 AM
@abitor I seem to get the same results as you. There appears to be documentation to suggest this should work:
https://docs.microsoft.com/en-us/universal-print/fundamentals/universal-print-document-conversion
I note this also seems to happen when I use the xps mime type application/vnd.ms-xpsdocument.
The only content-type setting it seems to work with is application/oxps.
Probably worth mentioning that when the printer's content type is set to anything other than application/oxps, the print on the client fails with 'Error - printing'.
Mar 13 2021 07:03 PM
@abitor / @AndrewCardy First lets confirm a few things:
Here is how it should work (if you have PDF only as the content type):
Hope this clarifies.
Thanks,
Saurabh
Mar 15 2021 02:31 AM
Thanks for the clarifications. I think I might be miss-understanding the flow for virtual printers where payload modification is needed.
Currently my flow looks like:
1) Poll taskDefinition for tasks
2) Find a task in 'processing state', with a job that is 'paused'
3) Modify payload
4) Upload modified payload
5) Either redirect or mark as complete
Redirection in step 5 seems to work fine, and the job ends up with a completed status.
However, if I want to send the job to OneDrive, for example, I attempt to mark the task as complete, but the job remains in a 'pending' state. Am I miss-understanding what a 'processing' and 'pending' task means? As a task, should I wait to modify a payload until it's 'fetchable' or is that just for the downstream printer to know when it can be fetched?
Hope this makes sense. :)
Thanks!
Mar 15 2021 10:29 AM
@AndrewCardy Thats more or less correct. A few clarifications/suggestions though:
Setup Graph change notifications to be notified for a new print job in the queue (instead of Polling)
When notified about a task that is created for a new job (in paused state), get job details and download the payload
Modify payload - please note that if your printer is PDF, then
Job will be in PDF format already if coming from Windows versions 2004 or 20H2
Upload modified payload (has to be compatible with the printer including supported format)
Either redirect or mark as complete
Hope this clarifies.
THanks
Saurabh
Mar 16 2021 01:25 AM