ELOxc is a service that provides an interface structure that contains instances. A service executes an instance. An instance provides a new structure for action trees. The action trees contain actions that are executed in sequence.

ELOxc has flexible configuration options. It offers a variety of parameters for setting the frequency and scope with which the service is processed, data granularity, and archiving. The configuration of a service is broken down into separate instances, which can run independently. Each instance contains the definition of the underlying process control settings, a catalog of available mailboxes, and any number of action trees and configuration templates. An instance is always linked to one ELO repository. Each action tree consists of a message selection based on the corresponding mailbox catalog and hierarchically arranged actions. Each action is a parameterized function, which is applied to a selected item of the corresponding action tree.

Action principle

An action always returns a binary result: success ("true") or fail ("false"). By linking the results to follow-up actions, it is possible to achieve a basic binary tree structure, which allows you to create application-specific configurations for ELOxc. The actions incorporate functions that affect the scope of the message data, the location in the repository, and the time of transfer, using and evaluating message properties in the process. You can create an action tree from any number of actions and call other action trees at any number of places. While an action tree is being processed, the buffer of all actions is constantly updated. The action tree returns a binary result for each item depending on the last completed action.

Please note: In many cases, the configuration of ELOxc is not a complete binary tree or one that contains many items, but is more like a linear sequence of actions.

The general configuration of an ELOxc service enables you to arrange the required actions in accordance with your requirements and easily manage recurring processing patterns.