Home → Using LincDoc 3.1+ → Release Notes → LincDoc 3.2.3 Release Notes
2.13. LincDoc 3.2.3 Release Notes
Published on: 17 Aug 2013
This section contains information about the LincDoc 3.2.3 release. This release contains both new features and corrected defects from previous releases.
New Features
One new feature has been added with this release.
New Loop Function
The new Loop function can be used with a multi-value table, allowing you to perform calculations (a running total) on dynamically added form entries.
An example of the loop in a LincDoc calculation is shown below.
Note: In this example, two images are used to show the calculation, since you need to scroll inside the Calculated field dialog box to view the entire calculation.
Corrected Defects
The following table provides a list of the most important defect resolutions.
| ID | Description |
|---|---|
|
3591 |
When creating a new condition (using the Condition to display option on the Fields/Sections tab), the newly created condition is now automatically selected in the corresponding drop-down list, and will be used in the form without any further action by the user. Previously, after creating the new condition, you would also have to select it from the drop-down list. |
|
3604 |
If a backslash ( \ ) was used when creating token-based document file name (in the Token-based name text box on the eForm tab), an error message appeared when the eForm or Document Package was saved. Now all backslashes ( \ ) are automatically converted to forward slashes ( / ). In addition, any spaces around the slash are removed. For example: If a file is created using a customer's first and last name and is specified as "Smith \ John", the actual file name would automatically be converted to "Smith/John". |
|
3606 |
The condition operator "contains" was not returning proper results. |
|
3607 |
If a condition was created and used in multiple places, including as a rule on a field-level event, and the condition was later deleted, the field-level events no longer displayed properly. Furthermore, the rule could not be edited or removed. Now the application displays a warning about such issues and allows them to be fixed. |
|
3608 |
When using PDF source documents that contain check boxes, and the default check box states of "Off" (cleared) and "Yes" (checked) were not used, and only a single state was defined (a replacement for one state existed, but not for both), an error message would appear. These types of PDFs (PDFs with single-state fields) are now allowed and will not produce an error. |
|
3620 |
If a field has its Condition to display option set to the value of another field's codelist, and the other field's codelist was changed to a different codelist, the Condition to display option for the dependent field was not recalculated correctly. For example, if "field2" is set to display only when "field1" is set to "yes", and "field1" is set to "no", "field1" was correctly updated, but "field2" still displayed, even though it was expected to be hidden. |