What is an eForm?
  • 14 Sep 2020
  • 2 Minutes To Read
  • Contributors
  • Print
  • Share
  • Dark

What is an eForm?

  • Print
  • Share
  • Dark

The Basics

For Normal People

A single form is a lot like an Excel spreadsheet, with a form that lets you input data for a single row at a time.

For Developers

In database terms, an eForm is (almost) equivalent to:

  • A single database table
  • 1 or more forms (called views)
  • 1 or more reports on that table (called profiles)

When you add a data control to a form, you are prompted to give it a name. This is exactly the same as creating a database column. This has the interesting effect that you build the user interface for a database table at the same time as defining what data should be in the table.

System Fields

Name Notes
EFormType Always the name of the current eForm
RecordID Unique identifier for this record
LineNumber This is the current line number in a multiline eForm record
Description* A generic description field that will be displayed in situations where the whole record cannot be displayed. E.g. child eForm tables
Assignee* If your username or the name of a group you are in is in this field, this record will show up in your ‘My eForms’ tab.
Status* The current workflow state. When set to the special value ‘Closed’, most controls on the form are disabled and formulas are not executed.
Priority* How urgent/important to treat this record.
Originator User who created the record
Sender User who last saved the record
DateCreated Date/time the record was first saved
DateLastUpdated Date/time the record was last modified
DateClosed Date/time the record was set to closed status. This is reset when the record is re-opened.

Many of these are read only and will be filled automatically. (*) The only ones that can be changed by a user or by a formula are: Assignee, Status, Priority and Description.

Workflow Fields

Assignee, Status and Priority are considered to be ‘Workflow’ fields, which trigger some notifications and workflow transaction log entries are added when any of these are modified.

eForm User Interface (Views)

View Structure

An eForm can contain one or more user interfaces, called a ‘View’. A view has the following nested structure.

  • View
    • Section (A section can be used to define a different page layout for part of a form)
      • Block (Blocks allow grouping of related data, and also automatic flow layout when blocks are collapsed or hidden)
        • Controls are individual elements such as labels, text boxes, buttons and so on.


Was This Article Helpful?