> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/tdo-project-builder-user-guide/determining-attributes/page-1/numeric-range-attribute.md).

# Numeric Range Attribute

To manually create a determining attribute, click the plus (+) sign in the lower right corner of the determining attributes screen. This will open the ‘Create Determining Attribute’ window.

First, give the attribute a name.  This one is called ‘pmt\_amt’ as it represents a randomly selected payment amount.  In the use case we are building, there are three different payment ranges we will be testing – under $250, $250 - $2,500, and $2,500 – 25,000.

In the ‘Type’ section of the upper pane, select ‘Range’.  Since this is a numeric field, select ‘Number’ from the ‘Data Type’ drop down menu.

In the center pane, there are fields for ‘min value’ and ‘max value’.  Enter the values for the first range and click the plus (+) sign to the right to add that to the values list.  In the example below, the first set of values has been added and the second set is entered and ready to add.

<figure><img src="/files/BjTMpFJNjglJkAjs3yme" alt=""><figcaption><p>Create Determining Attribure window - adding a numeric range attribute</p></figcaption></figure>

After adding all of your value ranges, click the ‘Save’ button in the top pane to save the determining attribute.


---

# 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.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/tdo-project-builder-user-guide/determining-attributes/page-1/numeric-range-attribute.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.