App Change Router
  • 21 Jan 2022
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

App Change Router

  • Dark
    Light
  • PDF

Article summary

There is one App Change Router Node that is created for your Tenant when you create your Tenant.

Your App Change Router Node is automatically connected to your Tenant's Change Emitter Node. You cannot delete this Edge.

Changes that affect Internal Nodes are automatically propogated by EchoStream, applying those changes to the affected Node in near-real time.

However, External Nodes are not automatically updated as the code and processing environment for those Nodes is not controlled by EchoStream and is not in the EchoStream Cloud. The App Change Router Node bridges this gap, delivering changes relevant to a particular External Node to an App Change Receiver Node running within the External Node's App.

This allows your External App implementation to receive change events via echo.change messages and perform whatever reconfiguration of the affect External Node(s) is required.

To enable this, simply create an Edge between the App Change Router Node and your App's App Change Receiver Node. The App Change Router Node will take it from there, routing any relevant echo.change received to your App.

NOTE - Managed Apps automatically have this Edge created for them and you cannot delete it. This is the mechanism that Managed Apps use to respond dynamically to configuration changes that affect them.


What's Next