COA and dataflows 🚀

As explained on the Phases and contracts page, there are three types of contracts: input, mediation, and output.

The ordered sequence of contracts that collectively process data is called a chain of contracts. It can begin with an input contract to acquire data, continue with a mediation contract to transform or enrich it, and conclude with an output contract to deliver or make the processed data available.

A Dataflow Instance represents the execution of a chain of contracts, triggered when a new file arrives in Data Mover through an input contract - or through a connection contract if Data Mover acts as a server.

The contracts in the chain share a Dataflow Instance Context (DFIC), which is the set of information of the dataflow instance. Data Mover creates the DFIC when the dataflow instance starts.

It contains essential information for the dataflow instance, including:

• the unique identifier of the dataflow instance (DFIID)

• system attributes (set by Data Mover) and user attributes (set by the user)

• additional information (originals) about the file and the dataflow

It is accessible during all input, mediation, and output phases.

Refer to the Dataflow Instance Context (DFIC) page for details.