> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/references/terminology.md).

# Terminology

## Custom Field/User-Defined Field

As of Clarity LIMS v5.0.0, the term **user-defined field** (UDF) has been replaced with **custom field** in the user interface. However, the API resource is still called UDF.

There are two types of custom fields:

* **Master step fields** — Configured on master steps. Master step fields only apply to the following:
  * The master step on which the fields are configured.
  * The steps derived from those master steps.
* **Global fields** — Configured on entities (eg, submitted sample, derived sample, measurement, etc.). Global fields apply to the entire Clarity LIMS system.

## Run Mode

* **Samplesheet run mode** - Only the sample sheet is generated and stored on Clarity LIMS. Run/Analysis configuration is imported manually into the instrument via a sample sheet to start the run. The downstream secondary analysis is performed on-premise. In NextSeq 1000/2000, this mode is also known as the Local Mode.
* **Hybrid/Cloud run mode** - The planned run is created on ICA based on the run/analysis data from the integration service. The planned run contains all the run and analysis configuration required to start the run on the instrument. The sample sheet is also generated and stored on Clarity LIMS for reference purposes. In **Cloud** run mode, the analysis is performed on the cloud whereas in **Hybrid** run mode, the analysis is performed on-premise.
* **Local run mode** - The planned run is created on IRM based on the run/analysis data from the integration service. The planned run contains all the run and analysis configuration required to start the run on the instrument. The sample sheet is also generated and stored on Clarity LIMS for reference purposes. The analysis is performed on-premise.

| **Clarity Integration**        | **Supported Run Mode**     | **Remarks** |
| ------------------------------ | -------------------------- | ----------- |
| NextSeq 1000/2000 (cloud)      | Samplesheet, hybrid, cloud |             |
| NextSeq 1000/2000 (file-based) | Samplesheet                |             |
| NovaSeq X Series (cloud)       | Samplesheet, hybrid, cloud |             |
| NovaSeq X Series (on-prem)     | Local                      |             |
| MiSeq i00 Series (cloud)       | Samplesheet, hybrid, cloud |             |
| MiSeq i00 Series (on-prem)     | Local                      |             |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/references/terminology.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.