How to submit Formotus forms in email

Formotus forms can submit using the email client on the mobile device or using a web service. When submitting by email, you can include 3 attachments: an HTML file that can be viewed and printed, an XML attachment that can be opened and edited as a Formotus form by anyone that has that form installed on their device; and/or a PDF. iOS, Windows and Android all use a web service  to create the PDF.  For Windows and Android, your device must be online when submitting a PDF. iOS will generate the PDF while offline.

You can choose which attachments you want to be included when submitting your Formotus form through email.  To select the attachments you would like included with each Formotus form, go to the Forms page, click on the form, then click on the Configuration gear icon in the right panel.


The HTML/PDF attachments will show one InfoPath view of the form, which can be specified as a setting in the Formotus portal or by naming the view "Formotus Print" in InfoPath. Read more about using special views.


Creating a Formotus Print view 

There are several reasons to create a print view separate from your data input views. If your form has more than one input view, you need to create a print view in order for all the information to be visible in the email attachment. Even if your form only has one view, you may want a second print view optimized for viewing and printing. 

Note: InfoPath has its own "print view" functionality that is unrelated to the Formotus feature. Do not use the InfoPath print view feature. Instead create a normal InfoPath view and name it Formotus Print.

Best practices for designing the Formotus Print view

  • Use layout tables that are sized for paper printing. Built-in InfoPath designs work well.
  • Use calculated value fields to display data rather than input controls such as textboxes, dropdowns, date pickers, etc.
  • Insert InfoPath page breaks for control over PDF layout as well as paper printing.
  • Think about using fonts, colors, underlining, etc. to help visually differentiate the entered data from the static labels.
  • Remember that the print view might benefit from being more or less verbose than the input view. For example, an inspector might fill a field labeled “Prob Desc” but the person receiving the printed report of the inspection could see the label “Description of the problem identified by our inspector” over the same information. On the other hand the field worker might need explicit instructions on filling the form that the reader of the report does not need.
  • An easy way to design your print view is to copy all the content from your other view(s), then delete or change that content as desired, To copy press CTRL+A to select everything in the view, and then press CTRL+C to copy the selection to the Clipboard. To paste the content into the print view press CTRL+V.

See also


Have more questions? Submit a request


Article is closed for comments.