Includes Conditional Field Behaviors, “Read-only” Digital Assets, render File Attachments as images on a form, and other UI improvements and fixes.
Conditional Field Behaviors
A version of QB Form Rules (the QB API doesn’t let us import QB Form Rules). This controls field behaviors (Require, Show, Hide, Enable, Disable) based on input to another field (checkbox, radio button, or dropdown fields). These are set in a Field’s Properties in each form, and work like QB Form Rules.
This feature, including combinations of conditions and rules can significantly improve form completion accuracy and completeness.
“Read-Only” Digital Assets
This major feature, particularly combined with QR codes, has volumes of uses to expand the information and service a company provides its customers, employees, the public and others. These are assets that are digitized in the Form Engine that are read-only, they aren’t mapped to any data. They become images with URL permalinks and QR codes, to be used anywhere. Whereas URLs/links are mostly usable only where they can be clicked, QR codes can extend mobile access to those assets anywhere in the physical world. So any type of documents, static information, maps, diagrams, directions, contact info, and more can be easily made into Digital Assets and managed centrally in the Form Engine.
Also, these assets do not live in Quickbase, so they can be shared anywhere, unlimited, without any user licensing requirements. They can also be printed or saved as pdfs, which does count as a transaction in the Form Engine.
File Attachments as mbedded Images
Adding File Attachment fields on a form can work for three purposes: 1) for form completers to attach a file(s) when submitting a form. 2) As e-signatures. 3) As embedded images in the form. When adding a File Attachment field to a form, the Form Engine opens a popup of Field Properties for the form builder to choose which use they intend for that File Attachment field.