Skip to main content

Submit data

Jadu Central can integrate with Perceptive Content to push PDF files (and any supplemental attachments) straight into Perceptive Content as a new Document, of a specified Document Type, within a specified Drawer, and within a specific Workflow stage (where applicable) through the Perceptive Content Integration Server API.

Once the Document has been created in Perceptive Content through Integration Server, the output document and any supporting uploaded files can be managed within Perceptive Content in the same way as any other Document uploaded directly through the ImageNow / Perceptive Content client application.

A Generate PDF action should be enabled before the Perceptive Content - Submit Data action.

tip

This action can optionally transfrom the generated PDF file into a TIFF image. A TIFF is useful when needing to annotate / stamp the file for instance. The PDF to TIFF conversion is handled through the imagemagick library.

Should this not be installed / available upon the web infrastructure, then the TIFF conversion option will not appear as a configurable option within the Control Center.

Creating a Perceptive Content Submit data template​

  1. Open a form, and navigate to Templates in the top navigation bar.

  2. Click the Create Template button. A window will open, asking which type of action we want to create a template for.

  3. Select Submit data under the "Perceptive Content" section, and click the Next button.

  4. Select a drawer, document type and optionally a workflow.

    Select whether to attach any supplemental user uploads and whether to convert the PDF to a TIFF image.

    The "Create as new document" option determines whether a name is set for the Document:

    • If the toggle is not enabled, the Document name will be set to be the filename of the generated PDF.
    • If the toggle is enabled, the Document name will not be set and therefore Perceptive Content will automatically assign one. In this case, it is important that Perceptive deems the Document to be unique. Uniqueness is determined by a combination of the Drawer, Document type and the values of Fields 1-5 (custom property values are not considered). If a matching Document is found, it will fail to create.

    Click the Next button.

  5. Complete the mappings in the final step. You can map a question, variable or logic formulae to each one. Alternatively enter manual text by typing it into the search box for the field and pressing the return key. Once complete, click the Save button to create the template.

note

Each file that is pushed within a single online form submission to Perceptive Content is a distinct page added to a single Perceptive Content Document.

Each Document that is created automatically is associated with the configured Document type, Drawer, Workflow Queue and provides the relevant User data values within the Document Key fields as configured as and when the form is submitted.

Using integrated component values​

If the form contains the Perceptive Content - Drawer Selector or the Perceptive Content - Document Type Selector Integrated Components, you can use their values within the template by selecting the following optionns:

  • Drawer: "Perceptive Drawer - Label"
  • Document Type: "Document Type - perceptive_content_document_type"

API Endpoint usage​

The current set of Integration Server API endpoints used overall by this process includes:

GET:/documentType.json
GET:/documentType/[id].json
GET:/drawer.json
GET:/drawer/[id].json
GET:/workflowQueue.json
GET:/workflowQueue/[id].json
POST:/document.json
POST:/document/[id]/page
POST:/workflowItem.json