So far, we have discussed how to use the Form Designer, Navigation, and Layout, all of which are meant to lead to submission. When users fail to complete submission of the form, the form is said to be abandoned. This is a most unwanted result and a waste of time for everyone.

 

Users are often asked to upload files, called attachments, as supporting documentation. Most attachments are generated outside of the form, and can be scans, Word documents, PDFs, JPEGs, PNGs and so forth.

 

However, there are form elements capable of generating attachments from within the form, for example:

•scribble pads for users to make their signature

•camera widgets for uses to take pictures with a mobile device's in-built camera

•barcode-reading widgets for use with a device's camera.

 

Defining attachments (i.e. files uploaded with the form) used to done exclusively in Transaction Manager. Now these can also be defined in Composer.

 

The Preview function of Composer does not include user interactions when they upload attachments; for that, you will have to publish to Transaction Manager.