> 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/business-rules/deleting-a-business-rule.md).
# Deleting a Business Rule
To delete a business rule, click the check box to the left of the rule and then hover to the right of the rule. Click on the trash can icon to delete the rule.
Deleting a business rule
TDO will pop up a message to confirm the deletion operation. Click on 'OK' to delete the rule or 'Cancel' to keep it.
Deletion confirmation message
Once deleted, the rule will be removed from the business rules list.
To delete two or more rules at the same time, click the blue pencil to the left of all rules you want to delete. Then click the trash can in the upper right corner of the business rules list pane. This will bring up the deletion message. Click 'OK' to delete all checked rules.
Select multiple business rules for deletion
After deleting the selected rules, the business rules page will show what is left (in this case, no rules).
Business rules page after deletion
---
# 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/business-rules/deleting-a-business-rule.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.