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 list of bookmarks and associated page number in the PDF

Anonymous
Parents

  • Hi! 

    We have a problem when we use getpdfflieds on a corrupted PDF. Sometimes our users upload this kind of PDF documents and we don't know how to control it. Would it be possible that this implementation exists in the current plugin and at least the function doesn't fail? It would be enough for us to throw a null. 




    Thank you!

  • in reply to mikelGran

    Hi mikel,
    tbh this will be hard to maintain properly. I mean we are talking for a reason about "corrupted PDF". 
    And if you dont have a valid PDF, how can the function be working on a reasonable level as "PDF tool" function?
    What would be your expected behavior? No error?

    kind regards,
    Richard

  • in reply to mikelGran

    to me more dangerous than helpful. I my personal opinion an alert should be created in a prod environment if a node fails and this is done the best way with an error message and a failed node in a process model instance. If it runs to smooth there is a high chance you miss this behavior, that something was not like it supposed to be. So its in general not the worst way to do it, but i get where are you coming from, I see here rather an issue why there are many cvorrupted PDF files ;) 

  • in reply to Richard Michaelis

    Hi, thanks for the reply! Unless there is another way to check in Appian, if there is the PDF is formed correclty, exactly that could be a good behavior.... A null might be fine. A null should mean that the function could not get any fields from the PDF. If the function response is null, it means there is no metadata and should mean that something is going on with that PDF and it is invalid. 

Comment
  • in reply to Richard Michaelis

    Hi, thanks for the reply! Unless there is another way to check in Appian, if there is the PDF is formed correclty, exactly that could be a good behavior.... A null might be fine. A null should mean that the function could not get any fields from the PDF. If the function response is null, it means there is no metadata and should mean that something is going on with that PDF and it is invalid. 

Children
  • in reply to mikelGran

    to me more dangerous than helpful. I my personal opinion an alert should be created in a prod environment if a node fails and this is done the best way with an error message and a failed node in a process model instance. If it runs to smooth there is a high chance you miss this behavior, that something was not like it supposed to be. So its in general not the worst way to do it, but i get where are you coming from, I see here rather an issue why there are many cvorrupted PDF files ;) 

© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.