The TOPICA framework lets the end user print individual forms (or rather: records = form instances). See Report Context.

The configurator may configure one or more reports for a given form (or rather: for records = form instances created by a given form). Such reports will be selectable (or selected automatically, if there is exactly one such report) when the end user selects a record an clicks the "Print" icon.

If the configurator has NOT configured such report(s), TOPICA uses the form template to auto-generate a print-friendly representation of the form.

Because this is auto-generated, the print representation has the same basic layout as the form template (the files come in same sequence, have the same labels, etc.). The differences exist to make sure, that ALL data is visible. The most notable differences are:

• All tabs in tabsets are visible.

• Values of text fields are NOT rendered inside text areas to avoid that some text is hidden, because the entered text is larger than the text area (the text area should have scrollbars in the situation).

• Fields are "read only", so that the end user cannot (accidently) modify fields before printing.

Because this "print view" is auto-generated, there is not much a configurator can do to customize it. There are a few possibilities, though:

• Form elements may be hidden completely from the print view by setting the ExcludeFromPrint to true.

• The Print.css stylesheet, that is part of the current skin, is used to display selected elements differently on print as compared to on screen.

  Caution
  Contents in the popup window is still rendered for screen. So any modifications in Print.css will only have effect on printed paper and in "Print preview".