top of page

Perceptive Content E-form Basics



  • Each form has one data definition that is coded using XML.

  • Data definitions contain all of the fields needed in a string format.

  • Anything that is not defined within the data definition cannot be accessed once the form is closed.


  • The presentation is the front-end of the form. This defines what the form looks like and defines functionality of each field. This is also where to define what to pass to the server-side lookup script.

  • These will mostly contain XSL, XML, JavaScripts, CSS and images.

  • The XSL will work with the data definition to pass values from the user (or server-side functions) into the data definition.

  • Shared Presentation are files that is shared among a department. No files can be named the same across departments in the shared presentation section unless they are configured to be shared across departments.

  • Each form can have more than one presentation.


  • Lookup iScripts retrieves all values needed from outside sources like databases, CSV files, and web services.

  • This is also used to grab values that forms cannot retrieve but iScripts can such as workflow history of the document.


  1. In the management console, select the department the form needs to be installed in.

  2. Click on “forms” tab on the left panel.

  3. Click on “manage form components” in the top middle section of the management console.

  4. In the “data definitions” tab, click “add” on the right side of “manage form components” window. Browse to the data definition that is already created (XML file) and click “open.”

  5. If shared files are needed in the “shared files” tab, click “add” on the right side of the “manage form components” window. Browse to all the shared files needed, select them all and click “open.”

  6. In the “presentations” tab, click “create” on the right side of the “manage form components” window.

  7. Add a name and description of the presentation. Click “OK.”

  8. Click on the newly created presentation in the middle of the “manage form components” window and click “modify.”

  9. In the “files” tab of the presentation window, click “add” and browse and select all of the presentation files needed for the form. Click “open.”

  10. If needed shared files, click “select shared files” and select all of the shared files needed for the presentation. Click “ok.”

  11. Press “OK” until the management console shows up.

  12. Click “new” on the right of the management console. Add a name and description of the form (this name will define the form and is used in iScripts to retrieve the form).

  13. Click on the new created form and click on “modify.”

  14. In the “components” tab, select the data definition in the data definition section.

  15. Click “select” and select all presentations needed for the form (usually only one is needed) and click “ok.”

  16. In the security tab, find and select all users that can’t and can access the form and determine the security for each presentation.

  17. Form is created. Forms are usually access through workflows which can be controlled through the management console.


Forms that need to be accessed outside Perceptive Content can be accessed through a web browser with Form Server. Users do not need to be a Perceptive Content user to access form server e-forms which creates form documents in Perceptive Content when submitted.


  1. In the Management Console, select the department that needs the form server form.

  2. Click on ‘Document Types’ on the left side panel.

  3. Click on ‘New’ on the right side and name the Form Server Document Type. This will be used to define the document.

  4. Click on the newly created document type and click ‘Modify’.

  5. In the ‘General’ tab, check ‘Is a form’ and select the e-form from the Form list. Click ‘OK’.

  6. Browse to inserver/etc and open up imagenowforms.xml.

  7. Copy and Paste the ‘DocumentForm’ section nodes (image on the left) to right above or below that section.

  8. ‘FormName’ will be the name of the document type, ‘QueueName’ is the queue that the form will route to when submitted. ‘Drawer’ and ‘Field1’ through ‘Field5’ are the created document’s index keys.

  9. ‘DataParams’ are the parameters passed into the form using the URL of the form.

  10. Restart ‘ImageNow Server’ in Services.msc.

  11. The form can now be accessed through the web browser with the URL pattern of this: http://HOSTNAME:PORT/imagenowforms/fs?form=DOCUMENTTYPE


Recent Posts

See All


bottom of page