The Data / Viewer Fields section of the toolbox holds the fields that bring other parts of the system onto a form: search results, documents, workflow items, another E-form, or data fetched from elsewhere. They are what turn an E-form from something you fill in into a screen you work from - a dashboard, a review page, a portal.


Several of these fields come in an internal and a public pair. The internal versions show what the signed-in user is allowed to see. The public versions are for forms used by people outside the organization, and they only reach records the site has been set up to expose - through Public Access or, for a signed-in external user, Collaboration. Use the public version on any form that will be shared outside; use the internal version everywhere else.

All of these fields share the settings described in Common Field Settings, and their conditions work as described in Field Conditions.


The fields

Record Notes - Shows the current record's notes and lets internal users add to them, the same as the notes panel in the viewer screen. See Record Notes.


Search Results - A results table for internal users, from a saved search or from criteria set on the field. See Search Results.


Document Viewer - Shows a document to internal users. See Document Viewer.


Document List - A clickable list of documents, usually paired with a viewer to build a reading screen of your own. See Document List.


Public Search Results - A results table for external users. See Public Search Results.


Public Document Viewer - Shows a document to external users. See Public Document Viewer.


Data Source - An invisible field that fetches data once when the form loads and holds it for charts, calendars, maps and tables to use. See Data Source Field.



Workflow List - Shows workflow items to internal users. See Workflow List.


E-form - Loads another E-form inside a panel on this one. See E-form.


Custom Options - Builds a drop-down list from an external REST call. See Custom Options.


Required Documents - Shows what a record still needs and lets the user supply it without leaving the form. See Required Documents Field.


Building a screen from these fields

The pattern worth knowing is that these fields talk to each other. A Search Results field can put the ID of the record the user clicked into another field; a Document Viewer or Document List pointed at that field then shows that record's documents. Add a Button Bar to switch between views and a Modal Window for editing, and the form becomes a working screen rather than a questionnaire.


Where several of them need the same data, use a Data Source rather than repeating a search in each: it is fetched once and shared, so a chart, a table and a map can be driven from one query.