> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-nodes/tab-control.md).

# Tab Control

## Description

The tab control allows for the repetition of a set of observation questions where the user can add and switch between each set using tabs.

## Use

It is best to use tab control to present and edit larger datasets efficiently on screen. The system presents each set of answers on a tab and the user can switch between tabs, add new tabs, and remove/delete existing tabs in creating the observation data set. For example, an application that asks the same set of questions about office locations where the number of locations can vary (e.g. London, Paris, New York) can use tab control so the user creates the named tabs and provides inputs for each location.

## Editor Fields

| Tab        | Field Name             | Description                                                                                                                                                                                            | Type/Options | Optional/Mandatory |
| ---------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ------------------ |
| Call       | Logicnet to call       | This is the name of the logicnet the system will call when the tab control renders its content.                                                                                                        | Text         | Mandatory          |
| Call       | Logicnet ID            | This field is not editable. The system will display the id of the selected logicnet.                                                                                                                   | Number       | Mandatory          |
| Call       | Context path           | This is the name of the collection view. Note: The collection name must be unique for the tab control.                                                                                                 | Data Object  | Optional           |
| Call       | Collection             |                                                                                                                                                                                                        | Text         | Mandatory          |
| Parameters | Source                 | This is the name of the actual collection of items to be displayed by the tab control.                                                                                                                 | Text         | Mandatory          |
| Parameters | Tab-index              | This is the index of the selected tab by default.                                                                                                                                                      | Number       | Optional           |
| Parameters | Number of visible tabs | <p>This is the number of tabs at a time the system will display within the tab control. The default value is 5.<br>If there are multiple tabs, you can navigation buttons can used for navigation.</p> | Number       | Mandatory          |
| Parameters | Caption                | This is the item in the collection the system displays as the caption on the tab.                                                                                                                      | Text         | Mandatory          |
| Parameters | Add/remove tab         | This option allows you to display buttons to add or remove tabs. These buttons allow users to add or remove tabs. The default value is yes.                                                            | Yes \| No    | Mandatory          |
| Parameters | Add navigation         | This options allows you to display navigation buttons that allow the user to navigate to the next or previous tabs. The default value is yes.                                                          | Yes \| No    | Mandatory          |

## Configuration Options

Tab control includes multiple configuration options:

* Place multiple tab controls on a single page.
* Link multiple tab controls together: - Tab Index: The navigation for both tab controls is synchronized. - Source: Both tab controls look and write to the same collection of data items.
* Nest tab controls within tab controls or other controls.

## Example

Please download and import the following [example project](/release-9/example-gallery/example-projects-for-parts/tab-control-example-project.md) in your workspace.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-nodes/tab-control.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.