> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/studio/ui-elements/button.md).

# button

A web page button is a type of hyperlink that can be clicked on to go to a new page or site. Web page buttons are often used to highlight important information on a website, such as contact information, navigation links, and other items that are frequently accessed.

Web page button is a graphical control element that is used to trigger a specific action on the web page.

## Automation

In QATTS, at the time of execution it automatically scrolls to the element irrespective of top or bottom of the page and clicks on the element.

There were some possible ways in the recent emerging web technologies where a click will not happen. In this kind of scenarios also QATTS has a rich property library where all the problems has a pre-defined solutions. Refer to link. [Properties Library](/studio/ui-elements/properties-library.md)

Let's also see some questions and exceptions from communities. [Trouble Shoot](/studio/ui-elements/trouble-shoot.md)


---

# 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.qatts.com/studio/ui-elements/button.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.