Home → Using LincDoc 3.1+ → Release Notes → LincDoc 3.2 Release Notes

2.16. LincDoc 3.2 Release Notes

Published on: 16 Aug 2013

This section contains information about the LincDoc 3.2 release. This release contains both new features and corrected defects from previous releases.

New Features

The following new features have been added with this release:

Uploading a CSV File into an Existing Table

You can now upload a CSV file into an existing table. A CSV file can be added when editing a JDBC lookup or configuring a database.

When editing a JDBC lookup, the upload button appears on the codelist dialog box, which is displayed when you click the edit button for an existing codelist.

The codelist dialog box and corresponding upload CSV button are shown below.

You can also use CSV files to update tables via the Databases dialog box (which is accessed using the system button). Each database has its own individual upload button, as highlighted below.

New Token-Based Name Creation Interface

You can now use tokens to dynamically generate a document's path and name. This option is available from the eForm tab.

When you click the corresponding arrow button (highlighted above), the Token-based path for generated documents dialog box appears.

This dialog box allows you to used the tokens (displayed on the Tokens tab) to define path and file information.

You can perform the following actions using this dialog box:

Add a token tag by selecting a token from the Tokens tab, and clicking the Add button; by double-clicking a token; or by dragging-and-dropping a token into the Path text box.
Modify a token tag by selecting it in the Path text box, and clicking the Modify button; or by double-clicking the token in the Path text box.
Delete a token tag by selecting it in the Path text box, and clicking the Delete button; or by dragging-and-dropping it outside of the Path text box.
Move a token tag using the Left and Right buttons.
Remove all of the contents of the Path text box by clicking the Clear button.
View the full DRAT content of the tags in the Path text box by clicking the Show DRAT check box. When this check box is cleared (unchecked), the tags display using a simple format.

Tip: You can also hover your mouse pointer over a tag (that is currently using the simple format) to view the DRAT content.

New Generation Calculations

A new type of calculation, Generation, is now available. This calculation is executed when documents are generated. You set the calculation on the Fields/Sections tab.

Note: This calculation is only available when you click the advanced check box.

An example of when this type of calculation would be useful is if you want to reformat a date from the default format (01/01/2013) to a text format (such as January 1, 2013) when your document is generated.

Offline Lookups on iPads

When using the iPad app, offline lookups are now available. Offline lookups allow you to reuse existing data when not connected to a server (when "in the field"). They retrieve all available data from a server at once, which allows them to then use a filter that can be evaluated by an offline device (such as an iPad). Any lookup that uses a DANG condition may be used offline, as all of the data may be retrieved by using a "always" condition, and offline devices can evaluate the DANG expression.

Updating Other Fields When Applying or Declining Signatures

You can specify fields that will be updated on PDF documents when the documents are signed.

These fields are selected using the Fields to update when signing section of the Field attributes (on the Field/Sections tab).

Use the check boxes in this section to specify the fields that will be updated when applying the signature.

The selected fields are then updated after the signature field value is created and set to the form data, but before the signature is stamped on the document, allowing these field values to be written to the document at the same time as the signature.

You can also specify fields to update when a signature is declined using the Fields to update when declining section of the Field attributes.

The selected fields are updated when a signature is declined and the document is not signed.

New "Clear Multi-value Table" Action

You can now clear all values from a multi-value table using the Clear Multi-value Table action.

When this action is used, you need to specify the field in the table that will be cleared when the action is executed.

For more information on using actions, see Actions.

Password Reset Question/Answer Required

In order to enhance the application's security, you are now required to set up a password reset question and answer when you login, if one is not already set.

You can also update the information at any time using the profile option available from the User Profile button, as shown below.

The Preferences dialog box appears, showing the security question options.

Password Reset (Security Question) Answer Securely Stored in Database

The answer to the password reset question (shown below) is now cryptographically hashed in the database for enhanced security.

Database Authorized Provider Username is Case In-sensitive

Usernames and email addresses for internal authentication provides are no longer case-sensitive.

In addition, you can no longer have duplicate usernames for the DB authentication provider.

New User Registration Feature

The new user registration feature allows for the easy creation of new LincDoc users. The feature generates a path (URL) to your LincDoc instance, which you then distribute to the potential new user (typically via an email message). The new user accesses LincDoc via the path, provides all of the necessary login information, and a new LincDoc account is dynamically created.

The feature is accessed using the system button on the main LincDoc interface, as shown below.

For more information, see Registering a User.

Deleting an Existing Path

If a path has already been defined but is no longer needed, you can click the Delete button to remove it.

Viewing a Path's Link

You can view the link associated with a defined path by clicking the Link button on the User Registration screen.

The link appears in its own dialog box, allowing you to either click it directly or copy it.

This link can be copied and emailed to the prospective new user.

Default Authorized Provider, Groups, and Roles Now Automatically Set for New Clients

When a new client ID is added, a new internal authentication provider is automatically created, and several default groups are added.

The following default roles and groups are used.

group	roles	parent groups
Users	login
Administrators	admin	Users
Form Admins	form-admin	Users
Report Admins	report-admin	Users
User Admins	user-admin	Users

For more information on roles and groups, see Security.

Additional File Types Available with "Append Files to Uploaded Documents" Action

The following additional file types can now be uploaded when using the Append Files to Uploaded Documents action:

.jpg
.jpeg
.tif
.png
.gif

Ability to Determine if Template Data is Included with Uploaded Files in Laserfiche

