> 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-2.md).
# Setting Determining Attribute Priorities
Priorities can be used to quickly reduce business rules to only include specific priorities when you need to meet deadlines or are only interested in testing certain items.
Priorities are set by the builder and should be based on input from testers or SMEs. In the case below, we will be setting priorities on both the \[account] currency and payment currency fields. For the currency field, USD and EUR will be priority 1, GBP and JPY will be priority 2, and CNY and SGD will be priority 3.
You can set the priority when creating a manual attribute or can set it by editing any attribute. Click on the pencil to the right of the determining attribute on the main page to open the ‘Edit Determining Attribute’ page. Scroll down to the list of values, and click the pencil to the right of each value (one at a time). The value will populate in the center pane, but will be greyed out. Type the associated priority on the ‘priority’ line, and click the 'Apply' button to set it. (Here we are applying a priority of 3 to the SGD value.) Once all desired priorities are applied, click ‘Save’ to save the priorities.
Creating priorities in the Edit Determining Attributes window
---
# 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-2.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.