Remappers overview

Similar to splitters, remappers mark the beginning of a loop, that is, a portion of the workflow that is executed multiple times. The fundamental difference between a remapper and a splitter is that the remapper does not produce the items on which it loops: instead, it "pulls them out" from a previous context, which can be that of a splitter or of another remapper.

As for a splitter, the portion of the workflow that must be executed for each item must be terminated with an End Context block, and, considering also the remapper and the End Context blocks, it constitutes the context of the remapper.

A remapper only makes sense if it references a previous context and serves to process its outputs, and, like for the context of a splitter, the n outputs that a remapper can produce are confined to its context and not transmitted downstream. To "pull them out" and make use of them, it is necessary to use a reducer or another remapper.

Remappers can establish their own, new, context (example: Simple Remapper) or re-open—"continue"—a previous context (example: Foreach remapper).

As with splitter contexts, a remapper's context is recognizable in the diagram by:

• The same-colored frame contouring all of its blocks.
• The color of the internal connections, which is the same of the frame above.
• The double arrow icon halfway of the internal connections.

Workflows containing remappers can only be published in asynchronous mode.