* Use case
Someone creates a source file (ex: Word form) and manually generates a PDF of that file. They set a password on the PDF to prevent editing or other alterations of the file after it is downloaded from Vault. They wish to upload the source file (Word), to delete the auto-generated Viewable Rendition, and to upload their own Viewable Rendition (protected PDF) to Vault. The security may limit the users to only downloading Viewable Renditions, so a missing Viewable Rendition would lock a user out from downloading and using a document such as a form needed for manufacturing purposes.
* Current Vault behavior
There's a Vault setting (under Admin > Settings > Rendition Settings) called "Allow viewing and annotation of protected PDF files." This setting allows us to upload a protected PDF as a source file and Vault will successfully make that PDF the Viewable Rendition. This allows the PDF to be displayed in the Document Viewer for viewing and adding comments, and allows the download of the Viewable Rendition.
If I take that exact same protected PDF and try to upload it as the Viewable Rendition of a different unprotected document (ex: a Word doc), it doesn't work. Vault won't accept the protected PDF as the Viewable Rendition, and subsequently won't display it in the document viewer. A notification is sent saying Vault can't render the document. Users without access to the source file will have no option to download this document.
Based on our testing, this appears to be a version-by-version situation. If the source file is protected, the upload of the protected Viewable Rendition is allowed. If the source file is not protected, the upload of the protected Viewable Rendition is not allowed.
* Feature request
Please let the "Allow viewing and annotation of protected PDF files" Vault setting apply to all documents, not just those with a protected source file. This will allow us to upload our manually-generated, protected PDF as the Viewable Rendition of an unprotected source file so that it can be displayed to and downloaded by others.
* Additional info about the current behavior
The upload of the Viewable Rendition falsely appears to work at first as the Renditions section populates with the file data. However, the document viewer shows an error. Upon refreshing the page, the Renditions section is empty again. However, the API and renditions query still show a Viewable Rendition. This doesn't prevent the user from being able to upload a new unprotected PDF via the UI, but it looks like a data consistency issue based on my observations.
Please let me know if you need additional information about this request.
Please sign in to leave a comment.