1.3. Terminology

action

Actions are units of work that are fired in response to form events. For example, sending an email containing a hyperlink to a document or displaying an alert message.

alert

A message box that is displayed to the end user during the data entry process.

boolean logic

A rule based on true or false, yes or no or the presence of one of two clearly opposed values.

calculated field

A field that is calculated by, or from a value(s) of another field.

click wrap signature

A type of signature whereby a user enters in their name and it is inserted into the generated document.

client ID

A container within LincDoc that stores all field definitions, source documents, generated documents and data.

codelist (code list)

Codelists are objects within LincDoc that drive drop down choice lists, e.g., a form question that has a yes/no answer. There are multiple types of codelists available, including simple, advanced, and JDBC.

condition

Conditions are boolean expressions that are evaluated throughout the lifecycle of an eForm in response to form events. When the conditions are true, then certain actions are allowed to happen based on the configuration of the eForm.

condition to display (sometimes abbreviated as c2d)

Logic used to conditionally display or hide a field or section

conditional text/paragraph

Refers to a snippet of text inside a Microsoft Word (or OpenOffice) source document that is conditionally shown in a generated document. The condition of the text is evaluated at document generation time, if the condition is true then the text is included else it is not included.

CSV

Comma Separated Values – a type of text output where each field's value is separated by a comma. Values that may contain commas may be surrounded by double quote characters. For example: "Jane","Smith","123 Main Street","Southtown","IL","65099"

DANG

Data And Number Generator – a key component of the LincDoc administrator UI used to create conditions, actions, and calculations

data entry

The term used to describe the process of an end user filling out the form fields of a particular eForm or document package.

DDL

Acronym for drop down list.

document inclusion logic

Boolean logic rule that selects a document based on the existence of a specific field or fields.

document package

Extends what an eForm can do by allowing one or many related Word or PDF source documents to be assembled based on predefined business logic. Enterprise Edition only.

document repository

A searchable storage area where documents and data are saved. LincDoc has its own internal document repository, and third party repositories such as Laserfiche are also supported.

document viewer

The window that the generated document is displayed in.

DRAT

Document Refinement Annotation Transformer. An extension of the LincDoc markup language for more sophisticated field resolution scenarios.

drop down list (DDL)

A form control that when clicked on presents a list of choices from which the user must choose one.

eForm

An electronic web form composed of a single Microsoft Word or PDF document. The document contains zero or more field placeholders. An eForm is also comprised of field details, sections, conditions, actions, events, and lookups.

end user

Any person who uses LincDoc to complete a preconfigured eForm or document package.

event

Events help describe significant points in time during the lifecycle of an eForm or document package. Examples of events include "on load" which fires when an eForm is first executed, or "on generate" which fires when the end user has completed the data entry process and is ready to generate their document.

field

A placeholder inside a source document for the purpose of filling with data either manually or from a database.

fields document

A source document used for the sole intention of field placeholders only, it is never meant to be part of a generated document. This technique is often used with more complex document packages which have many source documents: the fields document consolidates LincDoc fields to a single entity.

flattening

The processes of removing the ability to change field values in a PDF form

function

A system calculation that returns a single value given zero or more inputs.

global field

Field definitions that can be applied to any field of the same name or pattern when creating a new eForm.

inclusion logic

The use of Boolean logic to determine if a paragraph or document should be included when generating a new document.

input constraint

A simple input mask or regular expression that can be applied to a field to enforce what data is allowed for a field.

JDBC

Acronym for Java Database Connectivity.

LDAP signature

A type of signature in LincDoc whereby the user "signs" the document by being prompted to re-enter their LDAP password at the time of signing. Often used in combination with the Active Directory integration module.

LDAR

An acronym that stands for "LincDoc Archive". An eForm definition can be exported as a .ldar file, then imported to another LincDoc VM.

LincDoc administrator

The person responsible for creating eForms and corresponding field elements, conditions, lookups, actions, etc. within the LincDoc system for the end user community.

LincDoc markup language

The term used for "<<...>>" and "<<<...>>>" expressions inside Microsoft Word documents that respectively identify fields and conditional paragraphs.

lookup

A query that searches for data in an external system.

LWSA

LincWare System Administration Portal. Portal for all server level configuration options.

multi-phase signatures

The term is used to describe a document that contains multiple signature fields, and those signatures are not all signed in the same browser session: the signatures happen in different phases.

multivalue (or multirow or pound) field

This is the terms used to refer to the concept of fields that take on multiple values. For example, an eForm that captures a list of part numbers. These are sometimes called "pound fields" because in the LincDoc markup language they always are terminated by a pound sign.

OpenForm

The term used to describe when an eForm is launched in a separate browser window (or iframe), and none of the normal LincDoc desktop controls are present (e.g., no top toolbar with buttons for search, run, help, logout, etc.). This is the preferred way to run eForms for end users because it is very directed in the sense that all they can do is complete the form in front of them.

paragraph inclusion logic

A condition that shows or hides a paragraph in a generated document. Only applies to Word source documents. Enterprise Edition only.

parse/reparse

The process of resolving/finding fields in a document. A reparse operation typically takes place whenever a source document is altered.

PDF

Acronym for "portable document format".

pound field

Synonym for multivalue field.

required condition

This refers to a condition attached to a particular field that determines if the field must be non-blank before proceeding. Just before document generation time the condition is evaluated. If it is true and the corresponding field is blank then processing stops – the user is shown a warning message that they must fill in the field before proceeding.

section

The term for a container/area within an eForm that contains one or more related fields.

source document

A Microsoft Word or PDF document containing zero or more fields. In the case of Word, the LincDoc markup language is used to denote fields. For PDF, FDF fields are used. Adobe Lifecycle forms are also supported.

source document library (templates)

The library of documents available to users in LincDoc.

subject matter expert

When designing a new eForm, this is the person who has the knowledge and expertise to provide guidance on the finer details of the form. This person also has a thorough understanding of the business processes and high level workflow logic that often accompany an eForm.

synchronization/sync/on sync

An event indicating that a mobile device (e.g. iPad) is pushing locally saved forms/data to a LincDoc server.

TIFF

Acronym for "tagged image file format".

token based name

The term used to describe the process of substituting tokens for form field values, especially in the case of naming a generated document. For example, the admin can create a token based name in which one of the tokens is the "lastName" field collected from an eForm, plus other tokens for the current date, followed by the file type ".pdf".

Topaz signature

A type of signature using one of the supported devices offered by Topaz.

TortoiseSVN

An optional third-party plugin for MS Windows Explorer that allows administrators to check-in and check-out documents and eForms.

UI

Acronym for "user interface".

use case

This term refers to describing a situation that highlights a particular set of features and/or requirements of an eForm. For example, a form that requires several signatures from the same signee is a good "use case" for LincDoc's bulk signing feature.

user

Shorthand for "end user".

user profile

Stores Name, email address, password, and password reset question