Page History
...
The Solution Designer is the Windows-based configuration environment where solutions are built and tested. The Runtime Engine (TServer.exe) executes solutions on any supported platform. Operator interfaces run as Rich Clients (WPF desktop), Web Clients (WebAssembly via Blazor), or Mobile Clients. The Solution Manager provides a visual launcher for selecting and starting solutions.
...
Everything in FrameworX is an object in a unified namespace. Configuration, runtime, and navigation are three views of the same data:
| Configuration Table | Runtime Namespace Path | What It Represents |
|---|---|---|
| UnsTags, row "Tank1/Level" | Tag.Tank1/Level | A process data point |
| AlarmsGroups, row "Critical" | Alarm.Group.Critical | An alarm behavior group |
| DevicesNodes, row "PLC1" | Device.Node.PLC1 | A connected field device |
| ScriptsTasks, row "Startup" | Script.Task.Startup | An automation script |
| DisplaysList, row "MainPage" | Display.MainPage | An operator screen |
When you create a row in a configuration table, it immediately becomes a runtime object accessible via its namespace path. There is no separate deployment or compilation step — the runtime reads directly from the solution database.
...
ObjectName is used by ScriptsExpressions. It binds a calculation to a namespace object. Format: full namespace path like Tag.Machine1/Level — requires the namespace prefix, no @, no .Value.
Key Columns: When using write_objects, the tables with a NAME field, only the name is mandatory, when using TagName ( AlarmsItems, HistorianHistorianTags, and DevicesPoints), or ObjectName, it is necessary to include the 2 key columns of echo tables, and defined in the table_schema.
Singleton tables (SolutionSettings, AlarmsGlobalSettings, RuntimeStartup, DisplaysClientSettings) have no key column — they contain a single configuration row. RuntimeExecutionProfiles for AI will show only the differences between Development and Production profiles, directly on the Designer UI it has more options.
...
Terminology Quick Reference
| Term | Definition |
|---|---|
| Solution | A FrameworX project stored as a .dbSLN file containing all configuration |
| Tag | A data element in the Unified Namespace — the atomic unit of real-time data |
| UserType (UDT) | A custom tag template that defines member tags and auto-updates instances |
| Point | A tag mapped to a physical device address for reading/writing field data |
| Channel | A protocol configuration defining how to communicate with a class of devices |
| Node | A specific device address within a channel |
| Display | An operator interface screen (Canvas for absolute layout, Dashboard for grid layout) |
| Symbol | A user-authored reusable graphic component with customizable appearance and behavior |
| WizardSymbol | A pre-built symbol (TANK, VALVE, PUMP, MOTOR, BLOWER) with easy customization |
| CodeBehind | C# or VB.NET code embedded in a display for event handling and custom actions |
| Layout | A screen region definition (Header, Footer, Menu, SubMenu, Content) for the running application |
| Hot Update | Applying configuration changes to a running solution without restart |
| Execution Profile | Development (unrestricted) or Production (operational restrictions) mode |
| TagProvider | An external data source that dynamically populates the UNS with tags |
| Asset() | A function for dynamic access to UNS paths, essential for TagProvider data |
| SolutionCenter | The application for selecting, launching, and managing solutions |
| SolutionCategories | Object labels applied across the solution — the MCP label marks AI-created objects. The labels each object has are visible on the Column/Property Category of the object. |
...
Related Documentation
Getting Started: [Quick Start Guide] — Build your first solution in 30 minutes
...