By default, template data is no longer automatically saved with uploaded files (stored as separate documents) in Laserfiche. If the template data is needed with uploaded files, you need to activate the option.

To locate this option, open the Repositories tab, and click the edit button for your Laserfiche repository. The Configure dialog box appears, and the option is displayed (as highlighted below).

For more information, see Laserfiche Repository Configuration.

Ability to Reorganize Prompt Columns for Lookups

You can now alter the order of the information that appears as prompts once a lookup action has been initiated in an eForm or Document Package. Prompts give users the ability to select specific lookup results.

When working with a lookup action, you can access a specific lookup using the edit button via the drop-down list in the lookup column, as shown below.

Once you access a lookup, the lookup dialog box appears. The Prompt columns tab on this dialog box displays the available prompts for the selected (accessed) lookup.

The rows can now be reorganized by dragging and dropping them in new locations. When you click and hold your mouse button on a specific entry (row) and begin to move it, a "check mark" icon appears, showing you that the selected item is being moved.

When you release your mouse button, the selected item is moved and the displayed prompts are reorganized.

For more information on lookup actions, see Database Lookups.

Creating CodeLists Based on the Values from Multi-value Fields

You can now dynamically populate a codelist based on values you set in specific fields in an eForm or Document Package. This new type of codelist is specified using the Multi Value Field option from the Type drop-down list when creating a new codelist, as shown below.

When this type of codelist is created, the codelist dialog box appears, allowing you to set up the codelist using an existing multi-value field.

(optional) Provide a description of the new codelist in the corresponding text box. This description appears below the name of the codelist when selecting it from the Codelist(s) field on the Fields/Sections tab.
Using the Any field in source table drop-down list, select any existing field in the table that will be used to create the codelist. This option is used to determine the table for the codelist. Any field in the table can be selected.
Click the refresh button.
(optional) Click the auto-map button, which, in most scenarios, automatically populates the code, label, and description drop-down lists using the first three rows in the selected table.
If necessary, specify the following information using the corresponding drop-down lists (if you did not use the auto-map button or if the auto-mapping is incorrect):

code. The field that will be used to specify the information that will be stored in the database and generated documents.
label. The field that will be used to create the main entry seen in the codelist - the item that will appear and be selected from the drop-down list on the form.
description. The field that will be used to create a description of the main entry. This description will appear below the specified label.

Click save.

For example, if "1" is specified for code, "blue" is specified for label, and "the color of the item" is specified for description: The corresponding drop-down list on the form would show "blue" as an option, with "the color of the item" appearing immediately below the "blue" selection. If "blue" is selected, the value of "1" would be submitted via the form and stored in the database.

Once the codelist is defined, it can be dynamically created using the specified fields directly in the corresponding eForm or Document Package.

Adding an Uploaded File After a Specific Source Document

When using an upload field type, you now have the option of specifying after which source document the uploaded file should appear using the Append after option. This option provides better control over where uploaded files appear in your final form.

When you upload your file, the file will appear after the selected source document.

Purchases Using Amazon Marketplace Now Supported

eForms and Document Packages can now use Amazon Marketplace to support online purchases.

New Credit Card-based Features

Several new features have been added that facilitate credit card usage with your forms.

New Document Package Event

When creating a Document Package, you can now specify actions and rules that will take place after a credit card is approved using the After credit card processing event.

Two New Actions

Two new actions have been added for dealing with credit card transactions: credit card payment and credit card return.

New System Command

The new command available from the system button, accept credit card terms, allows you to set up credit card payment information in your LincDoc installation.

Changed Behavior

The following changes in the way the application behaves should be noted, especially if you are upgrading from a previous version.

Close Document Viewer after declining, add default rule to show document

Prior to LincDoc 3.1.3.27, declining a signature field did not make any changes to the generated document, and, therefore, did not close the Document Viewer and open a new one as the document had not changed.

Now, when a signature is declined, the Document Viewer can be closed and reopened, with any fields selected for updating after a declined signature being automatically updated, using the After declining event.

If you are upgrading from LincDoc 3.1 to 3.2, you will need to update your form configuration appropriately. In most cases, this update will consist of adding the "view document" action to the After declining event.

Corrected Defects

The following table provides a list of the most important defect resolutions.

ID	Description
3139	log4j level resets to DEBUG after tomcat restart
3150	Selecting multiple fields in the Field/Section tree using the SHIFT key does not work correctly.
3272	Do not allow slash (/) in lookup or codelist id
3309	Token-based name picker interface: ability to clear tag on modification and save it
3310	Token-based name picker interface: Fields tab has an extra blank column
3320	Cannot add custom property to JDBC database configuration
3321	Editing a named rule does not trigger the "this form has unsaved changes" message
3338	DocPkgCombobox creates a RepositoryManager for each document package
3364	Laserfiche: Uploaded fields from an iPad do not get populated into repository
3369	Admin user cannot import ldar or create new Document Package
3373	Poor error message when it is not possible to append upload type
3377	Error after generate does not force regenerate
3379	"Incorrect username or password" message when changing admin password for the first time
3380	NPE shown at login
3388	Security access checking broken
3390	Error saving user profile when it is not possible to change username
3423	DocRequest logs in as guest and then goes to login page
3436	LDAR import fails when replacing a Document Package with named actions or conditions
3459	Signature field: Signer name field does not keep selected field displayed
3460	Search: Generated forms do not appear to be searchable on local server
3464	No columns listed for views in JDBC lookup
3469	NPE while signing from email link

This page was: Helpful | Not Helpful

← 27.3. Creating an Email Template