Routes

A route in Alumio represents an integration of a data entity between two systems. It connects an incoming configuration and an outgoing configuration to enable the data transfer between the systems.

To create a route, you need to navigate to the Connections -> Routes section. Note that a Route first requires an Outgoing and an Incoming to have been created beforehand.

You can add Entity Transformers to a Route. These get their data from the Incoming configuration attached, and execute before the entity becomes a task. Generally, it is best-practice to put all Entity Transformers in an Incoming configuration. The exception to this is when an Incoming configuration is used for several different Routes. In that case, it might be best to filter and/or restructure the data within the Routes instead of within the Incoming.

The Route has a few configuration options:

• Realtime Processing: when this setting is on, a task that is created will immediately trigger the processing of that task by the Outgoing configuration. For routes that require as much speed as possible, this is generally the best option (i.e. an order which is pushed from system A to Alumio). However, using this setting also means that Alumio's queueing and scheduling system is bypassed. For 95% of routes, this setting should be off.
• Retry on Failure: this allows automatic retries of tasks that have failed. This is generally best-practice to enable, though there are a few exceptions.