Working in Multiple Browser Tabs for the Same Intelligence Hub Project
Where You Can Use Multiple Tabs:
- The Intelligence Hub runs in a browser-based configuration GUI with dedicated areas for Pipelines, Connections, troubleshooting tools, and more
- Pipelines include a Debug experience for inspection while you build
- Connections such as MQTT, OPC UA, SQL all have status or configuration pages you can open from the GUI
- The UNS Client is a built-in MQTT / Sparkplug view for live topic browsing and payload inspection
- The Event Log is available under Log for runtime and audit messages during troubleshooting
Note: HighByte does not explicitly say that Multiple Tabs is a feature. However, with the GUI being browser-based, it allows for multiple tabs. The items above are some of the features that you may find useful to keep open.
Workflow Suggestions Examples:
Use multiple browser tabs to separate build from observation as your projects become more complex and busy.
- Tab A - pipeline (edit/debug): Open your pipeline to modify stages
- Tab B - Connections (verify input or outputs): Open the specific Connection(s) to test connectivity or browse resources
- Tab C - UNS Client (observe live data): Subscribe to relevant topics or Sparkplug paths to validate structure and values
- Tab D - Event Log (audit): Keep logs visible for errors, retries, and audit entries while iterating
Why it Helps on Complex Projects:
- Parallel visibility: Edit in one tab while you watch the UNS Client and Event Log in others
- Fewer context switches: Keep Connections open for quick tests as you tweak pipeline logic
- Faster triage: Pipeline Debug + Event Log allows for faster identification and resolution of errors
Note: Because multi-tab is a best practice suggestion, treat tabs as parallel views of the same project. Make sure to always save your changes and refresh the other tab(s) so you’re looking at the current state.