Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

Description

This unit is a Processor unit type.

A Repeater is a unit that repeats an event a certain amount of times. 

An event comes in through the in port. The event is sent through the out port the number of times specified in the properties, optionally containing an event count field.

Configuration

After dragging this unit into the Flow canvas, double-click it to access its configuration options. The following table describes the configuration options of this unit:

Tab

Field

Description

General

Name

Enter a name for the unit. It must start with a letter, and cannot contain spaces. Only letters, numbers, and underscores are allowed.

Description

Enter a description detailing the scope of the unit.

Times

The number of times input events will be repeated.

Count field name

Enter the name of an input event field containing an event order number, starting at zero, to be added to the output event (optional).

Input ports

Port

Description

in

All events enter through this port.

Output ports

Port

Description

out

Outputs events the number of times indicated in the configuration, with optional count field starting at 0.

Example

Imagine you wish to repeat an event 10 times to send to a my.app table.

You can use the Repeater unit to do so. First, we add a Tick unit to fire the request every time we need it. Then, connect it to the Repeater unit through its in input port. Finally, we can send the events to a Devo my.app table by connecting the Repeater to Devo Sink unit.

In the Repeater unit properties, set the Times field to 10 to send the event ten times.

In the Repeater unit properties, specify the my.app table in the Table name field.

After saving and starting the Flow, you must click the red button of the Tick unit to begin sending events.

📁 Download this example

You can try this flow by downloading the following JSON file and uploading it to your domain using the Import option.

  • No labels