Understanding the End App
The End App is the final, runtime version of your application in Operations Hub. It represents how the App appears and functions at runtime.
It is the version users interact with after you have designed the App. When you preview in Operations Hub, the End App reflects your configured widgets, data bindings, logic, and layout in a production-ready format.
The End App is how operators, analysts, or end users interact with the application you have built. The End App runs in a secure, optimized runtime environment and reflects real-time data through active bindings to data sources. It lets you test your logic, data flow, and responsiveness as it would behave in production.
Operations Hub currently supports two versions of the End App, depending on how and where the App was launched from.
| End App (New) | End App (Classic) |
|---|---|
| Used by default in the latest Operations Hub via Configuration Hub. | Used for applications that were built or are still maintained in the Classic interface. |
| Launched directly from the current interface. | Launches automatically when opened via Classic. |
| Reflects the latest runtime container. | Runs in the older runtime environment. |
| Optimized for performance and responsiveness. | Requires a URL workaround to access if launching outside of Classic. |
Accessing the Old End App (Classic)
By default, Apps created in the new Operations Hub layout open in the new End App. If needed, you can load them in the old End App by manually adjusting the URL as described below.
Take your current URL and replace everything after /run/ as shown
here:
| What You Have (New End App) | What You Change It To (Old End App) |
|---|---|
https://your
server/run/v2/app-name/your app
name/page-name/your page name
|
https://your
server/run/?app_name=your app
name&page_name=your page
name&app_version=v1 |
The format switches to a query string, which tells Operations Hub to load the Classic End App.