Restricting print options with LC:RM ?

[Paulo_de_Paula]

Hi There,

We are trying to solve the followin problem - some insurance policies are sent to customers in PDF format, but for buiness reason such insurance policies can not be printed more than once. Never.

We think that LC:RM shoul be the rigth way to apply such prining restiction to PDFs, but searching on dicumentation we could not find the answer.

Any suggestion ?

Regards,

[Former Community Member]

This functionality does not exist for Rights Management as part of a policy definition, meaning you can either allow the print permission for a user, or you disallow printing for that user.  That being said, there is a way to "partially" create the behaviour you are looking for by using "Rights Management" events.  You can build a process that "listens" for the "print" event and then does something based on that event, such as revoking the document so that it can no longer be opened, or modify the policy to remove the "print" permission for the user\users.

Unfortunately, this solution as there are a few short comings...

1)  The print event will be captured and soon as File > Print is selected, even if the user cancels the printing and doesn't actually print the document

2)  A user could print multiple copies during a single print event

Regards

Steve

[Former Community Member]

Hi,

another opportunity is to create an external authorization handler. For more detail, check please the LiveDoc of Adobe LC ES: http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/help/000910.html.

I think, the use case described in this topic is exactly that, what you need.

Kind regards,

Angel

[Rui_Esteves]

One way to do it (based on Angel's link) is:

First you have to set up an External Authorization Handler in order to be able to act on the print event of a given document. To do so, you can follow the Print Once External Authorization Sample that Adobe provides (see Angel's link). Compile it, build the Jar file and install it in you Livecycle using Workbench (install as a component, don't forget to activate it).

Then you have to create a new policy that uses this External Handler and allows print and enables audit (you can set it up with an Anonymous account to circumvent login on the end-user's side).

Don't forget to set up the HTTPS interface in your App Server, otherwise the audit won't work.

Hope this helps.