Page History
Comprehensive product knowledge, for AI integration builders and advanced users.
Platform | Installation | Solution | Modules | Controls | Code | Troubleshooting
...
This page provides a comprehensive view of the FrameworX platform architecture, covering every module, data model, syntax rule, and integration pattern. It is designed for AI assistants working with FrameworX MCP services, system integrators building complex solutions, and advanced users who want a single-page understanding of how all platform components connect.
For getting started, see [Quick Start Guide]. For module-specific tutorials, see [BUILD section]. This page is the architectural map — not a tutorial.
This page provides a comprehensive view of the FrameworX platform architecture, covering every module, data model, syntax rule, and integration pattern. It is designed for AI assistants working with FrameworX MCP services, system integrators building complex solutions, and advanced users who want a single-page understanding of how all platform components connect.
For getting started, see [Quick Start Guide]. For module-specific tutorials, see [BUILD section]. This page is the architectural map — not a tutorial.
...
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 Name field , require only the name is mandatory, when . Tables 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.or ObjectName require both key columns to uniquely identify an object:
| Table | Key 1 | Key 2 | Example JSON |
|---|---|---|---|
| AlarmsItems | TagName | Condition | {"TagName": "Tank1/Level", "Condition": "1 (Hi)"} |
| DevicesPoints | TagName | Node | {"TagName": "Tank1/Level", "Node": "PLC1"} |
| HistorianHistorianTags | TagName | HistorianTable | {"TagName": "Tank1/Level", "HistorianTable": "Table1"} |
| ScriptsExpressions | ObjectName | Expression | {"ObjectName": "Tag.Tank1/Level", "Expression": "Tag.Input1 + Tag.Input2"} |
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.
...