Difference between revisions of "Iterations"
| Line 26: | Line 26: | ||
| Iterator SubFlowCall || [[GVIteratorOperationNode#SubFlowCall|SubFlowCall]] || Invokes a {{GVESB}} operation's [[SubFlow]]. | | Iterator SubFlowCall || [[GVIteratorOperationNode#SubFlowCall|SubFlowCall]] || Invokes a {{GVESB}} operation's [[SubFlow]]. | ||
|} | |} | ||
| + | |||
| + | {{VOTE}} | ||
Revision as of 09:59, 5 March 2012
The Iterations nodes are:
- Iterator Enqueue Node: Allows you to perform a queuing iteratively.
- Iterator Dequeue Node: Allows you to run a receive from a queue or a topic in an iterative manner.
- Iterator Call Node: Allows you to perform a synchronous iteratively.
- Iterator CoreCall Node: Allows you to make a call to another department in an iterative manner.
- Iterator SubFlowCall Node: Allows you to make a call to a SubFlow in an iterative manner.
VulCon Configuration
You might insert into your workflow one of the Nodes described bellow by drag and drop it into the VulCon Editor View.
When node will be insert into the editor, a new element GVIteratorOperationNode will appear into the element Flow (or SubFlow) of your Service Operation. This element will contain a sub-element which variates depending on the Iteration Node you select. The following table shows this:
| Iteration node | GVIterationOperationNode Sub-element | Description |
|---|---|---|
| Iterator Enqueue | proxy-enqueue | Sets a proxy to other Enqueue operation. |
| Iterator Dequeue | NONE | |
| Iterator Call | proxy-call | Sets a proxy to other Call operation. |
| Iterator CoreCall | CoreCall | Invokes a GreenVulcano® ESB service. |
| Iterator SubFlowCall | SubFlowCall | Invokes a GreenVulcano® ESB operation's SubFlow. |
{{#w4grb_rate:}} <w4grb_ratinglist latestvotes items="5" nosort/>
