Questions

Hi,  I'm getting this cookie-related warnings from my chrome developer console.   It looks like to be caused by the PDF embed API SDK file.  Please check. thanks,

even with a registered URL (document settings 'Basis-URL') an embedded link forces the alert box "do you want to open this link...".The same PDF-file opened in a current Acrobat Reader DC does not do this, just opens the browser with the URL from the PDF page. Is there a UI setting to avoid the alert box?Thanks a lot! Werner

I'm looking to rapidly create a pdf form from a Word document that is editted frequenctly, and needs to be converted to a pdf frequenctly. Right now, I would just save the word document as a pdf, open Acrobat, use "Prepare Form" and draw out 100+ text fields and checkboxes. Is there any feature within the Document Generation API that allows me to use templare tags in Word for these fields to generate fillable fields during conversion. Maybe someting like this: {{checkbox(30px)}}. I'm not seeking to do this within the Cloud.

Our DOCX documents have tracked changes enabled. Red with strikethrough are tracked for deletes and blue for chnages. When the Plugin for Power Automate is used, the document is created with blue for everything. Is there a way to keep our colors or define them?

Adobe has been hard at work the last several months offering new ways to automate document processes in your apps and workflows. In March, Adobe announced Adobe PDF Tools connector for Microsoft Power Automate to add PDF actions in your flows. In March, Adobe released Adobe Document Generation API, which will enable you to generate Word and PDF documents based on data dynamically. In September, Adobe provided PDF Extract API as a private beta.   This month, we have new updates to make it easier for you to generate your documents and extract data from your PDFs dynamically. In this post, let’s walk through what’s new. Adobe PDF Tools API is now called Adobe PDF Services API As we began offering our APIs across different applications and platforms, we felt it essential to change the name to reflect the offered services better. Therefore, from now on, Adobe PDF Tools API will now be called Adobe PDF Services API.   When you subscribe to Adobe PDF Services API

Is there an easy way to change the note color back to default or to another color? because when you add a note and then change the color to red and then add another note this one is still red. that's what I want to change.  best regards

