Connect OutSystems apps to industrial data platforms that speak i3X - historians, asset models, and telemetry stores. The i3X Connector wraps the i3X v1 REST API as ready-to-use ODC Server Actions: browse namespaces, object types, and objects, read current and historical values, and receive value updates through subscriptions, with no HTTP plumbing or custom integration code.Point it at any i3X v1 server. The server URL and authentication travel with each call, so one app can talk to many servers and nothing is hard-coded in the library. Every action returns a Success flag and a normalized error you can branch on, and calls appear in ODC monitoring with distributed tracing. Try it against the public i3X demo server first, then bring your own server and credentials.Use it to build dashboards, asset explorers, monitoring and alerting apps, and back-office tools.
v1 (Release) only. The connector targets the i3X v1 wire format.
17 of 20 endpoints. The two write endpoints (PUT /objects/value and
PUT /objects/history) and the SSE stream (POST /subscriptions/stream) are not
included; live updates use the /sync poll loop instead.
Dynamic nodes are raw JSON by design. They are not strongly typed; you
deserialize them yourself when needed.
https://opensource.org/licenses/BSD-3-Clause