Development and test

For most Processors, the "success" and "failure" connection options are available by default, which are executed depending on the success or failure of the process.

The gray arrow represents the default connection, which ultimately contains all connection types. An additional window opens for the connection, in which the specific type of connection can be selected.
Furthermore, certain Processors have additional connection types that can be used for specific results or events.

In addition, some Processors have the option of using dynamic properties to create your own connection types.

To improve clarity, the displayed edges of the connections are color-coded or described in the case of dynamic properties or specific events.

When already connected elements are moved, the links are retained and dynamically adapt to the repositioning.

To create a simple flow, see 5-minute tutorial.

The created connections can also be visually changed and bent in order to achieve a better overview in the data flow. If the edges are moved in edit mode, points appear on the edge that can be used for shaping.

Changes that have been made can be reset via the context menu.

Processors or flows can be executed in different ways, individually or in the entire Process Group.
The States of Processors can be adjusted via the context menu (by right-clicking on the element) and thus started or stopped.

If, on the other hand, the context menu is called up on an empty area and the status is changed, this action applies to all Processors in the current and all subordinate Process Groups. The configuration of the execution, such as the frequency of execution, takes place at Configuration area. While Processors are in the RUNNING state, this configuration is taken into account. This state is activated by selecting the Start command. If, on the other hand, the context menu Run Once is used to execute the Processor, the Processor is only executed once.

All previous executions can be stored in an Event table

The Success Relation is a connection that is available to all Processors. FlowFiles are always forwarded to the Success Relation if processing in the Processor was successful.

The Success Relation can be recognized in the Diagram by the green color, which is not used by any other relation.

The Failure Relation, which is available as an option for most Processors, is often the first step for appropriate error handling. FlowFiles are always forwarded to this relation if an error has occurred during processing within the Processor. This means that any errors that occur can be easily intercepted in order to react appropriately in a designated branch by connecting additional Processors. The success relation can be identified in the Diagram by the red color, which is not used by any other relation.

The first endpoints are often Funnels to indicate that further processing steps should be added at the corresponding point. This also helps users to detect errors by making the FlowFiles visible on the failure edge.

FlowFiles can be analyzed at this point to identify the cause of the error. For this purpose, the Event table provides further information on the Processor’s faulty event.

For appropriate error handling, however, it is important not only to collect the FlowFiles of an error in a Funnels, but also to process them in further steps in order to address existing errors appropriately.

It is also possible to analyze generated errors with the Metro Processors and bundle the error handling.

For different Processor types, there are other relation types in addition to the Failure or Success relations.

With the InvokeHttp Processor, there are four further relations that can be used. These include Retry, Response, Original and No Retry.

In the case of the Duplicate Processor, there are three further relations that belong specifically to this Processor and replace the Success relation.

Data packets that are transmitted via the resulting edges are referred to as FlowFiles. FlowFiles are displayed on the created edge itself in the Diagram and can also be viewed by clicking on the edge in the Processor’s queue.

FlowFiles have content and metadata, which are referred to as attributes in IGUASU. Both the content and the attributes can be used for routing or for transmitting information to other Processors or external systems.