> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/advanced-workflows/buttons.md). # Buttons ### Buttons {% embed url="" %} Buttons provide a faster way to add content to your report by allowing you to insert the same comment or observation multiple times with a single click. Unlike traditional dropdown fields, which typically allow only one selection, buttons can be clicked repeatedly to create multiple entries. This makes them especially useful for components that may appear several times throughout a property. Buttons become even more powerful when used with tables. For example, if a property has multiple water heaters, HVAC systems, or electrical panels, each click can create a new table entry, allowing you to document each component separately while keeping all of its styles, materials, observations, recommendations, and photos together in a single observation. #### Creating Buttons To display a field as buttons: 1. Edit the section containing the field. 2. Select the field you want to modify. 3. Under **Display Options**, enable **Display as Buttons**. 4. Save your changes. The field will now appear as one or more clickable buttons instead of a dropdown list. #### Design Considerations * An entire field is displayed as either **buttons** or a **dropdown**. Individual items within the same field cannot be mixed. * Buttons are ideal for fields where multiple entries are common. * Consider combining buttons with text replacement, observation tags, or tables to create highly efficient inspection workflows. Buttons can dramatically reduce repetitive data entry while making your report more organized and easier to complete, especially when documenting multiple instances of the same component. --- # 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.scribeware.com/advanced-workflows/buttons.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.