Connecting transformation steps or job entries in Atrium Integrator Spoon


In Atrium Integrator Spoon, a hop connects one transformation step or job entry with another.

Transformation Hop

A transformation hop defines the direction of the data flow in a transformation. It is as shown in the following diagram:

Hop.jpg

Job Hop

A job hop defines the job execution order and the condition on which the next job entry is executed. It is as shown in the following diagram:

Job hop.jpg



Hop colors

Transformation hops are displayed in various colors based on the properties and state of the hop. The hops are described in the following table. 

To create a hop

You can create a hop between steps in a job or between steps in a transformation.

  1. In Atrium Integrator Spoon, open the job or transformation to which you want to add a hop.
  2. Select the first step.
  3. Perform one of the following actions:
    • Press the Shift key and draw a line to the second step.
    • Press the Ctrl key and select the second step, and then press the right mouse button and select New hop.

The steps are connected by a hop. The hop arrow indicates the direction of the data flow.

You can change the direction of the data flow by reversing the direction of the hop.

To flip a hop

Right-click a hop and select Flip direction. The direction of the hop is reversed.


To disable a hop

You can disable a hop for testing purposes.

Right-click on a hop and select Disable hop. The hop is disabled and its color changes to gray.

Note

The Disable hop command appears only when you right-click on an active hop.


To delete a hop

Right-click a hop and select Delete hop. The hop is deleted.

Specifying the condition on which a job entry is executed

You can specify the condition on which the next job entry is to be executed by specifying an evaluation mode for the hop that goes to that job entry.

To specify the evaluation mode

  1. Right-click a job hop and select Evaluation.
  2. Select one of the following commands:
    • Unconditional specifies that the next job entry must be executed regardless of the result of the originating job entry. An unconditional job hop uses the jobHop1.gif
    • Follow when result is true specifies that the next job entry is to be executed when the result of the originating job entry is true. This job hop uses the jobHop2.gif
    • Follow when result is false specifies that the next job entry is to be executed when the result of the originating job entry is false. This job hop uses the jobHop3.gif


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*