FlowMessages, the custom .NET data type used in Crosser Edge Analytics, support dynamic structures with nested objects and arrays containing basic .NET data types. Find out more in this article.

In industrial IT/OT networks, proxies inspect outbound traffic for security. Crosser ensures connectivity by routing traffic through proxies while allowing local access when needed.

Use environment variables from Nodes and Flows to dynamically add Nodename, Flowname, Flowversion and more to your payload depending on where your flow is deployed.

The Node version configured on a Flow determines the minimum version required to run a Flow.
You can change the Node version within the settings panel of the Flow Studio. After selecting a new Node version, use the "Update Module" option to update all modules to the latest version supported by the selected Node version.

With the release of our Control Center on Feb 6th we introduced a new way of configuring modules. The Interactive Wizard for Data Selection and Mapping lets you configure modules in a more intuitive way by interacting with the source or destination systems.

Crosser ensures high availability for central Nodes by deploying multiple Nodes behind a load balancer, which distributes requests and reroutes traffic if a Node fails. This setup also enables seamless updates to central Flows and Nodes without disrupting data processing.

Parameters are used to override certain module settings based on the Node the flow is running on. Explore the different approaches.

With the release of Node version 4 we will also change the implementation of the integrated MQTT Broker to the .NET native MQTT Broker. Learn more in this article.

Explore how the Crosser's Data Trigger module enables real-time monitoring of multiple data sources, allowing you to initiate actions based on specific conditions.

Understand how to combine the OPC UA Reader/Subscriber with OPC UA Browser module to address dynamic changes in OPC UA Servers.