Additional usage rights

I cannot realize where I write the following code. would you tell me details?
What should I do before writing it as wel as after?
var sh = security.getHandler("Adobe.PPKMS");
var dir = sh.directories[0];
var dc = dir.connect();
dc.setOutputFields({oFields:["certificates","email"]});
var importantUsers = dc.search({oParams:{lastName:"Smith"}});
var otherUsers = dc.search({oParams:{lastName:"Jones"}});
this.encryptForRecipients({
oGroups:[
userEntities: importantUsers,
permissions: { allowAll: true }
userEntities: otherUsers,
permissions: { allowPrinting: "highQuality" }
bMetaData: true
eMailList = "";
for ( var i=0; i < importantUsers.length; i++)
eMailList += (importantUsers[i].email + ",");
for ( var i=0; i<otherUsers.length; i++)
eMailList += (otherUsers[i].email + ",");
// Now email the secured document.
this.mailDoc({
cTo: eMailList,
cSubject: "For your eyes only",
cMsg: "Please review for the meeting on Friday."
Developing Acrobat® Applications Using JavaScript™
Adobe® Acrobat® SDK
Version 8.0(page 115)

Thanks for answer.
So if I write in JS document, button, Text field, it will run perfecly?
I have written above JS in "Run JS" of action tab of button. However it shows the following message. Would you tel me what I should now?
NotAllowedError: Security settings prevent access to this property or method.
Security.getHandler:1:Field Button1:Mouse Up

Similar Messages

Enabling Usage Rights In A Form Created In Older LC, But Updated In Newer Version of LC

Has anyone run into the situation where updates have been made in a form that was originally created in an older version of LC with a newer version not enabling the usage rights for Reader? I have a form that I created that was done in an older version, and I recently needed to make updates to it, and I now have Adobe Pro X. Anyone who has Adobe Standard or higher can access the form and fill it out, but if someone only has Reader, they really cannot do anything with it. It has created a problem in my office. Once we figured out what was going on, I had to find someone with Adobe Pro 8 to pull up the form and enable the usage rights in Reader. I'm really hoping it is that I am missing something, but I don't know.
Here is how the form is set up as a default:
Thanks for any help that you can give me!
Maribeth

Sorry it took me so long. Things have been crazy, but here's what you do:
File > Save As > Reader Extended PDF > Enable Additional Features...

Save and File Attachment usage rights for adobe reader

With Acrobat Pro is there any way to save a pdf that has both save usage rights and file attachment usage rights?
It seems that if I save the pdf with save the form data usage rights then I can no longer use createDataObject or setDataObjectContents methods when viewing with adobe reader or acrobat.
createDataObject and setDataObjectContents require 'File Attachment' usage rights, which from the behavior I am getting totally disjoint from the save usage rights.
I have no trouble using submitForm method with save usage rights applied to the pdf.

Thanks for the replies, I also want to verify that a pdf created with acrobat that uses createDataObject or setDataObjectContents will no longer function properly in acrobat after saving the pdf with the additional usage permissions. Is there any documentation that points to what functions are crippled by saving the pdf with the various choices of extensions enabled? It seems as if I save the pdf with any type of extended usage rights for reader, then the pdf functions as if it was opened by adobe reader even if I have it open in acrobat?

Repeating Subforms after applying Usage Rights

Hi Guys,
I've been going crazy trying to get this problem solved over the last couple of weeks. I unfortunately can't post the PDF due to privacy issues, but I'm hoping you might be able to point me in the right direction for what might be causing the issue.
The Problem
We're running into a problem once the LiveCycle PDF is opened in Acrobat Pro and has Usage Rights enabled. Once we save the PDF, then re-open it, the repeating subforms start misbehaving. For example, when we re-open that document, rather than the subform having 1 instance (as it should be default), it opens with multiple instances of 2, 3, 6 or 20).
This issue only occurs once Usage Rights have been enabled on the document, and it's always the same number of instances being repeated.
Document Details
The PDF document was created in Indesign then imported into LiveCycle to apply the interactivity. There are a total of 17 pages
There are several subforms throughout the file on various pages. Each of these subforms has a button below them which allows the user to add additional instances of the subform (using the built-in script that LiveCycle generates). Each subform has a minimum count of 1 and maximum limit set to 20. The "initial count" has been set to 1, but it appears LiveCycle removes this value if it is the same as the minimum count.
This document does not tie into any database. It is simply an interactive document that allows users to show/hide pages based on the checkboxes they tick on the first page (just changes page visibility). The idea being, the customer can save the form once they've completed the fields required, then email it back, so save functionality is a requirement (which is why we need Usage Rights).
What I've Tried So Far
I've done a lot of reading on the subject, and I've seen people mention that subforms with non-unique names or empty subforms can cause the issue. I've checked through the document and all subforms have a unique name and there are no empty sub forms.
As a way to trying to narrow down which elements might be causing the issue, I resorted to deleting multiple pages from the document to track down a specific element that might be causing the issue, however, i didn't have much luck with this. The removal of the majority of pages other than the single repeating subform resulted in the subform repeating itself 6-8 times (can't remember specifically, but it previously repeated itself 20 times)
Any Ideas?
I know it's a bit difficult without being able to see the document directly, however I'm hoping someone might have a suggestion for anything I may have overlooked. Is it simply Usage Rights screwing things up, or is there potentially something in my code that conflicts with the usage rights. The thing I find most confusing about this scenario is the apparently randomness for how many instances show up. The first subform pre-loads with the maximum limit available, but the rest of the forms most load with only 2 instances (when they also have a max limit of 20 items).
I've read a few forums where people suggested Reader Extensions, however according to Adobe's system requirements it doesn't seem to match what we're trying to achieve. There is not database interaction at all - we only require the ability of users to save the PDF locally.
If anyone can offer suggestions for where I might need to look to sort the issue out, I'd be most appreciative. Thanks!

Hi,
Your description of the problem is very detailed. Send me a private message if it is possible to send the form to an individual instead of posting it publicly.
Here is a thread on repeating subforms, that may help: Saving finished Form duplicates some subForms I used a console.println line of script to try and help identify the problem.
I would try and minimise the number of flowed subforms and only use them where they are required for the contents of that subform. In all other cases use positioned subforms.
Minimum count only serves a purpose when you have a button that allows a user to delete instances. A minimum count of 1 means that the user can delete instances, but not the last remaining instance. Unless you need this, you could take this out.
I don't think the problem is because the form is enabled. There must be something else going on in the background.
Try opening the Javascript Console in Acrobat/Reader (pressing Control+J) and see if any warnings/errors come up. Also put in a console.println script to display the nodes in the console.
Good luck,
Niall

Enable Usage Rights Resetting in Adobe 8.1.2

Hi!
I've created a series of forms using Livecycle that need to be sent off to multiple recipients, who need to be able to save/print/etc. from Acrobat Reader.
Using Professional 8.1.2 I've been Enabling Usage Rights with Acrobat Reader but when I open the forms up again the next day the rights are no longer enabled and I have to enable them all over again! It doesn't happen every time - they stick with some forms - but most of the time they seem to be reset and it's getting very hard to keep track of which forms are still enabled.
Is this a known problem? Any ideas??

I've double checked my fonts, and the only fonts used are Myriad Pro which I'm pretty sure is embedded across Acrobat.
Do you know what kind of scripts might cause the change? I've got a couple running in the forms - the ones that I've written myself are:
1. calculation scripts (just pretty simple numeric calculations on inputted data)
2. an if... then script that runs on a dummy e-mail submit button that clicks the actual submit if a check-box is ticked
I know there's also script running in the 'current date' field, which is the only thing I could think of that might be running every time the form is opened, and which might explain why the rights stay until the next day. However, if I try to recreate the problem by changing the date on my comp calendar and re-opening the forms, the usage rights are still sticking there fine.
Do any of these seem like likely causes, or are there other scripts that might be hidden around on the form? What's the best way to check?
Also, all of my scripts were written in Formcalc instead of Javascript - would this make a difference?

Adobe reader does not open usage right enabled files in Ubntu 8.0.4

I have a series of pdf files with the usage right enabled in adobe acrobat.
When I try to open them in linux Ubuntu 8.0.4 the adobe windows flashes for a second and the disappears. I tried to run the command in a terminal but it doesn't give me any error or warning message. I am just wondering if any one else has been able to resolve this issue.

Thanks Farshid for sending the file.
We have tried using the file you sent on multiple linux distributions with Linux Reader 8.1.2 but we're not able to replicate the issue you're facing. We've tried on Ubuntu 8.04 as well and haven't seen any issues.
Could you share more information, includign the version of the reader youre' trying to use (you can see that at Help > About Adobe Reader).
Thanks,
Gaurav

Acrobat 9 Standard and the Digital Signature usage right

Acrobat 9 Standard is apparently able to apply certain usage rights to a document. I am trying to confirm whether or not the digital signature usage right is included. The
Acrobat 9 product comparison seems to indicate it is not, but the online help implies that it is.
Can someone with Acrobat 9 Standard confirm this for me by testing a document that you've enabled for use with Reader by attempting to sign a digital signature field with Reader?
George

In the office area, the Pro version might be good to have for the forms and other features. For the general library, Reader is probably adequate. Actually allowing PDF creation on public machines can be an issue. In a small libary system, Acrobat might be reasonable where you do not have to deal with a large, diverse population. However, for basic PDF creation, only Std is needed. Having both AA8 and AA9 on the same machine can lead to problems. However, if you remove one, you will likely have to repair the other.
The problem with older versions is that they may not properly read some of the newer PDFs that might be downloaded. For the latter, you could install the latest version of Reader, but you need to be aware that you may have to deal with issues of right clicking (windows) on a file and selecting which application to open a PDF with. For forms and some editing, the Pro version would be good to have. You also have PDF Optimize and PreFlight with the Pro version that generally are not including in the Std version.
To help compatibility with the files you create, you can select Start>Printers>Adobe PDF preferences (right click on printer). In the settings tab>Default settings> select at least Std or better Press or Print and then push edit. Under the general tab select the compatibility and set it to AA8 so that every thing is compatibile with the oldest version of Acrobat you have.
If you have more than one computer in the office, you might consider having AA8 on one and AA9 on the other. Do check and be sure you have licenses for whatever you have and that someone has not come in and installed a pirated version. Also be sure you keep the original CDs and licenses (or if they were downloaded, burn the downloaded version to a CD as an archive and write the SN on the label).
Now that I have confused you, are there more questions?

Enabling Usage Rights with Adobe Pro 6.0

Is there any way to enable usage rights in Adobe Acrobat Pro 6.0?
Am i forced to buy a newer Adobe product in order to do this?
Is there software online that allows me to do this?
I would like to allow users to markup drawings in Acrobat Reader.
Any help would be very much appreciated...

OK, let's go again...
Q: What is available online to enable usage rights?
A: Nothing.
Q: If i don't have to purchase more software through Adobe, what are my
options?
A: You do have to purchase software from Adobe, namely Acrobat Pro.

Form submit not working even with usage rights enabled

Hi everyone,
I created a form in Acrobat 7 professional (mac version), then used Acrobat 8 (windows version) to enable usage rights.
I have the following javascript code attached to a submit button:
this.mailForm(true, "[email protected]", "", "", "RSVP", "Yes! Please register me.");
When I test the form in the full version of Acrobat by pressing the submit button, it automatically launches my email program, attaches the form's .fdf file and addresses the email, ie. just as the code directs. The problem is that when I try and test in either Acrobat 7 or 8 Reader, it won't work, ie. I press the submit button but the email program doesn't open etc. As I said, I've already enabled usage rights in Acrobat 8 so I don't know why it's not working.
Can someone tell me what might be going wrong?
Appreciate any help offered.

pjones, Tembowa is correct.
if you look up the mailForm in the JavaScript reference guide, you see it's marked with the letter 'F', meaning that the PDF requires Form rights in order for this method to work in Reader.
Now as you rightly say you can use Acrobat 8 pro to extend a PDF with usage or Save rights. (These will be marked by the letter 'S' in the JS reference guide.)
In short when you enable a PDF in Acrobat pro, you 'only' assign Save rights. This is not sufficient for the mailForm method to function in the free Reader.
For mailForm to work in the reader you need to assign a PDF with form rights, which can only be done using LC Reader extensions.
Hope this clarifies things.

I have a recently acquired iPhone 4. Is it true if I am using PhotoStream to upload photos to my PC via iCloud, photos are only pushed when wifi is available? This means I don't have to worry about extra data usage, right? Thank you.

I have a recently acquired an iPhone 4. Is it true if I am using PhotoStream to upload photos to my PC via iCloud, photos are only pushed when wifi is available? This means I don't have to worry about extra data usage, right?
Thank you.

Correct.
On an iOS device, new photos you take will be automatically uploaded to your photo stream when you leave the Camera app and are connected to Wi-Fi. Note: My Photo Stream does not push photos over cellular connections.

Enabled Usage Rights turned off when form filled out in Acrobat vs Reader

I created a form in Acrobat Pro 9 and enabled the usage rights so the end user can save the form. Anyone who opens it and fills it in using Reader has no problem.
However, if one user begins filling it in using Acrobat (so far only Std to my knowledge), and then either that user or another opens it to continue in Reader, the form fields are no longer fillable. It has become a read only pdf.
I didn't see anything in the properties I could set to avoid this. Is there a way to save the form to avoid this problem?

You mentioned AA7 users. I don't think they can not edit the form at all, just fill it in unless you saved it with backward compatibility. The PDF to them would be like using Reader and that may be the difference for AA7 use. In fact, I am not sure how far back in compatibility the user rights will extend if activated and it might be lost if backward compatibility is used with the PDF Optimizer. Those are some thoughts anyway about the comparisons you made. The other guys are the forms experts and I am not in a position to debate their comments, only offer a possible explanation.

Why is Enable Usage Rights creating Duplicate Pages?

I have created a dynamic PDF form in LiveCycle Designer ES 8.2. The form is formatted correctly and has no duplicate pages when examining the not-enabled form in Adobe Acrobat Pro 9. However, when I attempt to Enable Usage Rights so that external users can download the form and fill in the fields, the ENABLED version has duplicate pages. I do not understand why because the original document does not have these duplicates - they only appear when I Enable the Usage Rights. I cannot delete these duplicate pages in the Enabled version. Please help!

hello, these are the files where firefox stores its cache - you won't need ccleaner (in fact it will only slow things down as you've already noticed, since those files have to be recreated after the next start of the browser), you can also clear the cache with the built-in mechanism in firefox: [[How to clear the Firefox cache]]

Enabling usage rights in Adobe Reader corrupts PDF text

Hi,
I've created a registration form using Open Office writer which has editable fields. I convert this to a PDF and then add a signature field in Acrobat 8.
At this point everything works fine, all the editable fields etc convert across, but I want people to be able to sign and save the form in Reader, so I check the "Enable Usage Rights in Adobe Reader" feature and save it. Now when I open the PDF in either Acrobat or Reader all the text is completely corrupted and illegible (see image).
Any idea what's going on here?
Thank you
Paul

OK, here you go.
https://www.dropbox.com/sh/y5mkwmw5h8wvxjk/2psk7418jq

Reader Extensions / Usage Rights

I followed the procedure in this paper from Paul Guerette to set Usage Rights to my forms, but at run time, it pops up a message:
"This document contained certain rights to enable special features in Adobe Reader. The document had been changed since it was created and these rights are no longer valid. Please contact the author for the original version of this document."
On the top of the window, below the Reader toolbar, it says "you cannot save the data typed into the form". There's no "commenting" icon in the toolbar, no digital signature icon either. Looks as if it's not Reader Extended.
How do I fix this?
my ES version is GM, no Service Pack not patches applied.

My RE was the last step as well, it was after the "Workspace enable form" step.
I have run another test. I removed the RE step, and it's working the same way as before; everything worked on a desktop that has the Acrobat Pro.
I then launched the form/process in Workspace on a desktop that only has Reader-8, the form got rendered in the browser, and I saved the PDF (a blank copy, no data).
Then I ran this PDF through the RE browser interface, and it was successfully Extended. When I opened the extended PDF, there's a Digital Signature icon, the "message" (which was entered when applying the rights) was behind the "i" button; but there was no commenting icon (unlike some other non-form PDF files, those files got an extra commenting icon). There was no pop-up warning.
Some other "form" type of PDFs also didn't get the Commenting icon after extended through the browser interface. I thought we could put some yellow stickers onto forms before? ES/Reader-8 doesn't allow you to do that anymore?
I have run another test, this time I removed all the scripts behind the Form:ready event, there's no other script. But it didn't help, I still got the popup warning. So, what could have caused it to think that the form got modified after the ApplyUsageRights ??? Why the Rights don't stick?

Batch processing for Enabling Usage Rights for Reader

Hello,
We have a lot of documents that we are converting to fillable pdfs using Acorbat 9 which will then be sent out via email to be filled by users. Since there are 50-100 different files, is there a way to use Batch Processing to enable usage rights to Reader for all those documents? Any help or advice is appreciated.
Thank you,
Sam

There's no way with Acrobat. You can with Adobe's LiveCycle Reader Extensions product, but it's likely not worth it for just this.
George

Additional usage rights

Similar Messages

Maybe you are looking for