> 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/manual-attribute-creation.md).
# Manual Attribute Creation
If the determining attribute cannot be sourced from an existing data file (i.e., for new functionality) you will need to create the attributes manually.
Click the plus (+) sign in the lower right corner of the window to open the ‘Create Determining Attribute’ pane.
This attribute is called ‘channel’ and will be used to designate the source of a payment. The type is ‘Value’ (since each value is unique) and the data type for this attribute is ‘String’.
Since we are creating a ‘Value’ type attribute, there is only one field to complete for each value. We are using the values of ‘MOBILE’, ‘ONLINE’, and ‘BRANCH’ here to indicate the source (channel) for incoming or outgoing payments in this use case.
As with range creation, once the attribute values are populated, click on the ‘Save’ button to save the attribute to your list of determining attributes.
Create Determining Attribute window - create a new 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/manual-attribute-creation.md?ask=&goal=
```
`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.