Form rights for Reader XI

The Adobe Acrobat XI SDK Release Notes state, "Beginning Acrobat XI, Form Rights are available to all documents irrespective of whether the documents are Reader extended or not." When I use importXFAData() in the document-level Javascript, everything works fine; however, if I use exportXFAData(), an error is thrown. Are Form Rights no longer required for ALL properties and methods when using Reader XI, or only a select few?

To clarify, the error that is thrown reads, "NotAllowedError: Security settings prevent access to this property or method."
In the Acrobat XI SDK release notes:
And the exportXFAData method notes the following in its quickbar:
So, if the "F" doesn't apply, then what's the problem? I've tried putting the method in a folder-level script with an enclosing app.beginPriv() and app.endPriv(). Still doesn't work.

Similar Messages

  • Enable "Save" rights for Reader using LC Server

    Hello All,
    To enable the "Save" rights for Reader I can use Acrobat Pro menu option Advanced -> Enable Usage Rights in Adobe Reader...
    What is the option in Reader Extensions console that maps to this right? Also, what service would this map to in Reader Extension WSDL?
    Thanks.
    Regards,
    JK

    Thanks.
    If that is the case please let me know if the following mapping between RE webservice and RE browser UI is correct.
    enabledFormFillIn                     - Basic form fill-in
    enabledFormDataImportExport   - Import and Export form data
    enabledSubmitStandalone         - Submit outside web browser
    enabledOnlineForms                - Database and web service connectivity
    enabledDynamicFormFields      - Add, delete and change form fields
    enabledDynamicFormPages      - Create pages from templates
    enabledBarcodeDecoding      - 2D bar decoding
    enabledDigitalSignatures      - Digital signatures
    enabledComments                - Commenting
    enabledCommentsOnline      - online commenting
    enabledEmbeddedFiles           - Embedded file attachments
    This will help decide the correct WS call.
    Regards,
    JK

  • 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

  • How to make a pdf (form) accessible for reader in Adobe Acrobat x pro?

    Hi guys, i have bit of a problem here as i am new to the Acrobat pro X 
    Using Acrobat pro 9 i always could save a LiveCycle pdf form with permission to fill and save as a reader user. now i have upgraded to cs6 and i have no clue how to do that anymore. The half of the options are gone and i can't access the older Acrobat pro anymore. 
    Does anyone know how to save a pdf form using Acrobat X for adobe reader users giving permission to read and save my pdf files?

    For Acrobat X go to File-> Save as->Reader Extended PDF
    This will embed the reader extended rights in PDF.

  • Making fillable forms usable for Reader users

    I create fillable forms in Adobe Acrobat X Pro and I need to know how to make it so that they can be filled out and saved (in their filled-out form) by users of Adobe Reader. I have tried the advice in this article: http://help.adobe.com/en_US/acrobat/X/pro/using/WS58a04a822e3e50102bd615109794195ff-7e0d.w .html, but when I save them as Reader-extended pdfs and then open them in Reader, I can't fill them out. If I save them as Reader-extended pdfs and then choose "save a copy", the resulting copy, when opened in Reader XI, can be filled out and saved, but it doesn't work in Reader X. I need a solution that works for all recent Reader versions!
    I am about to tear my hair out over this issue! I just need our clients to be able to fill out forms and save them with the data still in them in Reader!

    Working solution for "Can't save data to a PDF using Adobe Reader 11 (Dynamic form created in LiveCycle ES3, extended using Adobe Pro X)"
    I've been reading the posts in this thread and other threads, and many users seem to have a "similar" problem with data being put in to an "Extended PDF", but that data not being saved when opened in Adobe Reader.
    This issue has been happening at my place of work as well and I have found a work around.
    Firstly, let me explain what we have in place:
    Windows 7
    Adobe LiveCycle ES3 (10.0.2)
    Adobe Acrobat Pro X (10.1.10)
    Adobe Reader (11.0.06)
    Adobe Extension Server 9
    The Steps leading up to the issue:
    I created a Dynamic form using LiveCycle ES3
    Saved the XFA file to a Dynamic PDF
    Opened the PDF in Acrobat Pro X, and extended it (and saving under a new file name)*
    Open the PDF in Reader 11 and open the extended PDF, enter some data, save the PDF and close Reader
    Re-open Reader and the previously saved PDF with my data in it
    Once I re-open the file, the data is gone
    The solution (in my case):
    (first 3 steps are the same as above)
    I created a Dynamic form using LiveCycle ES3
    Saved the XFA file to a Dynamic PDF
    Opened the PDF in Acrobat Pro X, and extended it (and saving under a new file name)
    Open Acrobat Pro X (not Reader), then open the extended PDF*
    Enter some data, and save the form normally and give it a new name
    Re-open the PDF form with Acrobat Pro X, with the saved data (which the data should be there), then delete the data I entered, then save the form.
    Open Adobe Reader XI, open the same PDF that "I saved from Acrobat Pro X", then "cleared" the data from it (not the original PDF I extended)
    Enter some data, and then save the file
    Re-open Reader, the same PDF, and the data should now be holding (not empty)
    *Even if I use the Adobe Extension Server to extend the PDF, the data still does not save from Reader.
    My guess as to why this is happening(?)
    I never had this issue when I was creating my forms using LiveCycle ES2.
    I am guessing that ES3 somehow sets different security/document/property settings when I save the XFA document to a PDF. When I extended the PDF afterwards using Acrobat Pro X, something "under the covers" of Acrobat Pro X breaks or resets the properties of the PDF.
    By re-opening the PDF in Acrobat Pro X, entering data, then saving the PDF under a new name, then going back and removing the data I entered; it seems to set new security/property/document settings that Adobe Reader 11 can handle?
    I've had to follow this same process each time I edit or create a form in LiveCycle, with a 100% success rate. With that being said, I have not seen what happens if the form I create is simple and "not dynamic".
    Hope this "rather bizarre" solution is helpful to some?

  • Enable Usage Rights for Reader 9

    Hi,
    I'm reading through a pdf document and I want to make comments.  Apparently I need to enable the usage rights through Advanced/Extend Features in Adobe Reader.  However, I don't have the Advanced tab (Reader 9).  Do I need to update to a newer version?  I've tried doing this but the download only proceeds so far then stops.  I've tried temporarily disabling my Antivirus but this doesn't change anything.  Any suggestions would be greatly appreciated.
    wus

    You need Acrobat Standard or Pro to Reader-enable a document. Reader itself cannot do this. Reader 10 allows you to add sticky notes and hightlight text annotations, even of the file is not Reader-enabled, unless the document has security restrictions that prevent it.

  • 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?

  • Alternative to webservice for data exchange in PDF (Form Export Rights in Reader)

    Hello,
    I'm exchanging data between my pdf and a web server. Basically, the pdf needs to get some xml string from the web server, alternatively send some xml string to it. This is now done using a webservice, and it works fine with the SOAP javascript object. However, it doesn't work in Adobe Reader, because (quote from the docs):
    "The SOAP methods connect, request and response are available only for documents open in Acrobat Pro and  Acrobat Standard and for documents with Form Export Rights open in  Adobe Reader 6.0 or later."
    It turns out I need to enable Form Export Rights to get webservices work in Reader.
    Now, I was wondering if there's another way to exchange data between my pdf and a web server that doesn't involve enabling those Form Export Rights in Reader.
    Note that I need to be able to parse the response string xml from the web server in pdf using its javascript API.
    Thanks for any suggestions,
    James

    Your only other alternative is to POST th einformation to the web server via a submit operation. This is the same as POSTING on an HTML form.
    Paul

  • I created a pdf form and then iported it to Forms Central for distribute. It is now loaded to my website and setup so a person clicks on the link to open the form. At this point they then have to go to upper right to open form using a different view. I wo

    I created a pdf form and then imported it to Forms Central for distribute. It is now loaded to my website and setup so a person clicks on the link to open the form. At this point they then have to go to upper right to open form using a different view. I would like the form to open directly in Adobe Reader form to make it easier to enter information. Thanks, Ike

    If you created it in Forms Central, you have to edit it there. I believe Forms Central is similar to LiveCycle Designer in that the form created is no longer able to be edited in Acrobat. I might be wrong, but that is my understanding. You add the submit button in Forms Central. Within Acrobat, you should be able to go to the forms menu and Manage Data to save the data to an Excel file. Others better with forms should be by to clarify things, but this should get you started. In the future you might find it better to post a forms question in the forms discussions.

  • Saving pdf form with extended Reader rights

    Hello,
    I want to save form changes without further confirmations in Reader version X ("Save" and not "Save as...").
    - If you use a pdf form with enabled Reader rights, you should be able to save any changes made in form field by using the Reader.
    - To save changes use "File / Safe" or press CRTL+S
    Result:
    - Save-as window will appear
    - After choosing save button you will be asked to overwrite existing file.
    Expected results:
    File should be saved without further confirmations! In Reader version 9 there was no problem with that.
    Does anybody had the same problem and found a solution?
    Regards,
    Christian

    OK, it seems to be a typical "it's-not-a-bug-it's-a-feature"-problem. But I found no way to avoid the overwrite question during saving. I noticed that the question appears only the first time when you click on the save button. If you do further changes in form fiels and click a second time on the save button the document will be overwritten without additional warnings. Maybe it's a feature to prevent users from overwriting empty forms by asking for a new filename and so on..
    However, we are using the reader in conjunction with a document management software and the overwrite warning disturbs our enterprise workflow. So the only insufficient solution for my problem is to downgrade all users to version 9 again.
    Hope next version of reader will be better in disabling unwanted features ;-)
    Regards, Christian

  • Reader rights for adding attachment

    Hi ,
    is it possible to apply reader rights for adding attachments when output pdf form in sap?
    where can i find more document on controlling reader rights?
    thanks and best regards.
    Jun

    Hi Jun,
    here is a sample code for seting usage rights:
    FORM use_rights
      CHANGING p_pdf TYPE xstring.
    DATA: l_fp           TYPE REF TO if_fp,
          l_pdfobj       TYPE REF TO if_fp_pdf_object,
          l_dest TYPE rfcdest.
    MOVE cl_fp=>get_ads_connection( ) TO l_dest.
    l_fp = cl_fp=>get_reference( ).
    l_pdfobj = l_fp->create_pdf_object( connection = l_dest ).
    l_pdfobj->set_document( pdfdata = l_pdf ).
    DATA: lt_rights TYPE TFPURIGHT.
    PERFORM my_usagerights CHANGING lt_rights.
    l_pdfobj->set_usagerights( default_rights = space  rights = lt_rights ).
    l_pdfobj->execute( ).
    l_pdfobj->get_document( IMPORTING pdfdata = l_pdf ).
    ENDFORM.
    FORM my_usagerights
        CHANGING pt_rights TYPE TFPURIGHT.
      DATA: ls_rights LIKE LINE OF pt_rights.
      REFRESH pt_rights.
      ls_rights-right = if_fp_pdf_usage_rights=>formrights.
      ls_rights-value = if_fp_pdf_usage_rights=>formright_fillin. "Ukladani
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>formright_export. "Export XML
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>formright_add.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>formright_delete.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>formright_submitstandalone.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>formright_spawntemplate.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>formright_online.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-right = if_fp_pdf_usage_rights=>signrights.
      ls_rights-value = if_fp_pdf_usage_rights=>signright_modify.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-right = if_fp_pdf_usage_rights=>annotrights.
      ls_rights-value = if_fp_pdf_usage_rights=>annotright_create.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>annotright_delete.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>annotright_modify.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>annotright_copy.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>annotright_import.
      INSERT ls_rights INTO TABLE pt_rights.
      ls_rights-value = if_fp_pdf_usage_rights=>annotright_export.
      INSERT ls_rights INTO TABLE pt_rights.
    ENDFORM.
    Michal

  • Basics: Save Rights Enabled for Reader

    I have an involved Applescript that handles/creates pdfs for our clients. The only thing I need Acrobat Pro 9.4 to do is to create the Rights Enabled option for Reader and save as into a new file. Ideally, without having to use the GUI interface.
    Reading up on the API, every reference to Rights Enabled seems to be in the context of Forms, or Live Cycle. None of those would seem to be required? And there are several atomic levels that can be rights enabled, it seems, which is good. Even if I have none of these environments, is the effect of the menu command of "Enable Rights ..." the same as saving each of these options to a new pdf? I'm assuming this is an application level javascript?
    Starting to work the javascript examples in the API is frustrating because everything after "var jsNum = 10" fails to seem to work and the errors reported don't make sense in the context I'm seeing them. i'm not dumb, just inexperienced with javascript. Its frustrating when the examples copied and pasted error out, etc.
    Some pointers to guides that give me better context would be appreciated, so as not to clog the forum with newbie chatter, thanx, sam

    Thanks for explaining why I couldn't determine this.
    Thanks for the offer of explaining what I'm seeing with the basic API examples. The second one is here, from page 51, example 4.2 of the Adobe Acrobat SDK document:
    // Create a new PDF document:
    var newDoc = app.newDoc();
    // Insert doc1.pdf:
    newDoc.insertPages({
    nPage: -1,
    cPath: "Macintosh HD:tmp:1.pdf",
    // Insert doc2.pdf:
    newDoc.insertPages({
    nPage: newDoc.numPages-1,
    cPath: "Macintosh HD:tmp:2.pdf",
    // Save the new document:
    newDoc.saveAs({
    cPath: "Macintosh HD:tmp:11.pdf";
    // Close the new document without notifying the user:
    newDoc.closeDoc(true);
    SyntaxError: missing } after property list
    13:Console:Exec
    undefined
    OK, counting lines it appears to be after the newDoc.close statement. But to my way of thinking all the braces, parentheses are closed.
    I tried removing the returns after each cPath statement thinking perhaps I shouldn't have a return before the closing }); a long shot. Looking at my /tmp directory, I don't see a new pdf called 11.pdf.
    Clearly, there's something basic I'm missing here that I'm unaware of the context, thanx, sam

  • Preventing Extend Features for Reader when distributing form

    I am distributing a form created in LiveCycle and will have the form responses automatically tracked on an internal server. The distributed form is not sent out via email, but rather stored on the shared internal server. With Acrobat Pro 9, the distribute form function automatically extends Reader rights, which I do not want to happen with the form being stored on a shared server. The form will have secure information in it & responses are sent to a folder that will have write capabilities only.
    Any info on how to prevent the extenstion of Reader rights when distributing the form is appreciated.

    Something happened to the file after the time that it was Reader-enabled. It was modified in a way that invalidates the digital signature that controls whether the usage rights are valid. I seem to recall the GoLive can be configured to modify (optimize somehow?) PDFs when it uploads them, and you definately don't want this to happen for Reader-enabled documents. I don't have GoLive, so I can't check what setting it is, but you should be able to look for yourself. A workaround would be to upload via some other means, such as FTP. I'd be interested to know if this makes a difference.

  • Problem with enabling usage rights for Adobe Reader

    Hi All,
    I have designed a form using Live cycle. From Live cycle I export it as PDF. As a final step, I open the PDF by using acrobat professional to enable usage rights for Adobe Reader. As soon as I enble the rights it saves the document with a different name, which is fine. However; at the same time it also runs the postsave events from the form and removes a couple of objects. How do I avoid this? My form has very little code:
    There is a drop down field called 'LearningSolutionsAdvisor' which has the following code on PostSave event:
    NewHorizons.Page1.LearningSolutionsAdvisor::postSave - (FormCalc, client)
    LearningSolutionsAdvisor.access ="readOnly"
    There is 'Save' button which has the following code:
    NewHorizons.Page1.Save::click - (JavaScript, client)
    app.execMenuItem("SaveAs");
    NewHorizons.Page1.Save::postSave - (FormCalc, client)
    Save.presence = "invisible"
    I thank you for your help in advance.
    Regards,
    Girish

    This video is very helpful as it explains exactly what I want to do:  Extend Features in Adobe Reader, to allow my readers to save their changes.  However, I do not have that option in my version of Adobe X Pro 10.1.4.  Can anyone explain to me why I don't have that option, and what an alternative would be?  

  • Reader Extended form rights issues in Reader X

    Hi all
    I have a form which is reader extended, which is submit to a SOAP message service(just the form XML) after the form has been filled out. This all takes place over an internal network. When we clicked on the submit button in Reader 9, it would ask if you wanted to allow the connection to the webservice, and would send it through once we click "Allow".
    In Reader X however, the gold bar at the top of the form pops up when we click submit, and after choosing to trust the form, it reloads the whole form, and all of the changes made are lost.
    Is there any way to programatically tell Reader X to allow the form to make webservice calls(even if theres a security popup) when the form is first opened?
    Regards
    Ross Malan

    Yes, it can, especially if you are using Reader 8 or 9.  There were some issues with earlier reader versions that required the positive confirmation of the Reader Extensions credential with the certificate revocation list (CRL), which required that it had to go out to the web to fetch the CRL.
    Depending on how deep you want your testing methodology to go, I'd take a virgin windows machine that does not even have reader installed, download or otherwise transfer the RE installer and your form and take it offline.  Then install Reader and open your form.  It should open with the additional rights with no problem.
    But the bottom line is that it is designed to work for your use case.

Maybe you are looking for