| Anchor | ||||
|---|---|---|---|---|
|
In this article we expain how to build Message-Center-style routing inside single IWS translator.
This kind of routing allows you to route different messages to different translators based on condition derived from incoming data fields.
We will start by creating s simple workflow, with begin, translator and end shapes:
Double-click on router_translator shape, provide name.
The following screen will appear:
- Double-click on router translator to add and manage routing expressions
- Drag one or more "router's choice" element onto the worksheet. Populate expression for the router and "info" property (it will be displayed in the router translator)
For ease of mapping, you may also add source grid to the worksheet, but it is not necessary.
- Return to the router translator tab and click 'refresh' button under the router block. The picture will expand to show you newly added router's choices
- Drag two Message Translator tasks and drop to the right of each router choice, And then connect the elements:
- Translator1 and Translator2 are currently just empty shapes. You have to double-click on each and define the mapping
- By default outbound rules group incoming data. To avoid that, and have line-by-line routing instead, clear the "Enable grouping" checkbox in the router translator's worksheet propreties dialog.
Now in the publish preview screen you can see that the stream contains additional translators, and there are appropriate mapping expressions in the rsf file:
