> For the complete documentation index, see [llms.txt](https://docs.norrnext.com/norrcompetition/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.norrnext.com/norrcompetition/fields/creating-field.md).

# Creating Field

To create a new field proceed to the fields list and click on the "New" button. A new field form will open:

<figure><img src="https://norrnext.com/images/docs/norrcompetition/fields/field_add.png" alt="New field form - NorrCompetition"><figcaption><p>New field form</p></figcaption></figure>

Below is the list of all available field settings and its descriptions.

* **Title** – the title of the field. It will help you to identify the field in the list of fields (for example in contest settings) if you use the same label for several fields.
* **Type** – the list of field types. The field types are described [here](https://docs.norrnext.com/norrcompetition/fields/field-types).
* **State** – the state of the field: published, unpublished or trashed.
* **Label** - the label tag.
* **Hint** – a text inside the field input. The 'placeholder' attribute.
* **Description** – the description for the field. The 'description' attribute.
* **Filter** – this will sanitise a user input. The 'filter' attribute.

  You can set the following filter types:\
  STRING – converts the input to a plain text string; strips all tags / attributes\
  INT – uses the first integer value\
  UINT - the first unsigned integer value\
  FLOAT - uses the first floating point value\
  SAFEHTML - removes unsafe tags and attributes\
  URL - removes all the symbols not related to URL\
  TEL – removes all the symbols not related to phone number\
  USER\_UTC - converts a date to UTC based on the user timezone offset\
  SERVER\_UTC - converts a date to UTC based on the server timezone offset\
  Text Filters - use text filter settings from system global configuration

  If you use the field of type 'Calendar' without the time then use the STRING filter. Otherwise, the date will be converted incorrectly.
* **Visible** - show or hide the field in the list of entry fields on front-end.
* **Required** - include the 'required' attribute.
* **Class** – the class or several classes separated with the blank space. The 'class' attribute.
* **Size** - the size of the field. The 'size' attribute.
* **Maxlength** - the maximum input symbols for the field. The 'maxlength' attribute.
* **Nofollow** - enable or disable nofollow for the field. The 'nofollow' attribute is used for the 'URL' field.
* **Width** - the width of the field in cols. The 'cols' attribute.
* **Height** - the height of the field in rows. The 'rows' attribute.
* **Autofocus** - the autofocus for the field. The 'autofocus' attribute.
* **Autocompelete** - enable or disable autocomplete for field. The 'autocomplete' attribute.
* **Format** - the date and time format for the field. Is used for the 'Calendar' field.

  The most frequently used date string codes:\
  %d - day (0-365); %m - month (1-12); %Y - year (for example, 2015)\
  %H - hours; %M - minutes; %S – seconds\
  \
  More information you can get on the page <https://docs.joomla.org/Calendar_form_field_type>
* **Field Values** - is used for fields 'List', 'Radio' and 'Checkbox'. In the table you should set Text (is displayed to a user) and Value (is submitted to the server for saving).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.norrnext.com/norrcompetition/fields/creating-field.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.