We have no problems with a PDF form within Workspace when starting a process but when opening a new task assigned to a user we receive either the following 404 message inside Workspace or a message that says “Acrobat could not open ‘filename’ because it is either not a supported file type or because the file has been damaged…”.
How can we resolve this issue?
This usually occurs when you have a Document Form type variable in your process and in the Advanced Options of the variable you have selected the “Call the render service only once” checkbox.
While there are no issues associated directly with rendering only once, you need to ensure that you are passing a rendered PDF document to the next user in your process. To ensure that this is the case, open your form template (the XDP associated to this variable) and look for a hidden button with the name “FSSUBMIT_”. This hidden button is part of the Process Fields set of form fields you should have placed on your form initially. By default the form will only submit the XML Data Package (XDP) of the form and not the PDF itself.
If the task assignment step in your process uses the Document Form type variable that is configured to only be rendered once then the user attempting to view the assigned task will not be able to view the PDF as it has not been properly rendered.
To correct this problem change the Submit As parameter of the “FSSUBMIT_” hidden button on your form to “PDF”. This will ensure that the entire PDF itself is returned to your process and not just the data. Once this is corrected, re-save your form and start your process again. This will not correct any tasks that have already been assigned but new tasks should work well.
If you’d like to take a look at a working sample of this concept, feel free to download this sample.
By Lee Sutton
September 11, 2009