The Fields tab

See every review field for your template, where each one reaches the report, and set which fields a reviewer must answer.

The Fields tab in the template editor lists every review field for the template’s state, whether or not your report uses it.

Opening the tab

Open Settings > Templates, click the template you want, then select the Fields tab.

The tab is read-only until you click Edit Template to create a draft, the same as the rest of the editor.

Reading the table

Each row is one review field:

  • Field - the field as a reviewer sees it.
  • Review tab - the tab of the review it sits on.
  • In the report - the report items that use the field.
  • Reviewer must answer - whether a value is needed before the review can be finalised.

Filters above the table narrow the list to fields that reach the report, fields that don’t, or fields a reviewer must answer. Each filter carries a count. The search box filters by field name.

The Fields tab showing the filters and the field table

Where a field reaches the report

Fields reach the report through items. A row showing Used by 2 items expands to list them, each with the section it sits in and an Open item button that jumps to it in the editor.

An expanded field row listing the two items that use the field

Two labels mean no item is using the field:

  • No items use it - nothing in your report needs the field, so reviewers are never asked for it.
  • Not in the report - prescribed field - no item prints the field, but your report still needs it, usually because a figure elsewhere is worked out from it.

To start reporting on a field, open an item on Report Items and set This item reports on to that field.

Setting a field as required

In a draft, set a field’s Reviewer must answer dropdown to Required or Optional.

A required field carries a Required label on the review, stays expanded and can’t be hidden or removed. A reviewer can’t click Generate Draft until every required field has a value.

Changes save to the draft as you make them. Click Publish changes to apply them.

The Reviewer must answer dropdown open on a field row, showing Required and Optional

Some rows show text in place of the dropdown:

  • Required by Curia - required and cannot be disabled.
  • Not collected - nothing in your report needs this field, so there is nothing to require.
  • Optional - your report needs the field, but it can’t be made required.

FAQ

Why did a field I set to Required become Not collected?

Its required setting is still stored, but nothing in your report needs the field any more. Check the In the report column: if it reads No items use it, the item that reported on the field has been excluded or repointed at a different field. Bring the field back into the report and the dropdown returns.

Why do some fields have no Required option?

A field that Curia requires, or that can’t be required at all, shows its state as text instead of a dropdown. Those aren’t configurable.