Overview
EForms is an add on module that provides a robust custom form builder that integrates
creating, submitting, and processing electronic forms seamlessly through the
ECMToolbox workflow process. The integration provides the ability to create EForms
per workflow, map and export individual forms to the Document Management System,
or utilize forms as part of a more complex workflow design.
Sections
The EForm Administration composes of four main sections (tabbed buttons in main window):
EForms -- Forms are filtered by workflow. Select the workflow from dropdown (if more than one).The list of created forms are display and button to create new forms. Selecting a form from the list, gives access to the other tabbed buttons in the EForms Administration window.
EForms Creator –The web-based application form builder is the main component to creating the EForms. To access the Creator, either click the Add button to create a new form, or highlight the Eform in the list and select the Eform Creator tab.
EForms Mappings – Provides configuration for mapping the EForms to the Document Management System. Primarily one connection is created to map the document management fields to the EForm questions. The questions used for mapping are setup with an additional property value for export within the EForms Creator.
EForms Preview – Quick access to display the layout of the configured EForm, view PDF rendered outputs, and test the overall interactivity of the EForm.
Access
Access to the EForm Administration is via the Links section from the left-hand panel of ECMToolbox. By
default the link will be labeled “EForm Administration”. This label is customizable and may be different in
your environment. If the Link is not present, you may not have permissions to see it. This can be enabled
under ECMToolbox Administration.
The EForm Administration will display in the main window.
EForms Selection
The dropdown will default to the first workflow setup within the ECMToolbox
workflow system. If your system is configured with more than one workflow, use the dropdown to filter
EForms list to the specific workflow.
NOTE: If there are no workflow showing in the dropdown, you must configure a workflow from the
ECMToolbox Workflow Designer first. See the ECMToolbox Administration – Workflow Designer
for more information.
Add Button: Use the Add button to create a new EForm. A unique form name will automatically be
generated and added to the forms list (example – “Form(New) – 15098498733”). You can change the
form name at any time in the EForms Creator.
After clicking to Add an EForm, select the EForm (selected row will be highlighted), and select “Edit”
button link or the EForms Creator tabbed button.
EForms Creator
The interface is presented in a survey style environment where questions will be placed on the form through the use of single input textboxes, single or multiple choice drop down lists and checkboxes along with a host of other input gathering formats.
Eforms is based on the SurveyJS standard. This website can be used when help is needed in designing and programming a form. (http://SurveyJS.io).
This is the interface you will see when you start a new form.
The EForms Creator is what you will use to create the form. On the right side of the screen are the toolbox items. These items represent the questions you will be placing on the form. After you place a question on the form, the question’s settings can be accessed by clicking the Properties button.
The center of the screen is the workspace where questions will be placed. Due to space constraints on the form design page, the placement of the questions are not WYSIWYG. So even though the placement of the questions in the work area do not line up as you intended, when you Run the form, the questions will appear as planned. You can hide the left side screen to give the design area a bit more realism as to how the form will look when Run.
On the left side of the screen are the database connection(s) and tie-ins that allow data to be accessed from a database and shown on the form. The DBLookups section allows for database integration. An example might be a drop down listing. Instead of hard-coding the choices into the question, the drop down list could be pulled from the database so that if the list needs to be updated, the database would be updated and the question would simply show the values.
Another example might be auto-fill which will enter data, stored in a database, into a field based on the value of another field.