Outgoing

An outgoing configuration in Alumio is a setup that defines how data should be sent to an external system. Like an Incoming configuration, it has a technical component that is utilized for the action itself: the Publisher. Like Subscribers, there are many different Publishers.

An Outgoing configuration is the process that handles the execution of a Task. The 'input data' of an Outgoing therefore, is the Entity Data from the task.

The execution order of an Outgoing configuration is reversed from an Incoming configuration: first the Entity Transformers will execute, then the Publisher.

The use of a Publisher is not actually required, since there is a 'No Action Publisher'. Quite often you'll use the No Action Publisher, because there is an inherent issue with the Publisher model: the "primary action" taken by the Outgoing configuration (i.e. the saving of a Product) is often not the last action you'll need to take. Often it is necessary to, for example, save the resulting dataset into a Storage. The Publisher model however, does not allow this. Therefore, many Outgoing configurations will have a 'No Action Publisher', and all actions taken will be within the Entity Transformers.