> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/implementation/operation-specific-notes/set-input-parameters-using-flow-script.md).

# Set input parameters using flow script

Instead of defining all input parameters directly in the step, you can form input parameters in flow script and use that record as input parameters. Flow script is placed before the OData call.

This allows user to

* safely change the connector in step without having to manually add all input parameters
* allow to modify the parameters using flow script expressions
* add changed parameters without refreshing the step and/or projection.

## How

1. Obtain the record mapping from the step and copy the script to clipboard.

<figure><img src="/files/lyr4fsSOX2YjW9lOzyNM" alt=""><figcaption></figcaption></figure>

2. Paste it to flow script step before the operation where it is used. Add necessary values: flow variables (example name), functions or static values.&#x20;

<figure><img src="/files/iYxTg6O2nuViHcAKfaAl" alt=""><figcaption></figcaption></figure>

3. Change to new record instead of the default "Custom Record"

<figure><img src="/files/Mj3fJGcygGOKPj0y3aHJ" alt=""><figcaption></figcaption></figure>

Same record can be used in every step with the same operation.


---

# 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.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/implementation/operation-specific-notes/set-input-parameters-using-flow-script.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.