> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/connected-analytics/project/p-flow/f-pipelines/json-based-input-forms.md).

# JSON-Based input forms

### Introduction

Pipelines defined using the "Code" mode require an XML or JSON-based input form to define the fields shown on the launch view in the user interface (UI).

To create a JSON-based Nextflow (or CWL) pipeline, go to **Projects > your\_project > Flow > Pipelines > +Create > Nextflow (or CWL) > JSON-based**.

The files listed here, located on the inputform files tab, work together for evaluating and presenting JSON-based input.

* [**inputForm.json**](/connected-analytics/project/p-flow/f-pipelines/json-based-input-forms/inputform-json.md) contains the actual input form which is rendered when starting the pipeline run.
* [**onRender.js**](/connected-analytics/project/p-flow/f-pipelines/json-based-input-forms/onrender.js.md) is triggered when a value is changed.
* [**onSubmit.js**](/connected-analytics/project/p-flow/f-pipelines/json-based-input-forms/onsubmit.js.md) is triggered when starting a pipeline via the GUI or API.
* [**onFinish.js**](/connected-analytics/project/p-flow/f-pipelines/json-based-input-forms/onfinished.js.md) (optional, not automatically created) is triggered once the pipeline analysis has been completed

Use **+ Create** to add additional files and **Simulate** to test your inputForms.

Scripting execution supports crossfield validation of the values, hiding fields, making them required, .... based on value changes.


---

# 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://help.connected.illumina.com/connected-analytics/project/p-flow/f-pipelines/json-based-input-forms.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.