Справочник Пользователя для Adobe acrobat 7.0.5 sdk

Скачать
Страница из 122
89
Rights-enabled PDF Documents
Creating Rights-enabled Documents
10
C re at i n g   R i g h t s - e n a b l e d   D o c u m e nt s
PDF documents can be “rights-enabled” using Adobe LiveCycle Reader Extensions . 
Developers cannot programmatically rights-enable a PDF file. 
During the design process, a PDF document may be created through the usage of Adobe 
LiveCycle Designer, Adobe LiveCycle Forms, or Adobe Document Server. The document 
creator can assign appropriate usage rights using Adobe LiveCycle Reader Extensions. The 
PDF document is made available on the Web, and users can complete the form on the web 
site, or save it locally and subsequently complete and annotate it, digitally sign it, add 
attachments, and return it.
In effect, Adobe LiveCycle Reader Extensions enables additional functionality within Adobe 
Reader for a given document. After the user has finished working with the document, those 
functions are disabled until the user receives another rights-enabled PDF file.
One major advantage of Adobe LiveCycle Reader Extensions is that it supports data 
automation through XML-based representation and transfer via SOAP, ensuring seamless 
integration with business logic and advanced data transport capabilities available within 
enterprise applications.
For more information, see the Acrobat JavaScript Scripting Guide.
Accessing Additional Usage Rights
When a rights-enabled PDF is opened, Adobe Reader changes the user interface and 
enables additional features. Previously unavailable APIs, for both JavaScript and plug-ins, 
are then available to developers. 
To check whether a PDF document has rights enabled, plug-in developers can use the 
PDDocPermRequest
 methods. 
JavaScript developers cannot programmatically access or assign additional usage rights 
with a PDF file. For this reason, it is advised that try-catch blocks be used around methods 
which might violate the constraints related to the document’s rights.