Adobe acrobat 7.0.5 sdk User Manual

Page of 122
Rights-enabled PDF Documents
Differences between Usage Rights and Reader Enabling
10
88
Permissions enabled by usage rights may be disallowed if:
the document is encrypted and the security handler is set to disallow any of these 
operations, or
the document contains DocMDP settings that do not allow these operations.
For more information, see the Acrobat JavaScript Scripting Guide.
Differences between Usage Rights and Reader Enabling
You may not develop an Adobe Reader plug-in without approval from Adobe.  You must 
use Adobe’s web-based application to describe your plug-in and submit information to 
Adobe. Adobe reviews it and either approves or rejects the application. The application and 
the Adobe Reader Integration Key Licensing Agreement can only be submitted as a web 
form. Information can be found at: 
 
Note that there is a fee to get the enabling key, and that your plug-in can only use a 
restricted set of APIs. As with all plug-ins, reader-enabled plug-ins must be installed on 
each user’s machine (either through an installer or by the user), and the plug-in is then 
available to all PDF documents used on that computer.
PDF documents with additional usage rights contain rights-enabling information within 
each individual document, so no additional installation is needed. The APIs available to 
both plug-in and Acrobat JavaScript developers depends on which usage rights are set for 
each individual document; you cannot make APIs available to all documents as with 
Reader-enabled plug-ins. Using APIs available with additional usage rights requires no prior 
approval by Adobe. 
Form
 barcode plain text
Annot
 online
Form
 online
Embedded File
 create, delete, modify, copy, and import