Kirill Bondar 9/14/2012 6:32:58 AM
@Simon - "you could display a watermark like "copy".
After the user opens the "legal" copy of the document she can print it multiple times, save or send it somewhere for later printing, or, with some technical skills modify the content that otherwise appears read-only.
On the other side the user can open the document, send it to the printer, close it - while the printer is doing the job and then discover, say, paper was jammed or the cartridge is empty. The user needs to re-print the document but there is no way to do it since after the document was loaded the record moved to another state.
A decade ago, while I was working for another company, we were trying to solve similar task; but in this case it was a desktop application tied to customer's environment and we were controlling the whole process from button click to a printer state - unfortunately, web applications like TeamDesk have no such level of control.
To me, Slava is right - there should be two separate record states - one to allow printing the document and another to indicate the user is done with it and no "legal" document should be printed afterwards.