> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/button.md).
# Button
## Description
The button part allows you to insert a button on a screen so your application users can click the button and step a logicnet forward with a configured value.
## Use
The button part steps a logicnet forward when your application user clicks it. You define the data object associated with a button when you create a logicnet, and when your application user clicks the button the associated data object can be used in the decision tree; for example, to go to a particular page or trigger a process.
## Editor Fields
| Tab | Field Name | Description/Use | Type/Options | Optional/Mandatory |
| -------- | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ------------------ |
| Basic | Caption | This is the text the system will display on the button. | Text | Mandatory |
| Basic | Data object | This is the name of the data object in which the value will be stored when a user clicks the button. | Data object | Mandatory |
| Basic | Value | This indicates the value assigned to the data object when the user clicks the button. | Text | Mandatory |
| Basic | Data object 2 | It is possible to store a second value to a data object when a user clicks a button. A practical example can be to store the name of the "action" associated with the button to the first data object and then the "id" of the item to which the action must be applied, to the second data object.
This is the name of the second data object in which the second value will be stored when a user clicks the button.
| Data object | Optional |
| Basic | Value 2 | This indicates the value assigned to the second data object when the user clicks the button. | Text | Optional |
| Basic | Onclick interpolated-handler | This field contains JavaScript the system will execute when a user clicks the button. The system interpolates the provided value with the context, so it can contain $(...). | Text | Optional |
| Basic | Onclick-handler | This field contains JavaScript the system executes when a user clicks the button. The provided value is NOT interpolated with the context. This parameter is only applied when the Onclick interpolated-handler parameter is left empty. | Text | Optional |
| Basic | Image | Users can associate an image with a button and the user will see the image as a selectable icon/button. Click the **...** button on the right side of the image input box to navigate to and select from the resources/images folder of the project. When displayed, the button contains the entered Caption/Value. | Image | Optional |
| Basic | Speech command | This is the speech command the user must say to click the button when speech recognition functionality is enabled. | Text | Optional |
| Basic | Type | The button part allows for the following action types:
- button (form-submit): Show the button as a regular button that triggers an auto-submit when a user presses ENTER on a keyboard.
- button (custom-submit): Show the button as a regular button that does not trigger an auto-submit when a user presses ENTER on a keyboard and does not triggers submit when a user clicks the button. The onclick behavior can be configured through the onclick-parameter.
- button (click-submit): Show the button as a regular button that does not trigger an auto-submit when a user presses ENTER on a keyboard but triggers submit when a user clicks the button.
- text: Show the button as text with a hyperlink.
| Options | Optional |
| Basic | Data object type | This indicates whether the data object of the button is a number or text. | Options | Optional |
| Basic | ShortCut Key | This ShortCut Key is a single character that can be used to activate the button by using the keyboard:
- Internet Explorer: ALT+key
- Chrome: ALT+key
- Safari: ALT+key
- Opera: ALT+key (SHIFT+ESC+key for <= v12.1)
- FireFox: ALT+SHIFT+key
- Mac: CONTROL+ALT+key
For example a save-like button, specify 'S' to allow ALT+S to trigger the save-like button.
| Text | Optional |
| Style | CSS class | You can assign a CSS class to a button so all buttons in the application with the same class can be styled to display the same way. | Text or data object | Optional |
| Style | Disable input | Check this box to disable the button and prevent the user from clicking.
For conditional behavior use the Disable input expression field on the ADVANCED tab
| Checkbox | Optional |
| Advanced | Disable input expression | Use this to disable the input (prevents the user from editing/changing the selected option) based on the value of another variable by entering $(...) here. Otherwise this will reflect the "Disable Input" checkbox setting in the STYLE tab (1 for disabled, 0 for enabled).
See Setting Conditions - Data Validation article for more information on the syntax for the disable expression.
| Text | Optional |
## Example
For several examples of how to use the button part, download and import the following [sample project](/release-9/example-gallery/example-projects-for-parts/button-example-project.md) in your workspace.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/button.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.