HomeUsing LincDoc 3.0Software requirementsSoftware requirements for administrators

2.2. Software requirements for administrators

Overview

Most of administering LincDoc is through a web browser. We strongly recommend Google Chrome 15+ or Firefox 9+ for administering the LincDoc system.  The reason for this is that the admin UI is highly Javascript intensive, and those particular browsers have more powerful Javascript engines. Note that for end users the UI is less complex and so it is OK to use older browsers. Administering LincDoc from a mobile web browser is not supported.

Forms authoring tool

LincDoc can work with these types of source documents:

  • PDF: use Adobe Acrobat Pro version 9+ (or Adobe Livecycle Forms)
  • DOC/DOCX: use Microsoft Word 2003+
  • ODT: use OpenOffice (or LibreOffice)

There are some limitations to be aware of when choosing your forms authoring tool. This table summarizes those differences.

 
Source document format .doc .docx .odt .pdf

Supports multirow?

yes

yes

yes

no

Can produce TIFF output?

yes

yes

yes

yes

Can produce PDF output?

yes

yes

yes

yes

Can produce DOC output?

yes

no

no

no

Can produce DOCX output?

no yes no no

Can produce ODT output

no no yes no

Supports conditional paragraphs? (LincDoc EE only)

yes yes yes no

Supports cryptographic digital signatures? (requires the LincDoc signature module)

only when converted to PDF at generation time only when converted to PDF at generation time only when converted to PDF at generation time only when saved as PDF at generation time

Can be used for iPad-based forms?

no no no yes

Supports repagination?(LincDoc EE only)

yes yes yes no

Connector

LincDoc Connector software is used to write out documents and data to third party platforms. Currently there are connectors for writing out to a Windows file share, and Laserfiche. The connector software installs as a Windows service to the server on which the documents and data are being written to. The service is written in Java (Java 6 to be precise), so Java must be pre-installed to the Windows server first.

This page was: Helpful | Not Helpful