Information
  • Author: Appian Corporation
  • Type: Plug-in (Function & Smart Service)
  • Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
  • Industry: All Industries
  • Compatible Version(s): 23.2
  • First Released:
  • Last Updated:
  • Cost: Free
Share
Home » AppMarket » PDF Tools

PDF Tools

Overview

Contains multiple Smart Services and Functions for interacting with PDF Documents.

Key Features & Functionality

Smart Services:

  • Merge PDF - Merges multiple PDF documents into a single document.
  • Extract PDF Pages - Extracts a range of pages from an existing PDF into a new PDF.
  • Fill PDF - Populates the fields of a PDF Form and optionally flattens it disallow further changes.
  • Create PDF Content - Allows text to be added to a PDF with control over the style, position, and angle. An existing PDF can be updated or a new one created from scratch.
  • Convert PDF to Image - Creates an array of images or a multi-page tiff from a PDF.
  • Compress PDF - Compresses the images in the PDF to make it smaller.
  • Un-protect and Copy PDF - Using the document password, create an un-protected copy of a protected PDF.
  • Convert Image to PDF - Creates a PDF starting from one or many images. It also supports multi-page tiff images.
  • Encrypt PDF - Encrypts an existing PDF with a password.

Functions:

  • Get PDF Metadata - Retrieves metadata on the PDF: page count, title, author, security, encryption, etc.
  • Get PDF Text - Retrieves the text content from a PDF.
  • Get PDF Form Fields - Retrieves the populated form field values of an unflattened PDF.
  • Get PDF Signature Fields - Retrieves the populated signature field values of an unflattened PDF.
  • Get PDF Bookmarks - Retrieves the raw list of bookmarks in the PDF.

Anonymous
Parents

  • I'm having an issue when using FillPDF to populate fields in a LiveCycle document.  First I need to offer kudos that it works at all - the LiveCycle file format is pestersome and in my experience has been hard to work with.

    My issue is pretty straightforward: when I fill in a field in-process, and view the resulting document either in the Appian preview field, or previewed directly within Chrome, the filled-in value appears seemingly correctly.  But if I download the generated document and open in Adobe Reader, the field is apparently still empty.  If I open the file in a text editor, I'm able to find the value that had been inserted... but when I enter the value directly in Adobe Reader then save, the desired value shows up in additional places within the binary (again, viewed within a text editor).  I don't know what the exact issue is here, however it's preventing me from using Fill PDF to fulfill a use case of ours, which the older PDF from Template smart service fails at (in a worse way).  If anyone's able to offer some insight into this, I'd appreciate it.

  • in reply to Mike Schmitt

    Hi Mike, 

    Can you please tell me how do I configure fill PDF tool pluggin ? I need to create an editable form. Users will fill that pdf form with required values and submit. After submitting , we  can download that newly edited  pdf. 

  • in reply to Shikha

    sorry i never saw this reply before (community doesn't bother send notifications of general replies in these threads, for whatever reason) - the "pdf fields" parameter can just be passed a list of dictionary data where each dictionary has parameters named "name" and "value", where "name" will match the PDF fillable field's internal "name" parameter, and "value" is generally any text value. 

    I agree the documentation for this plug-in is a little vague as to how that works, though you can get a good idea by looking at the definition for the "PdfField" data type on page 13 of the documentation PDF.

Comment
  • in reply to Shikha

    sorry i never saw this reply before (community doesn't bother send notifications of general replies in these threads, for whatever reason) - the "pdf fields" parameter can just be passed a list of dictionary data where each dictionary has parameters named "name" and "value", where "name" will match the PDF fillable field's internal "name" parameter, and "value" is generally any text value. 

    I agree the documentation for this plug-in is a little vague as to how that works, though you can get a good idea by looking at the definition for the "PdfField" data type on page 13 of the documentation PDF.

Children
No Data

© 2024 Appian. All rights reserved.