The Form editor allows Form properties to be modified and Fields to be added, removed and modified.


No changes are made to the Form until the Form is Saved. This includes added, deleted and changed fields.

View Options

  • the Form Fields can be viewed with a Rave Classic-like style, or Rave EDC.

  • the Field Properties sheet can be displayed or hidden

  • the Form Fields can be displayed with or without key properties such as Field OID.

  • an EDC Role can be selected. View Restricted and Inactive Fields will be greyed out. Entry Restricted Fields will have the data entry control disabled.

The above view options will be remembered when moving between Forms.

Adding Fields

New Fields can be added by clicking on any of the Add buttons at the bottom of the field area. The add buttons allow you to quickly add Text, Label, Date/Time and Data Dictionary fields.

Fields can be added to the top or bottom of the Fields list, or before or after the currently selected Field.

Reordering Fields

Fields may be re-ordered by dragging a field line to a new position in the list. When approaching the top or bottom of the fields visible in the display the list will auto-scroll. If the auto-scroll pauses then moving the mouse slightly should restart it.

Deleting Fields

A Field may be deleted from the Field list if it is not referenced by any Edit Checks / Derivations. The deletion of a Field is finalized when you Save the Form.

The Field Property Sheet

The Field Property sheet shows the properties of the currently Selected Field. Some attributes of Fields are disabled for editing when certain control types are selected. For example, a Label field cannot have a Variable OID since it does not collect data. Similarly, non-Date/Time fields should not have "Query Future Date" set. Note that often controls are "greyed out" to show that they should not be used but since Medidata Rave allows Field attributes to be set this way TrialGrid does not prevent all conflicting combinations.

See also

Field Properties

Standards Management

The Form editor provides a number of Standards Management features which are displayed only when a Draft is part of a Standards Management Project.

Some of the capabilities of the Standards Management control area can also be achieved, more flexibly with Standard Rules.

Fields may be Removed

When this checkbox under the Standards Control tab is checked, it means that Fields may be deleted from this Form without triggering a standards compliance difference. Note that Fields which are set as "standards required" (see below) cannot be deleted without triggering a compliance difference. This allows you to set up forms where some fields can be deleted but some are required. Without this checkbox set, deleting any field will cause a compliance change.


Standard Rules can be created which override these settings. For example a MUST EXIST rule for a field will ignore the "fields may be removed" settings. Advanced users may prefer to use Standard Rules.

Fields may be Added

When this Standards Control checkbox is checked, it means that new Fields not in the standard Form may be added without triggering a standards compliance difference. Without this checkbox set, adding a new field not found in the standard form cause a compliance change.


Standard Rules can be created which override these settings. For example a MUST NOT EXIST rule for a field will ignore the "fields may be added" settings. Advanced users may prefer to use Standard Rules.

Form Allowed Changes

There may be some Form attributes which are expected to vary in library forms or in draft Forms which use this form as a library. For example, the Form Help might change based on the therapeutic area. The Allowed Changes area allows you to select one or more Form-level attributes as attributes which are allowed to change without triggering standards compliance findings. e.g. if Help is an attribute selected in this area then a Draft Form which uses this library for compliance can have any value entered for Help and Help is ignored for standard comparison purposes.

In this allowed-change list you will also see standards-compliance related attributes such as "Allow Deletes" and "Allowed Changes". Modifying these attributes makes sense when you have a core library which is used by a Therapeutic Area library. The Core library may state that the Help attribute can be changed but the Therapeutic Area library may want to take away this capability. When comparing the Therapeutic Area library to the Core library these settings will be taken into account when comparing their standards control settings. These settings have no meaning when comparing a study draft (non-library) draft against a library draft.

Field Allowed Changes

At the Field level, the Property sheet has a "Standards" tab with two options:

  1. A checkbox, Required / Not Required which controls whether this Field may be omitted in a Draft that uses this Form as a standard without requiring explanation. Note that this is only valid if at the Form level the "Fields may be deleted" option is set. Otherwise, it is ignored.

  2. A selection box allowing Field properties to be omitted from compliance checking. Any Property name selected in this list (multi-selections are possible) is ignored for the purposes of compliance checking. This allows a Field to have Standard Properties set but to ignore (for example) the Pre Text or Help Text properties if these should be modified in studies which use this Form.


Standard Rules can be created which override these Field-level settings and state that a particular field (or a field with an OID matching a particular pattern) MUST or MUST NOT exist.