This is primarily a question of opportunities more than instructions. I am a programming consultant working on a WSS project site system for my client. We have a document library in which files are downloaded to go through a complex approval process. With several steps in this process, we have an additional field that determines what the current status of the document is.
Now my client has become in love with the PDF watermark idea. He wants the document (which is already a PDF) to be watermarked according to the current status, so that at each stage of the approval process, the watermark will change.
One of the methods, the traditional PDF watermark method, is to have one “clean” copy of the document hidden on the site and create a new PDF file with a watermark from it at each stage of the approval process. Since the file name will never change, this new PDF file can be continuously uploaded to the public library, always overwriting the old version and simulating a “dynamically changing watermark”. However, at different stages there will also be people downloading clean copies with corrections and suggestions, apart from the complex nature of juggling around two libraries and the fact that we double the number of files saved. My client and I agree that this is not a practical choice.
What we would like to do is the ability to “modify” the watermark in a PDF file, so that we can only save one copy of the file. Unfortunately, from what I saw, in most cases, when you do something like a watermark, which by its nature should be “unchanged”, you will not be able to edit it later. So, is it possible to have a part of a PDF file that cannot be modified by anyone who downloads the file, but can be modified as part of a workflow or other object model process? Thanks in advance!
source
share