Union Connector

The Union connector is a reading connector that combines the records of several reading connectors.

A typical application example would be if you want to merge the data from several data sources with the same data structure into a larger "virtual" data set. For example, absences from the time management system could be combined with absences from a groupware system and thus made available as a new input data source.

When configuring the connector, which is fundamentally a "reading connector" that provides data for a synchronization, the following must be observed:

• The field names that the Union connector instance provides must be specified.
• For each input connector that is to be included in the data set of our Union connector instance, a separate connector link must be created in which our Union connector instance is the target connector.
• The connector links created above must then be linked in our Union connector configuration.

Example:

• A new Union connector configuration "Absences" is to combine absences from the time system with process instance data from the workflow engine.
• First, the desired field names must be defined in the connector configuration of our new "Absences connector". We decide on:
• userName
• fromDate
• toDate
• subject
• Now 2 connector links must be created, with our new Union connector always being the target. The first connector link is between the absences from the time system and our UnionConnector, the second connector link is between the workflow engine and our Union connector
• Now these two connector links still have to be entered in the configuration of our Union connector.
• Now a new source connector is available that combines data from the time system with data from the workflow engine.