> 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/design-considerations-and-frameworks/frameworks/application-starter-framework/popup-window-v7-3-and-lower.md).
# Popup Window (v7.3 and Lower)
In your application, you can add a popup window for focused user interaction with the application. You add a popup from the *special* menu and enter the parameter details. When your user opens the popup window, the system automatically disables the main content of the application until the popup window closes.
NOTE: This topic relates to the popup window function in LogicNets versions up to 7.3. For v7.4 and higher, see [Dialogue/Popup](/release-9/platform-documentation/form-node-parts/dialogue-popup.md).
## Popup Configuration Options
Once you have added the popup node you set the configuration parameters for the popup on the parameters tab of the node-details window.
## Editor Fields
The following table details the configuration options for the popup window.
| Field Name | Description/Use | Type/Options | Optional/Mandatory |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------------------ |
| Mode | Button: If this option is selected the system will display on the application screen a button that opens the popup window when the user clicks on it.
Launch: If this option is selected the system will launch the popup window when the logicnet is executed. For example, you can use this option in your process logicnet to launch a popup window based on certain user input.
| Button/Launch | Optional |
| Popup title | This is the text the system will show in the title bar of the popup window. | Text | Optional |
| UI net | This is the name of the logicnet that renders the UI of the popup window. | Logicnet | Optional |
| Process net | This is the name of the logicnet that processes user inputs from the popup window. | Logicnet | Optional |
| Action buttons | These are the action buttons for closing the popup window and each action button has the following parameters:
• Type: Submit/Cancel. For Submit, the system will close the popup window and reload the main and side panels.
• Value: This is the value that the system will store to the result object when the user clicks the button to close the popup window.
• Caption: This is the caption of the button to close the popup window.
| Collection | Optional |
| Result | This is the name of data object that stores the result of the popup window processes. | Data Object | Optional |
## Example
Download and import the [*Starter App Example Project*](/release-9/example-gallery/example-applications/starter-app-example-project-release-7-4-only.md) into your Designer.
---
# 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/design-considerations-and-frameworks/frameworks/application-starter-framework/popup-window-v7-3-and-lower.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.