Controlling #views/#prints and getting audit event notifications

Question

We have an evaluation of LiveCycle up and running, and we are negotiatons for purchase. In doing some quick proof-of-concept work, we ran across a couple issues we are looking to get help with.
Background: We are working in .Net using LiveCycle web services. We can successfully apply a policy to a PDF using web services, and we can successfully manipulate a PDF using reader extensions using web services.
1. We see where we can apply validity dates in the Policy, but where can we limit the number of views or prints allowed on the document? Is this even controlled by the policy, or somewhere else? We see where we can assign permissions to principles, but this is more of "Can print" or "Can view offline" but not a control on the Quantity of prints or views. Is this something we can setup via the web interface, or is it something we need to supply custom java extensions for? And if we need to supply extensions, is there any way to point us in the proper direction? (this seems like it would be fairly typical usage)
2. How do we setup livecycle so we can get notified of audit events like "# allowed views reached" or "# allowed prints reached" or just "someone viewed this PDF". We are a .net house, so is there any way to get notifications of this externally? Or do we have to supply some sort of extensions to LiveCycle? And if we have to supply an extension, can you point us in the proper direction?
Many thanks for any insights we can get on these issues.
Michael

Answer 1

Rob
If you want to revoke or expire a document based on user action (i.e. printing or viewing the document) then you can do this by capturing the print or view event in your process and then have your process perform the desired steps (i.e. revoke the document).
If you simply want to have the document revoked after a certain date or for it to only be valid for a specific period, you can do this as part of the policy definition itself.  When you create a policy, you can specifiy one of the following:
1)  Document will not be valid after x days
2)  Document will not be valid after this date: x
3)  Valid from "date 1" to "date 2"
or
4)  Document is always valid  (which means you would need to revoke\expire the document manually or via a process)
This functionality has always been a part of Rights management.
Regards
Steve