Home → Client Onboarding → Printer Friendly Version
You access your EOS Client Onboarding system by accessing a URL that is specific to your environment. When this URL is accessed, your EOS Client Onboarding system's login screen appears, allowing you to specify a username and password.
Note: Your URL is created and assigned to you during the initial EOS Client Onboarding system configuration phase. If you do not know your URL, contract Technical Support.
The login screen is your initial point of entry. It allows you to specify the following information:
You can access and edit some of your profile settings, if desired, using the profile button on the EOS Client Onboarding system's toolbar.
The EOS Client Onboarding toolbar displays several components. When used together, they enable access to simple management and administration features.
This drop-down list, the primary option in the interface, allows you to determine which form will be manipulated by other toolbar buttons. The list itself contains the unique identifier and full description of each form that you can access.
Note: EOS Client Onboarding customers will usually have only one form.
When the form is selected, you can run the form. You can also search for documents generated from the form.
Once the form has been selected using the Form Selection drop-down list, clicking run opens the item in the Document Viewer, and allows you to begin entering data.
The search option allows you to locate and retrieve previously saved forms.
After selecting your form, selecting search will list all relevant content to which the specific user has access. You may select from previously saved search parameters or create new criteria.
The browse option opens the Browse dialog box, which allows you to view and manipulate folders and files in your directory structure.
The interface is also defined by individual user profile parameters, which can be set using the profile button. This user information is established according to the user's role within the organization's EOS Client Onboarding community.
For more information, see Customizing Your User Profile.
The help option provides a method for accessing EOS online help/documentation, opening a support ticket with the development staff, or viewing your license agreement. The current EOS Client Onboarding system (LincDoc) version information can also be found here.
The windows button provides you with access to the list of currently opened windows (if any), and allows you to optionally tile the open windows on the workspace.
Hidden window are shown in italics, and can be re-displayed by selecting them.
Closes the current EOS Client Onboarding session.
Several different views are used through the form creation process. It is recommended that you become familiar with these views before using the EOS Client Onboarding system.
Proceed to one of the following topics below for more information:
This view is used to actually input information into the completed form.
This view is accessed by clicking the run button on the EOS Client Onboarding toolbar.
Once the form's data is added using the Data Entry View, the form is submitted via the Submit button at the bottom of the Data Entry View, and the final form appears in the Document Viewer.
For more information, see Running a Form.
This view is essentially the same as the Data Entry View, except that it runs in a dedicated web browser window or tab, instead of in the EOS Client Onboarding interface.
The Document Viewer is used to display the "final" form, after the form has been created and submitted via the Data Entry View.
This view also allows you to download, email, and sign the form (if applicable). For more information on this view, see Using the Document Viewer.
This special view is launched from the Document Viewer.
For more information, see Signing the Completed Form.
This is a list of the most common terms used throughout this documentation:
Term |
Definition |
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. |
authentication provider |
See provider. |
batch signing |
A feature that allows you to sign multiple documents with a single signature. |
bulk signing |
A feature that allows you to sign multiple signature fields, in a single document, with a single signature. |
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 EOS that stores all field definitions, source documents, generated documents and data. These cannot be created at the user level, but instead are directly tied to your license key - as created when you acquired EOS. In most cases, you will only have access to a single client ID, although multiple client IDs can be purchased, if needed. |
codelist (code list) |
Codelists are objects within EOS that drive drop down choice lists. For example, 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 |
Logic used to conditionally display or hide a field or section. Sometimes abbreviated as "c2d". |
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 |
Short for Comma Separated Values, which is 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 |
Short for Data And Number Generator, which is a key component of the EOS administrator interfaced 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 |
A file created using an eForm of Document Package. Basically the "filled-in" version of an eForm or Document Package. Also known as a generated document. |
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. |
document repository |
A searchable storage area where documents and data are saved. EOS has its own internal document repository, and third party repositories such as Laserfiche are also supported. |
document viewer |
The window in which the generated document is displayed. |
DRAT |
Short for Document Refinement Annotation Transformer, which is an extension of the EOS markup language for more sophisticated field resolution scenarios. |
drop-down list (DDL) |
An eForm 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. It is also comprised of field details, sections, conditions, actions, events, and lookups. |
end user |
Any person who uses EOS to complete a preconfigured eForm or Document Package. |
event |
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 EOS 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. |
generated document |
See document. |
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 |
Short for Java Database Connectivity. |
LDAP signature |
A type of signature in EOS 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 |
Short for EOS Archive. An eForm definition can be exported as an .ldar file, and imported to another EOS VM. |
EOS administrator |
The person responsible for creating eForms and corresponding field elements, conditions, lookups, actions, etc. within the EOS system for the end user community. |
EOS 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 |
Short for 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. |
multitenancy |
A type of software architecture where a single instance (installation) of the software runs on a server, but is designed to virtually partition (divide) its data and configuration. In this arrangement, each client organization (known as client IDs in EOS) uses a customized, virtual application. In the EOS environment, multitenancy is used to separate sets of forms and data. |
multi-value field |
A repeatable field that takes on multiple values. These are sometimes called "multi-row fields" or "pound fields" (because in the EOS markup language they are always terminated by a pound sign (#)). These field types are only available in Word source documents. Example:
|
node |
A specific item within a repository, accessed via the Browse dialog box. Nodes can be documents, files, or folders. |
OpenForm |
The term used to describe when an eForm is launched in a separate browser window (or iframe), and none of the normal EOS desktop controls are present (for example, no top toolbar with buttons for search, run, help, logout, etc.). This method 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. |
parse/reparse |
The process of resolving/finding fields in a document. A reparse operation typically takes place whenever a source document is altered. |
|
Acronym for "portable document format". |
pound field |
Another name for a multivalue field. |
provider |
Also known as authentication provider. Acts as a container for a specific set of users and groups. They can be created to control application access. They are created at the client ID level, making them available to other users with access to your current client ID. |
required condition |
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. |
signature |
Both a person's name, used to formalize a document, as well as a general term for the information that applies to all form fields to which a signature itself is applied. |
signature receipt |
A signature feature that displays the actual signature used on a form, information about the signature (such as the name of the user who signed and the date/time), and provides buttons for downloading the corresponding signed form or just the receipt information to a file. |
signature stamp |
An image that can be used in place of a script font representation of a signature, and is a digital representation of your actual signature. |
source document |
A Microsoft Word or PDF document containing zero or more fields. In the case of Word, the EOS 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 EOS. |
SQL repository |
A back end storage system that is based on a relational database. Currently, this database must be either PostgreSQL or Microsoft SQL Server. Note: This feature is available with EOS version 3.3 and later releases. |
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. |
stamp |
An electronic record, used with signatures, that captures details essential to demonstrate the authenticity of the signature. |
superuser |
Similar to a Windows Administrator account, this type of user is given access to a large majority of the EOS system and its settings. Typically, a non-cloud installation has only one superuser account called admin. Cloud installations never have a superuser account for security reasons. |
synchronization/sync/on sync |
An event indicating that a mobile device (for example, an iPad) is pushing locally saved forms/data to a EOS server. |
TIFF |
Short for "tagged image file format". |
token based name |
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 |
Short for "user interface" or the portion of the application with which users directly interact. |
UUID |
UUID (Universally Unique IDentifier) values can be thought of as random strings such as: 7402b0a6-d4da-489b-9955-8cc3f87735cb. UUID generators are very good at never producing the same string twice. For every document generated in EOS (regardless of the repository type: SQL Repository, Laserfiche, or Docuware), a UUID is assigned that is 36 characters long. The DANG function DocID can be used to return this value. The value is actually internally generated the moment you start a brand new form (and never changes for that form thereafter). This value is critical to doing any kind of workflow with a document, and is used to create URLs that allow direct access to manipulate a particular form (editing, viewing, signing, etc.). For more information on UUIDs, click here. |
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 EOS's bulk signing feature. |
user |
Short for "end user". |
user profile |
Stores the user's name, email address, time zone, password, and password reset question. |
The EOS Client Onboarding system has the ability to configure and save searches, within your repository, to locate previously generated documents.
This feature provides more flexibility when trying to find documents, and can be helpful when your repository contains a large number of generated documents.
The search feature is executed at the form level and accessed using the search button on the EOS Client Onboarding toolbar.
You can view an existing search's configuration options, as well as create and configure new searches, using the Search dialog box. Once configured, you can use these searches to locate generated documents in your SQL repository.
Proceed to one of the following sections below for more information:
You can select a previously defined search using the search drop-down list in the top left corner of the Search dialog box.
Once selected, access the search configuration options and edit them, as desired.
You can create a new search using the search drop-down list in the top left corner of the Search dialog box.
The new search is saved.
By default, the search configuration options are hidden on the Search dialog box.
You can access them using one of the following methods:
Note: You may need to resize the Search dialog box (click and drag to the right) to see this triangle icon.
The configuration options are displayed on several tabs immediately below the thin line/triangle icon (and above the search results table).
Proceed to Specifying the Configuration Options below.
Once you access a search's configuration options, you can adjust the options, as desired, to verify that the search locates the correct generated documents in your repository. These configuration options are displayed in several tabs on the Search dialog box.
Proceed to one of the following sections below for more information on each individual tab:
The options tab allows you to specify a description for the search, which can be helpful for allowing other users to easily understand how to use the search.
This description will appear immediately below the search's name in the search drop-down list.
The filter tab allows you to specify exactly what is searched for when the search is executed.
Using at least one condition, determine what the search will attempt to locate in your repository.
In the following example, all documents whose med_plan field contains the text gold will be returned by the search.
Tip: Use the + and - buttons to add or remove conditions, as necessary to define your search filters.
The columns tab allows you to control the information that appears in the search results table (in the lower half of the Search dialog box). This table displays the documents that match your search criteria, after a search is executed.
The columns tab is divided into the following three lists:
The queue tab allows to you specify if the configured search will be automatically executed when certain users log into EOS.
To use this option, you need to activate it by selecting the corresponding check box (it is not active by default) and then specify a user type that will use the option.
In the following example, the option has been activated and the search will automatically be performed for all users assigned the user-admin role.
When a user with this role next logs into EOS, a Queue dialog box similar to the following example will appear, showing the automatically executed search results.
Tip: You can click the button adjacent to the wrench button (highlighted below) to change from the Queue dialog box to the standard Search dialog box.
In addition, if this option is enabled for multiple searches, tabs appear at the top of the Queue dialog box. One tab appears for each search that uses the option. In the following example, two searches appear.
Once you have completely configured your search, you need to save your changes.
You can delete any search if it is no longer useful or necessary.
Once a search is configured, you can execute it, and view the results (the generated documents in your SQL repository returned by the search).
Proceed to one of the sections below for details:
A search is performed (executed) on a form-by-form basis using the Search dialog box.
Once a search is complete, the results are displayed in the search results table in the bottom half of the Search dialog box. You are also provided with additional options that can be used with the returned list of documents.
Tip: This customization only impacts the current search. If you want to permanently edit the information displayed in the search results table for the current search, see Specifying Search Column Settings.
Note: The column order is search-specific, so you can specify different column orders for different saved searches.
Tip: You can select individual documents (using their corresponding check boxes), as shown below, or you can click the check box in the column's heading to select all listed documents.
In the following example, two documents have been selected.
You can use EOS's internal file browser to store and access documents and related files (source documents, branding images, etc.) in a customizable directory structure. The files are actually stored in and accessed from your SQL repository.
You can also perform other actions using this feature including, but not limited to:
The Browse dialog box is comprised of three main components, which are shown in the diagram below.
The toolbar, at the top of the dialog box, contains the buttons which allow you to perform specific actions within this dialog box. The contents of the toolbar are dynamic, based on the type of item selected in the lower portion of the dialog box, as well as the permissions you have been granted on the selected item.
The navigation tree, on the left side of the dialog box, is used for selecting individual folders or subfolders. You can click the button immediately above the navigation tree to return to the top level directory. This button is labeled with the name of your repository (default in the following example).
The content viewer, on the right side of the dialog box, displays the contents of the folder or subfolder selected in the navigation tree. Both files and subfolders are displayed. Clicking a folder or subfolder displays the item's contents.
Clicking the check box to the left of a folder's, subfolder's, or file's name selects the item, allowing you to manipulate it via the toolbar. In the following example, the second listed file is selected.
Right-clicking a folder, subfolder, or file allows you to access options for the item without first clicking the item's corresponding check box. In the following example, the second listed file has been right-clicked.
You can also view the path to the current location in your directory structure, which appears near the top of the content viewer (highlighted below).
The Browse dialog box is accessed by clicking the browse button.
In order to use the Browse dialog box with your form (in other words, for the browse button to appear on the EOS Client Onboarding toolbar, allowing access to the browse feature), it needs to have been submitted. Before being submitted, they are only available via the Form Selection drop-down list on the EOS Client Onboarding toolbar.
The browse button appears on the main EOS Client Onboarding toolbar.
When the browse button is clicked, the Browse dialog box appears (shown below), displaying the current directory structure and your saved files. The dialog box itself takes its title from the title of your repository.
For more information on the layout of this dialog box, see About the Browse Dialog Box Layout.
You can move files or folders within the directory structure by clicking a file, and then dragging your mouse pointer over the desired, new location.
In the example below, the BackgroundForms document is being moved to the current forms subfolder. Notice the green check mark icon, which shows you that the move will be allowed when you release your mouse button.
You can also drag files to folders or subfolders listed in the navigation tree (on the left side of the dialog box), as shown below.
The selection process is slightly different depending on whether you are selecting an individual file or a folder/subfolder.
Proceed to one of the following sections below for more information:
You select individual files by navigating to the file's location, and clicking it in the content viewer on the right side of the Browse dialog box.
Note: If a file is grayed-out, and no check box is available, you do not have permission to manipulate the file.
Note: You can also right-click a file to both select it and access the menu of available options (which corresponds to the buttons that appear on the Browse dialog box's toolbar). Notice that the selected file's name appears at the top of the right-click menu, allowing you to verify that the correct file is selected.
Folders and subfolders (including the Trash folder) can be selected using both the navigation tree on the left side of the Browse dialog box and the content viewer on the right side of the dialog box.
Note: Clicking a folder or subfolder in the content viewer (on the right side of the dialog box) does not select it. Instead, it automatically opens it, showing you the item's contents. To select a folder or subfolder, you must use the item's corresponding check box.
You can select multiple files, folders, or subfolders using the check boxes displayed in the content viewer on the right side of the dialog box.
The following options are available for multiple item selection:
You can click the refresh button at any time to confirm that the displayed contents are the most up-to-date (current) contents.
This option is useful if you have just added a file or a folder/subfolder, or if another user had just added a file or folder/subfolder, and you are not seeing the expected items in your directory structure.
You can also access the feature using any of the following methods:
You can add a new folder or subfolder to your directory structure using the new folder button.
Important: If this button is not available from the toolbar, you may not have permission to edit your directory structure.
Proceed to one of the following sections below:
You can add a top-level folder by selecting the repository name and clicking the new folder button.
You can add a subfolder by selecting the folder in which the new subfolder will reside, and then clicking the new folder button.
You can also use the right-click menu to add folders and subfolders to your directory structure.
You can add files from your local computer to your EOS directory structure using the upload button.
Note: You can also right-click a particular folder or subfolder (on either side of the dialog box) and select upload from the menu that appears.
Important: If this button is not available from the toolbar, you may not have permission to add files to your directory structure.
The File Upload dialog box appears.Note: If you selected the wrong file, click the Cancel option immediately to the left of the currently selected file's name. The selected file is removed, and you can re-browse to a new file.
You can change the name of a file or folder using the rename button.
Note: You can also right-click the item (folder and subfolders on either side of the dialog box), and select rename from the menu that appears.
The Enter new name for dialog box appears, showing the current name of the file or folder.Important: Take care when changing a file name. Although you can alter the file's extension (.pdf, .docx, etc.) using the rename option, the file may no longer open properly. It is recommended that you change only the file's actual name.
You can directly access a document in the Data Entry View and add or change information to the document using the edit button. This button is only available for documents, and will not appear on the toolbar if you select a non-document file (such as an image file).
Important: If you want to retain the current document and its defined information by editing a copy of the document and providing new information, you should use the edit copy option as described in Editing a Copy of a Document.
Note: You can also right-click the document, and select edit from the menu that appears. The selected document's name appears at the top of the right-click menu.
Important: If this button is not available from the toolbar, you have not selected a document or you do not have permission to edit the document.
The document appears in the Data Entry View, showing you the document's currently defined information.
You can directly access a document in the Data Entry View and automatically add or change information to a copy of the document using the edit copy button. This button is only available for documents, and will not appear on the toolbar if you select a non-document file (such as an image file).
This option differs from the edit option in that any information added to or changed in the document is saved in a new copy of the document when you submit the changes. The original document is not updated.
Important: If you want to edit the actual, selected version of the document, and not create a new copy to edit, use the edit option as described in Editing a Document.
After you submit the document, a copy of the document appears in your folder structure, as described in the following procedure:
Note: You can also right-click the document, and select edit copy from the menu that appears. The selected document's name appears at the top of the right-click menu.
Important: If this button is not available from the toolbar, you have not selected a document or you do not have permission to edit the document.
The document appears in the Data Entry View, showing you the document's currently defined information.
You can copy a file from EOS to your local system using the download button.
Note: You can also right-click the file, and select download from the menu that appears. The selected file's name appears at the top of the right-click menu.
Important: If this button is not available from the toolbar, you may not have permission to access the file.
The file is saved to your local system. The exact process for saving the file differs based on your current web browser.
If a file is a document, you can access the final, completed document in the Document Viewer using the view button.
Note: You can also right-click the document, and select view from the menu that appears. The selected document's name appears at the top of the right-click menu.
Important: If this button is not available from the toolbar, you may not have permission to access the document.
The final version of the document is loaded in the Document Viewer.Tip: If you notice that the document information needs to be edited, you can quickly edit it using the edit button as described in Editing a Document.
If a document has signature fields, you can access them using the sign button.
Note: You can also right-click the document, and select sign from the menu that appears.
Important: If this button is not available from the toolbar, you may not have permission to access the document.
You can delete a file or folder from your EOS Client Onboarding directory structure using the remove button.
When removed, the item is placed in the Trash folder until it is permanently removed. When necessary, files in the Trash folder can be moved back to a non-deleted regular folder.
Important: If this button (or option) is not available from the toolbar, you may not have permission to access the file.
You can easily access the links (hyperlinks) related to a document via the link button.
These links allow you to edit the original document, edit a copy of the document, view the document, or sign the document using the OpenForm Viewer (a version of the Data Entry View that appears in a web browser).
You can your form using the Run button on the EOS Client Onboarding toolbar.
Clicking this button opens your form in the Data Entry View, which allows you to enter information. This information is then transferred to the final document when you click the Submit button (at the bottom of the Data Entry View dialog box).
The Document Viewer, which appears after you complete a form in the Data Entry view and click Submit, allows you to perform the following actions:
One way to access previously saved documents is using the Browse dialog box.
You can copy a completed document to your local system using the download button.
Note: The exact process for downloading the document differs based on your current web browser.
You can email a copy of the completed document using the email button.
When this button is clicked, the Compose New Email dialog box appears.
To send an email:
If signature fields are present in your document, you are immediately alerted when the Document Viewer first opens.
You can then sign the document using the sign button, as specified in the message above.
This button opens the Signature screen, which allows you to sign the document.
Once you sign the document, you can view the corresponding signature information using the signInfo button.
When you click this button, the Signature Info dialog box appears, displaying complete details about all of the document's signatures. For more information, see Viewing Signature Details (Signature Log).
Download the file, and then print it using the image viewer of your choice.
Batch signing allows you to sign multiple documents, with a single signature, via the Browse dialog box. Once the documents are selected, you can pick and choose the fields that you want to sign.
The batch signing feature is used by accessing the desired documents via the Browse dialog box.
Tip: If you are not satisfied with the signature, click clear to recreate it.
The signature is applied to the selected fields in the selected documents, and each document is opened in its own Document Viewer window, allowing you to see the applied signatures. In addition, the Signed documents dialog box appears, allowing you to review the signature actions that just occurred.You can also access batch signing using the EOS Search feature. When multiple documents are selected, the batch sign button becomes active.
Clicking the batch sign button opens the Who is signing? screen.
The Signature Info dialog box displays the document's signature details, including the name of the signer, the date of the signature, the signer's system information, an image of the signature, and related stamp details.
Proceed to one of the sections below for more information:
The Signature Info dialog box displays information for both signatures and stamps. In order to better understand the displayed information, you need to understand the meaning of both of these terms:
Important: The term stamp can also be used to describe the default, user stamp that can be assigned via the Preferences dialog box.
When a user signs a document, the signature may be applied to multiple fields across multiple documents. Therefore, it can be said that a single signature may be stamped multiple times on multiple documents, and each "signature" object can have one or more "stamp" objects associated with it.
The hash codes associated with signatures are digital fingerprints of the document after the signature was applied. They act as a security feature, and can be used to determine if the document has been tampered with or altered. For example, if someone emailed you a PDF, and you know the hash algorithm that has been used, you could compute the PDF's fingerprint. This fingerprint could then be compared to the fingerprint of the signature stamp. If the fingerprints are not identical, the PDFs are not the same, even if they appear identical.
For more information, refer to the following website:
http://en.wikipedia.org/wiki/Cryptographic_hash_function
In general, the information displayed in the Signature Info dialog box is for viewing purposes only. The displayed information cannot be altered or edited in any way.
Note: If more than one signature exists in a document, all signatures are shown. The example at the beginning of this topic shows only a single signature.
This dialog box allows you to view the following information:
In the following example, two individuals (Mrs. Johnson and Mr. Bauer) needed to sign a medical insurance form at the doctor's office. After they both signed, the resulting details (one signature details section with two individual stamps) are displayed on the Signature Info dialog box.
The Signature Info dialog box can be accessed from any of the following locations:
EOS Client Onboarding Mobile allows you to emulate your existing EOS Client Onboarding system on an Apple iPad, allowing for easy portability and in-the-field information collection.
The terminology listed below is used throughout this chapter of the help, and it needs to be understood before effectively using the mobile topics.
Note: Some of these terms are mobile-specific, but some also apply to the standard EOS Client Onboarding application.
When you first start the EOS Client Onboarding mobile app, you will be asked to enter login credentials which are the same as those used when accessing the standard EOS Client Onboarding application.
The main app screen (also know as the "initial screen") is the default screen that appears when the app is first accessed, after your login information is provided and verified. This screen also provides access to all features available in the mobile app.
This screen is divided into the following two areas:
The following information is available, based on the selected (tapped) option:
When you tap the All Forms option, the forms currently available on your iPad are displayed on the right side of the app.
When you select (tap) an individual form, the form's options and information appear.
The following features are displayed on the right side of the app:
Once you access a form, you can run it (access it in the mobile version of the Data Entry View), which allows you to populate the form's fields and create a new document.
Note: If the document is incomplete (if all required fields have not been populated), a message appears verifying that you want to exit and create a document.
The newly created document appears, and additional options are displayed at the bottom of the app.Note: Forms created using Microsoft Word source documents cannot be displayed at this point in the process. However, the additional options, mentioned above, are still available.
If your form contains upload buttons (as shown below), you can add newly taken pictures (taken with your iPad's camera), existing (previously taken) pictures, or imported files to your form.
Once this button is clicked, additional options appear.
Both the icons (in the middle of the app) and the option (on the bottom toolbar) can be tapped to add photos or files.
After you select a photo or file, tap Attach to add it to your form.
Tip: If you attached the wrong photo or file, or want to replace the existing selection, simply tap the field again and select a different photo or file. The newly selected item overwrites the previously selected one.
You can specify individual forms as "favorites", which allows you to easily access them, especially if your main list of forms (the All Forms option) is lengthy.
Proceed to one of the following sections below for more information:
Forms that have been added to your favorites list can be easily accessed by tapping the Favorite Forms option on the left side of the app. The forms that have been designated as favorites are listed on the right side of the app.
The process for accessing these forms, and the corresponding form options that appear, is identical to the one used when using the All Forms option. The difference is that you have the ability to control the content of the Favorite Forms list, as described below.
You can add a form to your list of favorite forms using the Favorite option.
You can use templates to populate forms more accurately and rapidly while using EOS Client Onboarding Mobile. Templates allow you to pre-fill specific form fields if you know that the field value will not change.
When filling out a form, you can then choose between a completely blank form or a template version of the form, which contains the pre-filled fields.
Note: Templates exist only in your local app and cannot be shared between iPads or uploaded to the EOS server.
Proceed to one of the following sections below for more information:
You can create a template from a specific form using the gear icon at the bottom of the form itself.
Once a template has been created, it can be accessed via the corresponding form's main options screen.
Once created, templates can be used in the same way as standard forms using the template's Run option.
You can adjust an existing template, altering the pre-defined fields, using the Update Template option.
You can rename a template after it is created and given an initial name.
You can remove an existing template from your app.
When you are ready to sign a form, you can either sign it immediately after you fill in the form, or you can access it at a later time and then sign it (as a document).
Proceed to one of the following sections below for more information:
You can sign a form as soon as it is completed, and all of the required fields are filled in.
Note: The Who is signing? screen example shown above only displays a single signature field. If you are using bulk signing, additional signature fields would be listed.
The large signature box appears.Verify that the signature has been accepted.
You are returned to the form's preview, and, for PDF-based forms, the signature is displayed. In the following example, all signature fields were signed with the same signature (via the Sign All option).
You can sign a document that was completed at an earlier time but was never signed. This sign option is accessed via the document's individual options.
Important: If you do not see this option, you should verify with Technical Support that your clientID has batch signing enabled (via the batchSign option).
When multiple documents have been completed, you can sign all of them using a single signature. This feature is known as "batch signing".
Proceed to one of the following sections below for more information:
Batch signing, described in this topic, allows you to sign multiple documents using a single signature.
A similar feature, bulk signing, allows you to sign multiple signature fields in a single document using a single signature. For more information on using this feature, as part of the process of signing a single document, see Signing an Individual Form/Document.
You can view a list of all documents that are incomplete, have been completed but not signed, have been signed, or have been downloaded from your EOS server using the All Documents option.
Once you tap this option, the completed documents are displayed on the right side of the app.
Tip: You can search for documents, if your document list is lengthy, using the Search Documents text box at the top of the right side of the app.
You can tap any listed form to access its individual options.
The following options are available from completed, signed, and downloaded documents:
The ability to select multiple documents can be useful, especially in the following situations:
Selecting multiple documents is similar to the standard Apple (iOS) control for selecting multiple items in other apps.
You can access a preview of your PDF-based documents using the View option. You can also use this option to access a completed document that needs to be signed.
You can access a previously created document and alter its contents using the Edit option.
Important: Signed documents typically cannot be edited and most of the document's fields were probably locked when the signature was applied.
You can complete partially filled-in documents using the Edit option.
You can update previously completed, un-signed documents or downloaded forms using the Edit option.
You can update the form definitions and related information on your iPad, pulling down updates from the EOS server, using the Update Forms option.
The following information is updated when this feature is used:
Using this feature allows you to verify that you have access to the most up-to-date versions of forms and related information that is shared among numerous iPads and the standard EOS Client Onboarding application.
Completed documents must be saved back to the EOS server at some point, and at that time the locally completed documents are removed from the iPad. This process is known as "synchronization".
You can view the documents that need to be synchronized using either of the following options on the left side of the app:
If you simply want to synchronize all available documents, without first reviewing the list of documents that will be uploaded to your EOS server, use the Sync Documents option.
Note: If you want to review the list of documents that will be synced, before uploading them to your EOS server, proceed to the next section below.
You can update all completed, signed, and downloaded documents, and send these updated versions from your iPad to the EOS server, using the Synchronize All option. When using this option, a list of the documents that will be synced is displayed.
Important: This option automatically synchronizes all available documents in the overall list of documents.
You can synchronize a single document by accessing the document's options and using the Synchronize option.
You can specify a subset of the documents in your app for synchronization. This feature allows you to synchronize more than one document without having to synchronize all documents.
You can search for previously created documents on your EOS server. When found, these documents can be downloaded to your mobile device and manipulated using the EOS Client Onboarding mobile app.
Proceed to one of the following sections below for more information:
Each form automatically includes a default search feature, which allows you to search for documents created by the user currently authenticated to the app and during a specified time frame.
You can access this search as described below.
The search feature is accessed at the form level. Each form can have different searches defined for it.
Note: Any parameters added using this method are only available while the Search screen is open. Once you exit the search, only the search's parameters, as defined on your EOS server, are saved.
Note: If a document has already been downloaded to your mobile device, the word "Downloaded" appears in place of the document's date/time stamp.
Once located via a search, a document can be downloaded and manipulated with your mobile app.
You can select more than one document from your search results and download them simultaneously.
You can view a copy of the completed document, as it appears on the server, without downloading it to your iPad using the View Server Copy option.
You can remove documents from your iPad app. The deleted documents are still available from your EOS server.
Proceed to one of the following sections below for more information:
You can delete a particular incomplete, completed, signed, or downloaded document from your mobile device.
You can delete multiple incomplete, completed, signed, or downloaded documents from your mobile device.
You can easily delete all of the incomplete, completed, signed, or downloaded documents from your mobile device.
When synchronizing documents between your iPad and your EOS server, a check is performed, to verify that the versions match. This step prevents multiple users from editing and updating the same document and overriding each other's changes.
Note: This verification process is sometimes referred to as optimistic locking.
Proceed to one of the following topics for more information:
This feature guarantees that the version on the EOS server is always up-to-date, and that changes uploaded from an iPad cannot overwrite changes made (at the same time) to the same document either from other mobile devices or via the standard (web-based) EOS application.
However, this feature does not prevent changes from being made on a server while working with a document on a mobile device. When you download a document to your iPad, you take the risk of changes being made to the same document on the EOS server by another user. If this other version of the document is uploaded to the EOS server before your personal version, you will not be able to upload your version. In other words, the server version of the document is not locked after you download it, so other users can make changes to and upload the same document, which will render your changes non-syncable.
Important: The main purpose of the optimistic locking feature is to prevent your EOS server from containing conflicting data. It is a server-side feature, not a mobile app-side feature.
If a downloaded document has been updated on your EOS server, a message will appear adjacent to the document when viewed via the All Documents list, as shown below.
Documents displaying this message can no longer by synced. Instead, you should download the updated version from the EOS server, and then make updates using your mobile device. For more information, see Resolving Synchronization Errors below.
The following example shows the error message that will appear if the version of the document on the EOS server is newer than the version being synchronized from your iPad.
After you tap OK to close the error message, the form's information is displayed, and a Conflicts with Server message appears in the Sync Status field.
This message also appears if the document appears in a document list.
If you access a downloaded document that has been updated on your EOS server, different options appear than with a standard document.
The following options allow you to either view the different versions of the document or resolve the synchronization error:
For more information on the last two options listed above, proceed to the next section below.
If a sync error occurs, as described above, you can perform one of the following actions to resolve the issue. Remember, resolving the issue means that your local copy of the document, and all changes that you have made, will be lost and replaced with the updated copy from your EOS server.
Proceed to one of the following sections below for more details:
You can replace the local version of the document with the version on your EOS server. Once replaced, the new version can again be edited, if desired.
If desired, you can simply delete the local copy, and then download the document again at a later time.
You can import .PDF and Microsoft Word files (both .docx and .doc file types) into the EOS Client Onboarding Mobile app from other iPad apps (for example: your email app, the Safari web browser, a file sharing app, etc.).
The exact process for importing a file varies based on the app from which the file is coming.
Once imported, a message appears in the EOS Client Onboarding app.
These files can then be used with a form's upload field via the Files options.
Important: Imported files are only available from the app for a specified period of time, after which they are automatically deleted from the app. This time period is set using the Delete imported files server-side option.
The Options feature gives you access to user and app information, as well as basic app settings.
Proceed to one of the sections below for more information:
The basic app information is accessed by tapping Options on the left side of the mobile application.
You can view complete user information, including offline settings set on the EOS server, by tapping the the More option in the User Info area.
Additional options appear for you app. You'll need to swipe up to see some of the available options.
The following additional options are available, which allow you to control the appearance of your app:
You can exit the app simply by clicking your iPad's Home button.
However, it is recommended that you log out of the app first.
LincWare is dedicated to providing its customers with the most efficient and affordable pathway to benefiting from its products. Each EOS Client Onboarding solution is designed around ease of use, exceptional cost-to-benefit value and rock-solid architecture.
Backing those product principles is a knowledgeable, 24/7 web-based technical support structure dedicated to solving any issue that arises in as little time as possible. In fact, one call is typically all it takes.
You can contact EOS Technical Support using any of the following methods:
If at any time your problem is not solved to your satisfaction, the chain of command is readily available to address it until you are completely satisfied.
You access your EOS Client Onboarding system by accessing a URL that is specific to your environment. When this URL is accessed, your EOS Client Onboarding system's login screen appears, allowing you to specify a username and password.
Note: Your URL is created and assigned to you during the initial EOS Client Onboarding system configuration phase. If you do not know your URL, contract Technical Support.
The login screen is your initial point of entry. It allows you to specify the following information:
You can access and edit some of your profile settings, if desired, using the profile button on the EOS Client Onboarding system's toolbar.
The EOS Client Onboarding toolbar displays several components. When used together, they enable access to simple management and administration features.
This drop-down list, the primary option in the interface, allows you to determine which form will be manipulated by other toolbar buttons. The list itself contains the unique identifier and full description of each form that you can access.
Note: EOS Client Onboarding customers will usually have only one form.
When the form is selected, you can run the form. You can also search for documents generated from the form.
Once the form has been selected using the Form Selection drop-down list, clicking run opens the item in the Document Viewer, and allows you to begin entering data.
The search option allows you to locate and retrieve previously saved forms.
After selecting your form, selecting search will list all relevant content to which the specific user has access. You may select from previously saved search parameters or create new criteria.
The browse option opens the Browse dialog box, which allows you to view and manipulate folders and files in your directory structure.
The interface is also defined by individual user profile parameters, which can be set using the profile button. This user information is established according to the user's role within the organization's EOS Client Onboarding community.
For more information, see Customizing Your User Profile.
The help option provides a method for accessing EOS online help/documentation, opening a support ticket with the development staff, or viewing your license agreement. The current EOS Client Onboarding system (LincDoc) version information can also be found here.
The windows button provides you with access to the list of currently opened windows (if any), and allows you to optionally tile the open windows on the workspace.
Hidden window are shown in italics, and can be re-displayed by selecting them.
Closes the current EOS Client Onboarding session.
Several different views are used through the form creation process. It is recommended that you become familiar with these views before using the EOS Client Onboarding system.
Proceed to one of the following topics below for more information:
This view is used to actually input information into the completed form.
This view is accessed by clicking the run button on the EOS Client Onboarding toolbar.
Once the form's data is added using the Data Entry View, the form is submitted via the Submit button at the bottom of the Data Entry View, and the final form appears in the Document Viewer.
For more information, see Running a Form.
This view is essentially the same as the Data Entry View, except that it runs in a dedicated web browser window or tab, instead of in the EOS Client Onboarding interface.
The Document Viewer is used to display the "final" form, after the form has been created and submitted via the Data Entry View.
This view also allows you to download, email, and sign the form (if applicable). For more information on this view, see Using the Document Viewer.
This special view is launched from the Document Viewer.
For more information, see Signing the Completed Form.
This is a list of the most common terms used throughout this documentation:
Term |
Definition |
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. |
authentication provider |
See provider. |
batch signing |
A feature that allows you to sign multiple documents with a single signature. |
bulk signing |
A feature that allows you to sign multiple signature fields, in a single document, with a single signature. |
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 EOS that stores all field definitions, source documents, generated documents and data. These cannot be created at the user level, but instead are directly tied to your license key - as created when you acquired EOS. In most cases, you will only have access to a single client ID, although multiple client IDs can be purchased, if needed. |
codelist (code list) |
Codelists are objects within EOS that drive drop down choice lists. For example, 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 |
Logic used to conditionally display or hide a field or section. Sometimes abbreviated as "c2d". |
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 |
Short for Comma Separated Values, which is 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 |
Short for Data And Number Generator, which is a key component of the EOS administrator interfaced 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 |
A file created using an eForm of Document Package. Basically the "filled-in" version of an eForm or Document Package. Also known as a generated document. |
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. |
document repository |
A searchable storage area where documents and data are saved. EOS has its own internal document repository, and third party repositories such as Laserfiche are also supported. |
document viewer |
The window in which the generated document is displayed. |
DRAT |
Short for Document Refinement Annotation Transformer, which is an extension of the EOS markup language for more sophisticated field resolution scenarios. |
drop-down list (DDL) |
An eForm 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. It is also comprised of field details, sections, conditions, actions, events, and lookups. |
end user |
Any person who uses EOS to complete a preconfigured eForm or Document Package. |
event |
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 EOS 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. |
generated document |
See document. |
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 |
Short for Java Database Connectivity. |
LDAP signature |
A type of signature in EOS 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 |
Short for EOS Archive. An eForm definition can be exported as an .ldar file, and imported to another EOS VM. |
EOS administrator |
The person responsible for creating eForms and corresponding field elements, conditions, lookups, actions, etc. within the EOS system for the end user community. |
EOS 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 |
Short for 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. |
multitenancy |
A type of software architecture where a single instance (installation) of the software runs on a server, but is designed to virtually partition (divide) its data and configuration. In this arrangement, each client organization (known as client IDs in EOS) uses a customized, virtual application. In the EOS environment, multitenancy is used to separate sets of forms and data. |
multi-value field |
A repeatable field that takes on multiple values. These are sometimes called "multi-row fields" or "pound fields" (because in the EOS markup language they are always terminated by a pound sign (#)). These field types are only available in Word source documents. Example:
|
node |
A specific item within a repository, accessed via the Browse dialog box. Nodes can be documents, files, or folders. |
OpenForm |
The term used to describe when an eForm is launched in a separate browser window (or iframe), and none of the normal EOS desktop controls are present (for example, no top toolbar with buttons for search, run, help, logout, etc.). This method 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. |
parse/reparse |
The process of resolving/finding fields in a document. A reparse operation typically takes place whenever a source document is altered. |
|
Acronym for "portable document format". |
pound field |
Another name for a multivalue field. |
provider |
Also known as authentication provider. Acts as a container for a specific set of users and groups. They can be created to control application access. They are created at the client ID level, making them available to other users with access to your current client ID. |
required condition |
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. |
signature |
Both a person's name, used to formalize a document, as well as a general term for the information that applies to all form fields to which a signature itself is applied. |
signature receipt |
A signature feature that displays the actual signature used on a form, information about the signature (such as the name of the user who signed and the date/time), and provides buttons for downloading the corresponding signed form or just the receipt information to a file. |
signature stamp |
An image that can be used in place of a script font representation of a signature, and is a digital representation of your actual signature. |
source document |
A Microsoft Word or PDF document containing zero or more fields. In the case of Word, the EOS 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 EOS. |
SQL repository |
A back end storage system that is based on a relational database. Currently, this database must be either PostgreSQL or Microsoft SQL Server. Note: This feature is available with EOS version 3.3 and later releases. |
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. |
stamp |
An electronic record, used with signatures, that captures details essential to demonstrate the authenticity of the signature. |
superuser |
Similar to a Windows Administrator account, this type of user is given access to a large majority of the EOS system and its settings. Typically, a non-cloud installation has only one superuser account called admin. Cloud installations never have a superuser account for security reasons. |
synchronization/sync/on sync |
An event indicating that a mobile device (for example, an iPad) is pushing locally saved forms/data to a EOS server. |
TIFF |
Short for "tagged image file format". |
token based name |
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 |
Short for "user interface" or the portion of the application with which users directly interact. |
UUID |
UUID (Universally Unique IDentifier) values can be thought of as random strings such as: 7402b0a6-d4da-489b-9955-8cc3f87735cb. UUID generators are very good at never producing the same string twice. For every document generated in EOS (regardless of the repository type: SQL Repository, Laserfiche, or Docuware), a UUID is assigned that is 36 characters long. The DANG function DocID can be used to return this value. The value is actually internally generated the moment you start a brand new form (and never changes for that form thereafter). This value is critical to doing any kind of workflow with a document, and is used to create URLs that allow direct access to manipulate a particular form (editing, viewing, signing, etc.). For more information on UUIDs, click here. |
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 EOS's bulk signing feature. |
user |
Short for "end user". |
user profile |
Stores the user's name, email address, time zone, password, and password reset question. |
The EOS Client Onboarding system has the ability to configure and save searches, within your repository, to locate previously generated documents.
This feature provides more flexibility when trying to find documents, and can be helpful when your repository contains a large number of generated documents.
The search feature is executed at the form level and accessed using the search button on the EOS Client Onboarding toolbar.
You can view an existing search's configuration options, as well as create and configure new searches, using the Search dialog box. Once configured, you can use these searches to locate generated documents in your SQL repository.
Proceed to one of the following sections below for more information:
You can select a previously defined search using the search drop-down list in the top left corner of the Search dialog box.
Once selected, access the search configuration options and edit them, as desired.
You can create a new search using the search drop-down list in the top left corner of the Search dialog box.
The new search is saved.
By default, the search configuration options are hidden on the Search dialog box.
You can access them using one of the following methods:
Note: You may need to resize the Search dialog box (click and drag to the right) to see this triangle icon.
The configuration options are displayed on several tabs immediately below the thin line/triangle icon (and above the search results table).
Proceed to Specifying the Configuration Options below.
Once you access a search's configuration options, you can adjust the options, as desired, to verify that the search locates the correct generated documents in your repository. These configuration options are displayed in several tabs on the Search dialog box.
Proceed to one of the following sections below for more information on each individual tab:
The options tab allows you to specify a description for the search, which can be helpful for allowing other users to easily understand how to use the search.
This description will appear immediately below the search's name in the search drop-down list.
The filter tab allows you to specify exactly what is searched for when the search is executed.
Using at least one condition, determine what the search will attempt to locate in your repository.
In the following example, all documents whose med_plan field contains the text gold will be returned by the search.
Tip: Use the + and - buttons to add or remove conditions, as necessary to define your search filters.
The columns tab allows you to control the information that appears in the search results table (in the lower half of the Search dialog box). This table displays the documents that match your search criteria, after a search is executed.
The columns tab is divided into the following three lists:
The queue tab allows to you specify if the configured search will be automatically executed when certain users log into EOS.
To use this option, you need to activate it by selecting the corresponding check box (it is not active by default) and then specify a user type that will use the option.
In the following example, the option has been activated and the search will automatically be performed for all users assigned the user-admin role.
When a user with this role next logs into EOS, a Queue dialog box similar to the following example will appear, showing the automatically executed search results.
Tip: You can click the button adjacent to the wrench button (highlighted below) to change from the Queue dialog box to the standard Search dialog box.
In addition, if this option is enabled for multiple searches, tabs appear at the top of the Queue dialog box. One tab appears for each search that uses the option. In the following example, two searches appear.
Once you have completely configured your search, you need to save your changes.
You can delete any search if it is no longer useful or necessary.
Once a search is configured, you can execute it, and view the results (the generated documents in your SQL repository returned by the search).
Proceed to one of the sections below for details:
A search is performed (executed) on a form-by-form basis using the Search dialog box.
Once a search is complete, the results are displayed in the search results table in the bottom half of the Search dialog box. You are also provided with additional options that can be used with the returned list of documents.
Tip: This customization only impacts the current search. If you want to permanently edit the information displayed in the search results table for the current search, see Specifying Search Column Settings.
Note: The column order is search-specific, so you can specify different column orders for different saved searches.
Tip: You can select individual documents (using their corresponding check boxes), as shown below, or you can click the check box in the column's heading to select all listed documents.
In the following example, two documents have been selected.
You can use EOS's internal file browser to store and access documents and related files (source documents, branding images, etc.) in a customizable directory structure. The files are actually stored in and accessed from your SQL repository.
You can also perform other actions using this feature including, but not limited to:
The Browse dialog box is comprised of three main components, which are shown in the diagram below.
The toolbar, at the top of the dialog box, contains the buttons which allow you to perform specific actions within this dialog box. The contents of the toolbar are dynamic, based on the type of item selected in the lower portion of the dialog box, as well as the permissions you have been granted on the selected item.
The navigation tree, on the left side of the dialog box, is used for selecting individual folders or subfolders. You can click the button immediately above the navigation tree to return to the top level directory. This button is labeled with the name of your repository (default in the following example).
The content viewer, on the right side of the dialog box, displays the contents of the folder or subfolder selected in the navigation tree. Both files and subfolders are displayed. Clicking a folder or subfolder displays the item's contents.
Clicking the check box to the left of a folder's, subfolder's, or file's name selects the item, allowing you to manipulate it via the toolbar. In the following example, the second listed file is selected.
Right-clicking a folder, subfolder, or file allows you to access options for the item without first clicking the item's corresponding check box. In the following example, the second listed file has been right-clicked.
You can also view the path to the current location in your directory structure, which appears near the top of the content viewer (highlighted below).
The Browse dialog box is accessed by clicking the browse button.
In order to use the Browse dialog box with your form (in other words, for the browse button to appear on the EOS Client Onboarding toolbar, allowing access to the browse feature), it needs to have been submitted. Before being submitted, they are only available via the Form Selection drop-down list on the EOS Client Onboarding toolbar.
The browse button appears on the main EOS Client Onboarding toolbar.
When the browse button is clicked, the Browse dialog box appears (shown below), displaying the current directory structure and your saved files. The dialog box itself takes its title from the title of your repository.
For more information on the layout of this dialog box, see About the Browse Dialog Box Layout.
You can move files or folders within the directory structure by clicking a file, and then dragging your mouse pointer over the desired, new location.
In the example below, the BackgroundForms document is being moved to the current forms subfolder. Notice the green check mark icon, which shows you that the move will be allowed when you release your mouse button.
You can also drag files to folders or subfolders listed in the navigation tree (on the left side of the dialog box), as shown below.
The selection process is slightly different depending on whether you are selecting an individual file or a folder/subfolder.
Proceed to one of the following sections below for more information:
You select individual files by navigating to the file's location, and clicking it in the content viewer on the right side of the Browse dialog box.
Note: If a file is grayed-out, and no check box is available, you do not have permission to manipulate the file.
Note: You can also right-click a file to both select it and access the menu of available options (which corresponds to the buttons that appear on the Browse dialog box's toolbar). Notice that the selected file's name appears at the top of the right-click menu, allowing you to verify that the correct file is selected.
Folders and subfolders (including the Trash folder) can be selected using both the navigation tree on the left side of the Browse dialog box and the content viewer on the right side of the dialog box.
Note: Clicking a folder or subfolder in the content viewer (on the right side of the dialog box) does not select it. Instead, it automatically opens it, showing you the item's contents. To select a folder or subfolder, you must use the item's corresponding check box.
You can select multiple files, folders, or subfolders using the check boxes displayed in the content viewer on the right side of the dialog box.
The following options are available for multiple item selection:
You can click the refresh button at any time to confirm that the displayed contents are the most up-to-date (current) contents.
This option is useful if you have just added a file or a folder/subfolder, or if another user had just added a file or folder/subfolder, and you are not seeing the expected items in your directory structure.
You can also access the feature using any of the following methods:
You can add a new folder or subfolder to your directory structure using the new folder button.
Important: If this button is not available from the toolbar, you may not have permission to edit your directory structure.
Proceed to one of the following sections below:
You can add a top-level folder by selecting the repository name and clicking the new folder button.
You can add a subfolder by selecting the folder in which the new subfolder will reside, and then clicking the new folder button.
You can also use the right-click menu to add folders and subfolders to your directory structure.
You can add files from your local computer to your EOS directory structure using the upload button.
Note: You can also right-click a particular folder or subfolder (on either side of the dialog box) and select upload from the menu that appears.
Important: If this button is not available from the toolbar, you may not have permission to add files to your directory structure.
The File Upload dialog box appears.Note: If you selected the wrong file, click the Cancel option immediately to the left of the currently selected file's name. The selected file is removed, and you can re-browse to a new file.
You can change the name of a file or folder using the rename button.
Note: You can also right-click the item (folder and subfolders on either side of the dialog box), and select rename from the menu that appears.
The Enter new name for dialog box appears, showing the current name of the file or folder.Important: Take care when changing a file name. Although you can alter the file's extension (.pdf, .docx, etc.) using the rename option, the file may no longer open properly. It is recommended that you change only the file's actual name.
You can directly access a document in the Data Entry View and add or change information to the document using the edit button. This button is only available for documents, and will not appear on the toolbar if you select a non-document file (such as an image file).
Important: If you want to retain the current document and its defined information by editing a copy of the document and providing new information, you should use the edit copy option as described in Editing a Copy of a Document.
Note: You can also right-click the document, and select edit from the menu that appears. The selected document's name appears at the top of the right-click menu.
Important: If this button is not available from the toolbar, you have not selected a document or you do not have permission to edit the document.
The document appears in the Data Entry View, showing you the document's currently defined information.
You can directly access a document in the Data Entry View and automatically add or change information to a copy of the document using the edit copy button. This button is only available for documents, and will not appear on the toolbar if you select a non-document file (such as an image file).
This option differs from the edit option in that any information added to or changed in the document is saved in a new copy of the document when you submit the changes. The original document is not updated.
Important: If you want to edit the actual, selected version of the document, and not create a new copy to edit, use the edit option as described in Editing a Document.
After you submit the document, a copy of the document appears in your folder structure, as described in the following procedure:
Note: You can also right-click the document, and select edit copy from the menu that appears. The selected document's name appears at the top of the right-click menu.
Important: If this button is not available from the toolbar, you have not selected a document or you do not have permission to edit the document.
The document appears in the Data Entry View, showing you the document's currently defined information.
You can copy a file from EOS to your local system using the download button.
Note: You can also right-click the file, and select download from the menu that appears. The selected file's name appears at the top of the right-click menu.
Important: If this button is not available from the toolbar, you may not have permission to access the file.
The file is saved to your local system. The exact process for saving the file differs based on your current web browser.
If a file is a document, you can access the final, completed document in the Document Viewer using the view button.
Note: You can also right-click the document, and select view from the menu that appears. The selected document's name appears at the top of the right-click menu.
Important: If this button is not available from the toolbar, you may not have permission to access the document.
The final version of the document is loaded in the Document Viewer.Tip: If you notice that the document information needs to be edited, you can quickly edit it using the edit button as described in Editing a Document.
If a document has signature fields, you can access them using the sign button.
Note: You can also right-click the document, and select sign from the menu that appears.
Important: If this button is not available from the toolbar, you may not have permission to access the document.
For more information on signatures, see Signatures.
You can delete a file or folder from your EOS Client Onboarding directory structure using the remove button.
When removed, the item is placed in the Trash folder until it is permanently removed. When necessary, files in the Trash folder can be moved back to a non-deleted regular folder.
Important: If this button (or option) is not available from the toolbar, you may not have permission to access the file.
You can easily access the links (hyperlinks) related to a document via the link button.
These links allow you to edit the original document, edit a copy of the document, view the document, or sign the document using the OpenForm Viewer (a version of the Data Entry View that appears in a web browser).
You can your form using the Run button on the EOS Client Onboarding toolbar.
Clicking this button opens your form in the Data Entry View, which allows you to enter information. This information is then transferred to the final document when you click the Submit button (at the bottom of the Data Entry View dialog box).
The Document Viewer, which appears after you complete a form in the Data Entry view and click Submit, allows you to perform the following actions:
One way to access previously saved documents is using the Browse dialog box.
You can copy a completed document to your local system using the download button.
Note: The exact process for downloading the document differs based on your current web browser.
You can email a copy of the completed document using the email button.
When this button is clicked, the Compose New Email dialog box appears.
To send an email:
If signature fields are present in your document, you are immediately alerted when the Document Viewer first opens.
You can then sign the document using the sign button, as specified in the message above.
This button opens the Signature screen, which allows you to sign the document.
Once you sign the document, you can view the corresponding signature information using the signInfo button.
When you click this button, the Signature Info dialog box appears, displaying complete details about all of the document's signatures. For more information, see Viewing Signature Details (Signature Log).
Download the file, and then print it using the image viewer of your choice.
Batch signing allows you to sign multiple documents, with a single signature, via the Browse dialog box. Once the documents are selected, you can pick and choose the fields that you want to sign.
The batch signing feature is used by accessing the desired documents via the Browse dialog box.
Tip: If you are not satisfied with the signature, click clear to recreate it.
The signature is applied to the selected fields in the selected documents, and each document is opened in its own Document Viewer window, allowing you to see the applied signatures. In addition, the Signed documents dialog box appears, allowing you to review the signature actions that just occurred.You can also access batch signing using the EOS Search feature. When multiple documents are selected, the batch sign button becomes active.
Clicking the batch sign button opens the Who is signing? screen.
The Signature Info dialog box displays the document's signature details, including the name of the signer, the date of the signature, the signer's system information, an image of the signature, and related stamp details.
Proceed to one of the sections below for more information:
The Signature Info dialog box displays information for both signatures and stamps. In order to better understand the displayed information, you need to understand the meaning of both of these terms:
Important: The term stamp can also be used to describe the default, user stamp that can be assigned via the Preferences dialog box.
When a user signs a document, the signature may be applied to multiple fields across multiple documents. Therefore, it can be said that a single signature may be stamped multiple times on multiple documents, and each "signature" object can have one or more "stamp" objects associated with it.
The hash codes associated with signatures are digital fingerprints of the document after the signature was applied. They act as a security feature, and can be used to determine if the document has been tampered with or altered. For example, if someone emailed you a PDF, and you know the hash algorithm that has been used, you could compute the PDF's fingerprint. This fingerprint could then be compared to the fingerprint of the signature stamp. If the fingerprints are not identical, the PDFs are not the same, even if they appear identical.
For more information, refer to the following website:
http://en.wikipedia.org/wiki/Cryptographic_hash_function
In general, the information displayed in the Signature Info dialog box is for viewing purposes only. The displayed information cannot be altered or edited in any way.
Note: If more than one signature exists in a document, all signatures are shown. The example at the beginning of this topic shows only a single signature.
This dialog box allows you to view the following information:
In the following example, two individuals (Mrs. Johnson and Mr. Bauer) needed to sign a medical insurance form at the doctor's office. After they both signed, the resulting details (one signature details section with two individual stamps) are displayed on the Signature Info dialog box.
The Signature Info dialog box can be accessed from any of the following locations:
EOS Client Onboarding Mobile allows you to emulate your existing EOS Client Onboarding system on an Apple iPad, allowing for easy portability and in-the-field information collection.
The terminology listed below is used throughout this chapter of the help, and it needs to be understood before effectively using the mobile topics.
Note: Some of these terms are mobile-specific, but some also apply to the standard EOS Client Onboarding application.
When you first start the EOS Client Onboarding mobile app, you will be asked to enter login credentials which are the same as those used when accessing the standard EOS Client Onboarding application.
The main app screen (also know as the "initial screen") is the default screen that appears when the app is first accessed, after your login information is provided and verified. This screen also provides access to all features available in the mobile app.
This screen is divided into the following two areas:
The following information is available, based on the selected (tapped) option:
When you tap the All Forms option, the forms currently available on your iPad are displayed on the right side of the app.
When you select (tap) an individual form, the form's options and information appear.
The following features are displayed on the right side of the app:
Once you access a form, you can run it (access it in the mobile version of the Data Entry View), which allows you to populate the form's fields and create a new document.
Note: If the document is incomplete (if all required fields have not been populated), a message appears verifying that you want to exit and create a document.
The newly created document appears, and additional options are displayed at the bottom of the app.Note: Forms created using Microsoft Word source documents cannot be displayed at this point in the process. However, the additional options, mentioned above, are still available.
If your form contains upload buttons (as shown below), you can add newly taken pictures (taken with your iPad's camera), existing (previously taken) pictures, or imported files to your form.
Once this button is clicked, additional options appear.
Both the icons (in the middle of the app) and the option (on the bottom toolbar) can be tapped to add photos or files.
After you select a photo or file, tap Attach to add it to your form.
Tip: If you attached the wrong photo or file, or want to replace the existing selection, simply tap the field again and select a different photo or file. The newly selected item overwrites the previously selected one.
You can specify individual forms as "favorites", which allows you to easily access them, especially if your main list of forms (the All Forms option) is lengthy.
Proceed to one of the following sections below for more information:
Forms that have been added to your favorites list can be easily accessed by tapping the Favorite Forms option on the left side of the app. The forms that have been designated as favorites are listed on the right side of the app.
The process for accessing these forms, and the corresponding form options that appear, is identical to the one used when using the All Forms option. The difference is that you have the ability to control the content of the Favorite Forms list, as described below.
You can add a form to your list of favorite forms using the Favorite option.
You can use templates to populate forms more accurately and rapidly while using EOS Client Onboarding Mobile. Templates allow you to pre-fill specific form fields if you know that the field value will not change.
When filling out a form, you can then choose between a completely blank form or a template version of the form, which contains the pre-filled fields.
Note: Templates exist only in your local app and cannot be shared between iPads or uploaded to the EOS server.
Proceed to one of the following sections below for more information:
You can create a template from a specific form using the gear icon at the bottom of the form itself.
Once a template has been created, it can be accessed via the corresponding form's main options screen.
Once created, templates can be used in the same way as standard forms using the template's Run option.
You can adjust an existing template, altering the pre-defined fields, using the Update Template option.
You can rename a template after it is created and given an initial name.
You can remove an existing template from your app.
When you are ready to sign a form, you can either sign it immediately after you fill in the form, or you can access it at a later time and then sign it (as a document).
Proceed to one of the following sections below for more information:
You can sign a form as soon as it is completed, and all of the required fields are filled in.
Note: The Who is signing? screen example shown above only displays a single signature field. If you are using bulk signing, additional signature fields would be listed.
The large signature box appears.Verify that the signature has been accepted.
You are returned to the form's preview, and, for PDF-based forms, the signature is displayed. In the following example, all signature fields were signed with the same signature (via the Sign All option).
You can sign a document that was completed at an earlier time but was never signed. This sign option is accessed via the document's individual options.
Important: If you do not see this option, you should verify with Technical Support that your clientID has batch signing enabled (via the batchSign option).
When multiple documents have been completed, you can sign all of them using a single signature. This feature is known as "batch signing".
Proceed to one of the following sections below for more information:
Batch signing, described in this topic, allows you to sign multiple documents using a single signature.
A similar feature, bulk signing, allows you to sign multiple signature fields in a single document using a single signature. For more information on using this feature, as part of the process of signing a single document, see Signing an Individual Form/Document.
You can view a list of all documents that are incomplete, have been completed but not signed, have been signed, or have been downloaded from your EOS server using the All Documents option.
Once you tap this option, the completed documents are displayed on the right side of the app.
Tip: You can search for documents, if your document list is lengthy, using the Search Documents text box at the top of the right side of the app.
You can tap any listed form to access its individual options.
The following options are available from completed, signed, and downloaded documents:
The ability to select multiple documents can be useful, especially in the following situations:
Selecting multiple documents is similar to the standard Apple (iOS) control for selecting multiple items in other apps.
You can access a preview of your PDF-based documents using the View option. You can also use this option to access a completed document that needs to be signed.
You can access a previously created document and alter its contents using the Edit option.
Important: Signed documents typically cannot be edited and most of the document's fields were probably locked when the signature was applied.
You can complete partially filled-in documents using the Edit option.
You can update previously completed, un-signed documents or downloaded forms using the Edit option.
You can update the form definitions and related information on your iPad, pulling down updates from the EOS server, using the Update Forms option.
The following information is updated when this feature is used:
Using this feature allows you to verify that you have access to the most up-to-date versions of forms and related information that is shared among numerous iPads and the standard EOS Client Onboarding application.
Completed documents must be saved back to the EOS server at some point, and at that time the locally completed documents are removed from the iPad. This process is known as "synchronization".
You can view the documents that need to be synchronized using either of the following options on the left side of the app:
If you simply want to synchronize all available documents, without first reviewing the list of documents that will be uploaded to your EOS server, use the Sync Documents option.
Note: If you want to review the list of documents that will be synced, before uploading them to your EOS server, proceed to the next section below.
You can update all completed, signed, and downloaded documents, and send these updated versions from your iPad to the EOS server, using the Synchronize All option. When using this option, a list of the documents that will be synced is displayed.
Important: This option automatically synchronizes all available documents in the overall list of documents.
You can synchronize a single document by accessing the document's options and using the Synchronize option.
You can specify a subset of the documents in your app for synchronization. This feature allows you to synchronize more than one document without having to synchronize all documents.
You can search for previously created documents on your EOS server. When found, these documents can be downloaded to your mobile device and manipulated using the EOS Client Onboarding mobile app.
Proceed to one of the following sections below for more information:
Each form automatically includes a default search feature, which allows you to search for documents created by the user currently authenticated to the app and during a specified time frame.
You can access this search as described below.
The search feature is accessed at the form level. Each form can have different searches defined for it.
Note: Any parameters added using this method are only available while the Search screen is open. Once you exit the search, only the search's parameters, as defined on your EOS server, are saved.
Note: If a document has already been downloaded to your mobile device, the word "Downloaded" appears in place of the document's date/time stamp.
Once located via a search, a document can be downloaded and manipulated with your mobile app.
You can select more than one document from your search results and download them simultaneously.
You can view a copy of the completed document, as it appears on the server, without downloading it to your iPad using the View Server Copy option.
You can remove documents from your iPad app. The deleted documents are still available from your EOS server.
Proceed to one of the following sections below for more information:
You can delete a particular incomplete, completed, signed, or downloaded document from your mobile device.
You can delete multiple incomplete, completed, signed, or downloaded documents from your mobile device.
You can easily delete all of the incomplete, completed, signed, or downloaded documents from your mobile device.
You can import .PDF and Microsoft Word files (both .docx and .doc file types) into the EOS Client Onboarding Mobile app from other iPad apps (for example: your email app, the Safari web browser, a file sharing app, etc.).
The exact process for importing a file varies based on the app from which the file is coming.
Once imported, a message appears in the EOS Client Onboarding app.
These files can then be used with a form's upload field via the Files options.
Important: Imported files are only available from the app for a specified period of time, after which they are automatically deleted from the app. This time period is set using the Delete imported files server-side option.
The Options feature gives you access to user and app information, as well as basic app settings.
Proceed to one of the sections below for more information:
The basic app information is accessed by tapping Options on the left side of the mobile application.
You can view complete user information, including offline settings set on the EOS server, by tapping the the More option in the User Info area.
Additional options appear for you app. You'll need to swipe up to see some of the available options.
The following additional options are available, which allow you to control the appearance of your app:
You can exit the app simply by clicking your iPad's Home button.
However, it is recommended that you log out of the app first.
LincWare is dedicated to providing its customers with the most efficient and affordable pathway to benefiting from its products. Each EOS Client Onboarding solution is designed around ease of use, exceptional cost-to-benefit value and rock-solid architecture.
Backing those product principles is a knowledgeable, 24/7 web-based technical support structure dedicated to solving any issue that arises in as little time as possible. In fact, one call is typically all it takes.
You can contact EOS Technical Support using any of the following methods:
If at any time your problem is not solved to your satisfaction, the chain of command is readily available to address it until you are completely satisfied.
You access your EOS Client Onboarding system by accessing a URL that is specific to your environment. When this URL is accessed, your EOS Client Onboarding system's login screen appears, allowing you to specify a username and password.
Note: Your URL is created and assigned to you during the initial EOS Client Onboarding system configuration phase. If you do not know your URL, contract Technical Support.
The login screen is your initial point of entry. It allows you to specify the following information:
You can access and edit some of your profile settings, if desired, using the profile button on the EOS Client Onboarding system's toolbar.
The EOS Client Onboarding toolbar displays several components. When used together, they enable access to simple management and administration features.
The interface is also defined by individual user profile parameters, which can be set using the profile button. This user information is established according to the user's role within the organization's EOS Client Onboarding community.
For more information, see Customizing Your User Profile.
The system button provides a method for maintaining individual and group access to documents and other application-wide security settings.
Clicking this button displays a list of addition options. This list varies based on your user security level.
The help option provides a method for accessing EOS online help/documentation, opening a support ticket with the development staff, or viewing your license agreement. The current EOS Client Onboarding system (LincDoc) version information can also be found here.
The windows button provides you with access to the list of currently opened windows (if any), and allows you to optionally tile the open windows on the workspace.
Hidden window are shown in italics, and can be re-displayed by selecting them.
Closes the current EOS Client Onboarding session.
To access secure forms in the EOS Client Onboarding system, individual users must be created. Once available in the EOS Client Onboarding system, the users and groups are assigned to roles, granting them rights to access various parts of the system.
Proceed to one of the following sections below for more information:
When working with new or existing users, you will need to locate the user in your user list.
When you create a new user, or need to update an existing user, you can do so using the user's individual settings.
You can reset a user's password. The EOS Client Onboarding system will then send an email to the user, informing them that they need to create a new password.
You can add a user to a specific group, which allows you to easily grant multiple users roles at the same time.
Tip: It is recommended that you assign roles to groups instead of individual users. Although you can assign individual users to roles, assigning groups allows for easier administration.
You can completely delete a user's account, if necessary.
Tip: If you accidentally delete a user, you can close the dialog box without clicking save, and the deleted user will still be available when you re-open the dialog box.
Sales Rep
Management/Operations
Manage Accounts
This is a list of the most common terms used throughout this documentation:
Term |
Definition |
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. |
authentication provider |
See provider. |
batch signing |
A feature that allows you to sign multiple documents with a single signature. |
bulk signing |
A feature that allows you to sign multiple signature fields, in a single document, with a single signature. |
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 EOS that stores all field definitions, source documents, generated documents and data. These cannot be created at the user level, but instead are directly tied to your license key - as created when you acquired EOS. In most cases, you will only have access to a single client ID, although multiple client IDs can be purchased, if needed. |
codelist (code list) |
Codelists are objects within EOS that drive drop down choice lists. For example, 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 |
Logic used to conditionally display or hide a field or section. Sometimes abbreviated as "c2d". |
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 |
Short for Comma Separated Values, which is 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 |
Short for Data And Number Generator, which is a key component of the EOS administrator interfaced 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 |
A file created using an eForm of Document Package. Basically the "filled-in" version of an eForm or Document Package. Also known as a generated document. |
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. |
document repository |
A searchable storage area where documents and data are saved. EOS has its own internal document repository, and third party repositories such as Laserfiche are also supported. |
document viewer |
The window in which the generated document is displayed. |
DRAT |
Short for Document Refinement Annotation Transformer, which is an extension of the EOS markup language for more sophisticated field resolution scenarios. |
drop-down list (DDL) |
An eForm 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. It is also comprised of field details, sections, conditions, actions, events, and lookups. |
end user |
Any person who uses EOS to complete a preconfigured eForm or Document Package. |
event |
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 EOS 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. |
generated document |
See document. |
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 |
Short for Java Database Connectivity. |
LDAP signature |
A type of signature in EOS 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 |
Short for EOS Archive. An eForm definition can be exported as an .ldar file, and imported to another EOS VM. |
EOS administrator |
The person responsible for creating eForms and corresponding field elements, conditions, lookups, actions, etc. within the EOS system for the end user community. |
EOS 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 |
Short for 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. |
multitenancy |
A type of software architecture where a single instance (installation) of the software runs on a server, but is designed to virtually partition (divide) its data and configuration. In this arrangement, each client organization (known as client IDs in EOS) uses a customized, virtual application. In the EOS environment, multitenancy is used to separate sets of forms and data. |
multi-value field |
A repeatable field that takes on multiple values. These are sometimes called "multi-row fields" or "pound fields" (because in the EOS markup language they are always terminated by a pound sign (#)). These field types are only available in Word source documents. Example:
|
node |
A specific item within a repository, accessed via the Browse dialog box. Nodes can be documents, files, or folders. |
OpenForm |
The term used to describe when an eForm is launched in a separate browser window (or iframe), and none of the normal EOS desktop controls are present (for example, no top toolbar with buttons for search, run, help, logout, etc.). This method 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. |
parse/reparse |
The process of resolving/finding fields in a document. A reparse operation typically takes place whenever a source document is altered. |
|
Acronym for "portable document format". |
pound field |
Another name for a multivalue field. |
provider |
Also known as authentication provider. Acts as a container for a specific set of users and groups. They can be created to control application access. They are created at the client ID level, making them available to other users with access to your current client ID. |
required condition |
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. |
signature |
Both a person's name, used to formalize a document, as well as a general term for the information that applies to all form fields to which a signature itself is applied. |
signature receipt |
A signature feature that displays the actual signature used on a form, information about the signature (such as the name of the user who signed and the date/time), and provides buttons for downloading the corresponding signed form or just the receipt information to a file. |
signature stamp |
An image that can be used in place of a script font representation of a signature, and is a digital representation of your actual signature. |
source document |
A Microsoft Word or PDF document containing zero or more fields. In the case of Word, the EOS 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 EOS. |
SQL repository |
A back end storage system that is based on a relational database. Currently, this database must be either PostgreSQL or Microsoft SQL Server. Note: This feature is available with EOS version 3.3 and later releases. |
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. |
stamp |
An electronic record, used with signatures, that captures details essential to demonstrate the authenticity of the signature. |
superuser |
Similar to a Windows Administrator account, this type of user is given access to a large majority of the EOS system and its settings. Typically, a non-cloud installation has only one superuser account called admin. Cloud installations never have a superuser account for security reasons. |
synchronization/sync/on sync |
An event indicating that a mobile device (for example, an iPad) is pushing locally saved forms/data to a EOS server. |
TIFF |
Short for "tagged image file format". |
token based name |
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 |
Short for "user interface" or the portion of the application with which users directly interact. |
UUID |
UUID (Universally Unique IDentifier) values can be thought of as random strings such as: 7402b0a6-d4da-489b-9955-8cc3f87735cb. UUID generators are very good at never producing the same string twice. For every document generated in EOS (regardless of the repository type: SQL Repository, Laserfiche, or Docuware), a UUID is assigned that is 36 characters long. The DANG function DocID can be used to return this value. The value is actually internally generated the moment you start a brand new form (and never changes for that form thereafter). This value is critical to doing any kind of workflow with a document, and is used to create URLs that allow direct access to manipulate a particular form (editing, viewing, signing, etc.). For more information on UUIDs, click here. |
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 EOS's bulk signing feature. |
user |
Short for "end user". |
user profile |
Stores the user's name, email address, time zone, password, and password reset question. |
LincWare is dedicated to providing its customers with the most efficient and affordable pathway to benefiting from its products. Each EOS Client Onboarding solution is designed around ease of use, exceptional cost-to-benefit value and rock-solid architecture.
Backing those product principles is a knowledgeable, 24/7 web-based technical support structure dedicated to solving any issue that arises in as little time as possible. In fact, one call is typically all it takes.
You can contact EOS Technical Support using any of the following methods:
If at any time your problem is not solved to your satisfaction, the chain of command is readily available to address it until you are completely satisfied.