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

2.2. LincDoc 3.3.4 Release Notes

Published on: 1 Feb 2015

This section contains information about the LincDoc 3.3.4 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:

Ability to Skip Multi-value Rows in a Generated Table (5073)

When working with multi-row tables, you can now skip a row within the table (via a condition) when the table is generated. This feature is controlled using the Skip row when generating attribute, which is available when the advanced check box is selected.

You should specify this attribute for the first field in a multi-value table. The defined condition is evaluated when the form is generated (the run button is clicked). If the condition is true, the corresponding row is not displayed in the form's table.

Ability to Use Check Boxes in Multi-row Tables (5086)

When creating a multi-row table in a Microsoft Word form, the use of check boxes within the multi-row table is now supported. In previous releases, the check box entry in the Word source document had to end with a pound sign (#) . However, this character is not supported in the check box syntax within Microsoft Word. Now you can end check box entries with an underscore ( _ ) instead of a pound sign (#), which allows the check boxes to function correctly within Word and the corresponding LincDoc form.

Important: This feature is not supported when using LincDoc Mobile (on an iPad).

For more information on creating check boxes in Microsoft Word-based forms, see Creating Check Boxes in Word Source Documents.

For more information on using multi-value fields within tables (and the general usage of the pound sign (#)), see Using Multi-value Fields Inside Tables.

New Action and Function Available for Setting User Information (5120, 5121)

A new action, Set user option, allows you to dynamically configure an option that gathers any desired, arbitrary piece of information (birthday, mother's maiden name, etc.). This information is then permanently stored with the user's profile (it does not expire after the user's current session).

The following settings are available with this action:

User option. Specify the name of the information that is being gathered (birthday, favorite color, etc.).
Determine how the information is collected. Typically, you will specify a field in your form that is then populated by the user. However, you can also specify a value or select a function, as with all other calculations. For more information, see Calculations.

Once the information is specified using the Set user option action, a new function, UserOption, is used to retrieve the information from the user's profile.

Once you select the UserOption function, the following settings become available, as shown above:

option. Specify the name of the information as defined in the appropriate Set user option action (the individual action's User option setting). This setting allows the function to locate and use the correct action.
default. If the name specified using the option setting (above) is not found, the value defined via this setting is used.

Timeout Settings Now Available for Topaz Signature Pads (5183)

Two new settings, labeled as Signature pad timeout, are available from the client's Configure dialog box. These settings allow you to control the timeouts (in seconds) when using Topaz signature pads.

The first setting (server) is used to specify how long the web application (LincDoc) will wait for a user to launch the signature pad application and sign the form. The countdown starts when the user clicks the sign button on the Signature View, thereby selecting the signature that will be signed. A value of at least 15 seconds more than the client time out (specified in the second setting described below) is recommended.

The second setting (client) is used to specify how long the signature pad application will wait for the user to sign before automatically closing. The countdown starts when the signature pad application launches. A value of at least 15 seconds less than the server time out (specified in the first setting described above) is recommended.

Exported File Name Now Displays Version Number (5328)

In previous versions, when exporting an eForm or Document Package, the resulting .ldar file name ended with four random characters to guarantee that a unique file name was created (and no previously exported files were overwritten). Now, a number is added to the end of the .ldar file name, which represents the version of that file (based on how many times the eForm or Document Package has been saved in LincDoc). For example, if your exported file name ends with 00013, the 13th saved version of that .ldar file was used during the export process.

Ability to Immediately Access the Signature View Following Form Submission (5331)

A new setting, Show sign prompt, has been added to the view document action, which allows form users to proceed directly to a form's Signature View when the form is submitted.

When this setting is selected (checked), after the Submit button is clicked, the Signature View is immediately displayed (and the Document Viewer is bypassed). When this setting is not selected (the default value), the Document Viewer first displays the form, and form users must click the sign button to open the Signature View.

Automatic Versioning Supported with DocuWare (5496)

In previous versions of LincDoc, DocuWare-based versioning, as provided by DocuWare file cabinets, was not supported. Now, automatic versioning is supported when LincDoc forms are sent to Docuware for storage. The following cabinets support this versioning feature: Document, Launcher, and Uploaded.

Important: The Data file cabinet does not support DocuWare versioning.

Ability to Add Text to Signature Pad Dialog Box (5705, 5706)

When using On-screen Canvas signatures (also known as "mouse signatures"), you can now specify text that will appear at the top of the Signature Pad dialog box, as highlighted below.

This text is defined using the new setting Signature blurb (HTML format) setting, which appears on the eForm / Document Package tab of the Admin dialog box.

You must specify HTML text when using this setting (plain text cannot be used), and the HTML text must adhere to the following guidelines:

It must be well formed (as described here: http://en.wikipedia.org/wiki/Well-formed_element).
It must not contain <html> or <iframe> tags

LincDoc will determine the validity of the HTML text when you save your form. If the text is not valid, an error message appears informing you of the issue.

Ability to Select a Subset of Lookup Results (5808)

When using a lookup action in previous versions of LincDoc, your form had to use either all of the results returned by the lookup or a single, selected result. To expand this functionality, you can now select a subset of a lookups returned results using the new Prompt to Select Some option available from the On multiple results setting. This option and its corresponding setting are available on the action's configuration dialog box, as shown below.

Note: This setting only applies when using a multi-row lookup (where multiple results are returned by the lookup).

Once this option is selected, a screen appears allowing you to specify which lookup results will be used by your form.

For example, if your lookup returns a dozen results, but you can only put two into your form, you can use this feature to select which two items are used.

For more information on configuring lookups, including using the other available On multiple results options, see Configuring a Lookup Action.

Security Configuration Now Available for DocuWare Repositories (5813)

When configuring a DocuWare repository, a Security Config button is now available, which provides access to security configuration settings that were previously unavailable for DocuWare repositories.

Note: This dialog box is accessed by clicking the configuration (wrench) button that corresponds to the repository on the Admin dialog box's Repositories tab.

When this button is clicked, the Role Security Config dialog box appears, allowing you to specify various security settings.

For more information on configuring DocuWare security settings, click here.

Microsoft Access Database Connections Now Supported (5847)

You can now use Microsoft Access databases when create connections to external databases for lookups.

For more information on setting up a connection to a Microsoft Access database, contact LincDoc Technical Support.

LincDoc Connector for Laserfiche Installation Enhancements (5860)

The LincDoc Connector for Laserfiche, which is a Java-based Windows service that allows LincDoc to write documents and data to external Laserfiche systems, has been updated to use a newer version of Java. This new Java version provides for enhanced connection security between the two applications.

For more information on this connector and how it is installed, see LincDoc Connector for Laserfiche: Installing and Configuring.

Improvements to Order of Search Indexes in LincDoc Mobile (5704, 5900)

Search indexes, defined on the Admin dialog box's Search tab (in the current search indexes list), were not being correctly displayed in LincDoc Mobile. Although the indexes were present, their order was arbitrary, and did not match the order defined in LincDoc. Now, the order of the indexes is consistent between the two versions of LincDoc (standard and mobile).

Corrected Defects

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

ID	Description
5309	When a folder is auto-created based on the token-based file name, the new folder now has the same owner as its parent.
5329	Form validation message does not show field data.
5427	Groovy scripts run multiple times add to Perm Gen space.
5434	Search fails for null values.
5745	DeleteData does not include schema name.
5751	Signature Receipt signature line does not stretch to cover the signature.
5796	Docuware: Invalid Content Length.
5835	Doc viewer image (PNG) mode does not display after signing.
5836	Docuware: Retrieve not working, especially not with attachments.
5839	Error appears if using a calculated label with a DRAT expression (and at least one other field has a default calculation).
5859	Connector test button from launcher-config.exe throws SSLPeerUnverifiedException with valid SSL certificate.
5861	Docuware: Fix possible errors (null pointers).
5863	Export to CSV: created-by, modified-by was a user name in version 3.0. It is now a uid.
5870	Saving to Laserfiche fails with default file name.
5871	Error using HTML edit link from Laserfiche 9.0 when a mapped template field is an integer field.
5873	Left, Right should return values when string is too short.
5894	An error ("No enum constant com.lincdoc.repo.security.ROperation") appears when attempting to edit repository security configuration.
5161	Long alert messages are truncated.
5287	Search: Out of range calendar inputs crashes application.

This page was: Helpful | Not Helpful

← 27.3. Creating an Email Template