User Profile
AndrewCardy
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: Document conversion
Saurabh_Bansal 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!2.9KViews0likes2CommentsRe: Document conversion
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'.3.2KViews0likes4Comments
