Home →
Using LincDoc 3.1+ →
Reference Information →
eForm Design Considerations
27.1. eForm Design Considerations
This topic contains best practices and tips that may be useful when designing your eForm.
Best Practices
- Use standard naming conventions for fields so you can utilize the global fields library. For example, all date related fields end with the suffix _dt, phone number fields end with _phone, address fields end with _addr, etc. If you plan to integrate your eForms with an external repository, it is recommended to try to keep the names consistent there as well. For example, if saving documents/data to Laserfiche, keep the field names consistent with the Laserfiche template field names.
- Early on in a new eForm set all the field types first before diving into calculations, lookups, etc. Be sure to press save after setting all the field types.
- Make small incremental changes to existing, stable eForms. For example, make a small change (like altering a calculation), test that it works as desired, and then save the changes. Then move on to other changes (if necessary). Alternatively, use the export/import feature to work on a copy of the eForm without having to worry about breaking existing functionality.
- When editing eForms, it is recommended to use Firefox 9+ or Google Chrome 16+, because these browsers have very fast Javascript engines. Editing eForms is a very Javascript-intensive task.
PDF Source File Tips
Take note of the file size of PDF source documents prior to building eForms and then just before placing them into production. It is not unusual for a PDF, over the course of many small edits, to continuously grow in size. The bigger the PDF, the longer it will take to process, and the longer it will take users to download, view, and possibly sign. The size of a PDF can be reduced by printing the document to a new PDF, and then copying the fields from the large document to the small. If the source doc is a scanned PDF, there is an option in Adobe Acrobat to optimize the scanned PDF, which also works well. In one recent example, the former method was used to reduced the size of a PDF from 2.2 MB to 300 KB.