Difference between revisions of "Iterations"

From GreenVulcano Wiki
Jump to: navigation, search
Line 6: Line 6:
 
*Iterator CoreCall Node: Allows you to make a call to another department in an iterative manner.
 
*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.
 
*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 GVIterationOperationNode will appear into the element [[Flow]] (or [[SubFlow]]) of your Service [[Operation]].

Revision as of 17:19, 2 March 2012

The Iterations nodes are:

iterationsNode
  • 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 GVIterationOperationNode will appear into the element Flow (or SubFlow) of your Service Operation.