We have created a document in HTML and used CSS to resize it to the size of an A5 document. If we call the API via the create request and set the key "contentAnalyzerRequests" in the body with the following value: { "cpf:inputs": { "params": { "cpf:inline": { "print": { "includeHeaderFooter": true }, "pageLayout": { "pageHeight": 5.8, "pageWidth": 8.3 }, "json": "{\"k1\": \"v1\", \"k2\": \"v2\"}" } }, "documentIn": { "cpf:location": "InputFile0", "dc:format": "application/zip" } }, "cpf:engine": { "repo:assetId": "urn:aaid:cpf:Service-e2ee120a2b06427cb449592f5db967e7" }, "cpf:outputs": { "documentOut": { "cpf:location": "multipartLabelOut", "dc:format": "application/pdf" } } }We get the following response back:{ "cpf:inputs": { "params": { "cpf:inline": { "print": { "includeHeaderFooter": true }, "pageLayout": { "pageHeight": 5.8, "pageWidth": 8.3 }, "json": "{\"k1\":

Hi,  I'd like to have this one more API for creating new annotations, as currently there are only addAnnotations(). I'd like to use this API to create new annotations from my code or at least creating new replies to existing APIs. I wonder if this API will be implemented soon?  thank you, 

According to the documentation -  if enableAnnotationAPIs is true then I should  be able to see annotations that were added programmatically  If annotations APIs are enabled (enableAnnotationAPIs: true) and includePDFAnnotations: false, then:                     - The PDF Embed API does not display existing annotations, but will display new ones.  -               -  Any annotation added or updated either from the UI or API is not saved to the PDF buffer; therefore, no Save button appears in the top bar. However the only way I can see annotations that were added programatically is if   showAnnotationTools is enabled - however I don't want the annotation tool bar to be enabled because I don't want users to manually create/alter annotations- I should be able to see annotations that were added programatically without enabling t

Only last week came across PDF Embed API by Adobe and I am trying to integrate this on our web application.Have got the credentials generated for the domainHowever in local, getting this warning when doing inspect:DevTools failed to load SourceMap: Could not load content for https://documentcloud.adobe.com/view-sdk/2.10.3_1.10.0-1257dda/private/main.js.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE What am I doing wrong?

Hello, i'm using the .net package to create pdfs from html and I need to hide the header and footer, but this configuration is not working.How can I remove the headers an footers from the documents?

I think I've done everthing correclty, I'm geting this:File preview not availableHere's the code used--see screenshot

I am trying to find a way to convert PDF to DOCX with creating proper table structure <table> <tr> <td> etc.The tricky part is that the conversion should be done without user interaction. I pass the information about the PDF location via API or the document itself and I would like to get DOCX at the outputIdeally, it should be able to run directly on the server.

Can PDF Tools API be used to extract page annotations? When yes how? Because I've not been able to find any documentaion or samplecode on the subject

When using document generation api, is it possible to automatically obtain the current page number and total number of pages and then automatically assign the value of page footer? Does pdftools-sdk-samples have such a function?

In my webportal i just required to view pdf and print. but this not allowing me to simply print the doc. Other featues looking good that it allowes hiding panels which are not required like download, side panel etc. But i stucked when i am trying to print the pdf. It says download pdf and then print. I dont thing its a mature product created by adobe.

A embedded link forces the alert box "do you want to open this link..." When this link is toward the bottom of the .pdf, it's unreadable and the buttons are unavailable; it is placed such that most of the alert runs past the limits of the container, see example below.  This makes it quite unusable. How can this be fixed?

Our clinet is facing issue in PDF Embed API. When they are opning any PDF on their corporate computer. They simply get a white screen. Meanwhile they can access same PDF on their personal mobile. When I asked them to give me snapshot of there console then it's giving them Uncaught ReferenceError: AdobeDc is not defined error.Buisness team is not facing any such issue , PDF is opning fine for the as well for me.Not sure what would be causing this issue. Do you have suggestions for how we go about fixing this? e.g. is there something that the user can download like a plug-in? do we need to talk to their IT?Any help is appreciated. Thanks,Ashwani

I'm unable to add localhost as a domain, and therefore I cannot review the presentation of PDF Embed until I push to production. Is there a way to overcome this?

Hello, We are evaulating the Documentation Services API's to support the generation of some PDF documents. The documents are not big, but tables within the documents might end up containing a few hundred rows. While testing the document merge with the sales order json and doc provided in the Java samples (https://github.com/adobe/pdftools-java-sdk-samples/tree/master/src/main/java/com/adobe/platform/operation/samples/documentmerge) we found that the PDF were rendered correctly but the rendered was very slow or timed out after a number of minutes:2 products in the json payload: PDF merging time is 23 seconds100 products in the json payload: PDF merging time 49 seconds500 products in the json payload: Operation times out after ~ 5 minutes. It is important to note that the generated PDF files are not particularly big (under 1Mb). nor is the json payload (under 250Kb). The issue seems to be related to rendering a high number of table rows. We would appreciate to know if

Hi,We are planning on using PDF Embed API to render the PDF in our application. While navigating through the document rendered, we noticed that blobs are getting downloaded from document cloud. On further inspecting, it looks like a preview of the document is returned from Adobe Document Cloud.Details:blob:https://documentcloud.adobe.com/c02ae5ee-0768-4d6f-9906-6f3875099df8Downloaded Blob:Netwok Stats: This is conflicting with the details shared in the security document: https://www.adobe.com/content/dam/cc/en/security/pdfs/AdobeDocumentServices_SecurityOverview.pdf Can you please help us clarify this behaviour?

Trying to include the Adobe Viewer with<script type="text/javascript">   document.addEventListener("adobe_dc_view_sdk.ready", function(){and activating the content security policy with the Apache configurationHeader always set Content-Security-Policy "script-src 'self' documentcloud.adobe.com"without 'unsafe-inline' results in the following error message in Safari:"Refused to execute a script because its hash, its nonce, or 'unsafe-inline' does not appear in the script-src directive of the Content Security Policy."How can I get the script running without using 'unsafe-inline'?

I am using the PDF Embed API to display a local PDF and am experiencing an issue where the PDF Viewer is stuck on "Opening Document 0%" about half the time that I open it.  I've followed the sample for React provided by Adobe.  I've tried using a URL as well as a promise.  I've tried doing a timeout call to see if it was an async timing issue but it still happens.  Has anyone else experienced this?  I know it's not a problem with the PDF because half the time it loads correctly and everything is fine.   React Typescript Implementation: const Bill: React.SFC<BillProps> = (props) => { const bill = props.billDetails; const viewSDKClient = new ViewSDKClient(); viewSDKClient.ready().then(() => { //const blob = await getBillImageLocation(String(bill.controlNumber)); //const url = window.URL.createObjectURL(blob); viewSDKClient.previewFileUsingFilePromise("pdf-div", getBillImageArrayBuffer(St

I've tried "sized container" and "in-line" mode, but in both I am unable to simulataneously have the PDF fully display, have no extra space in the container, and have it work on multiple screen sizes. Is there any way to have this work on multiple screen sizes? The behavior in the demo https://documentcloud.adobe.com/view-sdk-demo/index.html#/view/IN_LINE/Bodea%20Brochure.pdfdoes not match what happens in production with the code it says is being used; pdf remains 800px on smaller screensizes, exceeding the screen width.

I am working with PDF file of 43 pages (18.2 mb). For some reason we get 500 error during its export.Error could be solved if I reduce the number of pages required for the export.{ requestTrackingId: 'tJEXfIuVZnonTHw1J0sqmtujeg2DB7zt', statusCode: 500, name: 'ServiceApiError', errorCode: 'INTERNAL_SERVER_ERROR' }In the unit description I see that "Per API request for a single document output, up to 50 pages". Are there any additional limitations and requirements to check before the export?