Iterations - Revision history

Anonymous at 21:39, 18 April 2012

2012-04-18T21:39:28Z

2012-03-05T10:05:26Z

‎{{VULCON}} Configuration

2012-03-05T10:03:44Z

‎{{VULCON}} Configuration

2012-03-05T10:02:31Z

‎{{VULCON}} Configuration

2012-03-05T09:59:45Z

2012-03-05T09:33:58Z

2012-03-05T09:20:53Z

2012-03-05T09:19:48Z

2012-03-05T09:15:48Z

‎{{VULCON}} Configuration

2012-03-05T08:18:38Z

‎{{VULCON}} Configuration

@@ Line 2: / Line 2: @@
 [[File:iterationsNode.png|thumb|{{GVESB}} Iterator Nodes]]
 *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 Dequeue Node: Allows you to run a receive from a queue or a topic in an iterative manner.Using the right mouse button you can edit/add operations or InputServices OutputServices.
 *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.

@@ Line 11: / Line 11: @@
 You might insert into your workflow one of the Nodes described above by drag and drop it into the {{VULCON}} Editor View.
-When one of this node is inserted 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 selected. The following table shows this:
+When one of these nodes is inserted 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 selected. The following table shows this:
 {|class="gvtable"

@@ Line 9: / Line 9: @@
 =={{VULCON}} Configuration==
-You might insert into your workflow one of the Nodes described bellow by drag and drop it into the {{VULCON}} Editor View.
+You might insert into your workflow one of the Nodes described above by drag and drop it into the {{VULCON}} Editor View.
 When one of this node is inserted 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 selected. The following table shows this:

@@ Line 11: / Line 11: @@
 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:
+When one of this node is inserted 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 selected. The following table shows this:
 {|class="gvtable"

← Older revision		Revision as of 09:59, 5 March 2012
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}}

@@ Line 16: / Line 16: @@
 ! Iteration node !! GVIterationOperationNode Sub-element !! Description
 |-
-| Iterator Enqueue || [[#proxy-enqueue|proxy-enqueue]] || Sets a proxy to other Enqueue operation.
+| Iterator Enqueue || [[GVIteratorOperationNode#proxy-enqueue|proxy-enqueue]] || Sets a proxy to other Enqueue operation.
 |-
 | Iterator Dequeue || NONE ||
 |-
-| Iterator Call ||  [[#proxy-call|proxy-call]] || Sets a proxy to other Call operation.
+| Iterator Call ||  [[GVIteratorOperationNode#proxy-call|proxy-call]] || Sets a proxy to other Call operation.
 |-
-| Iterator CoreCall || [[#CoreCall|CoreCall]] || Invokes a {{GVESB}} [[service]].
+| Iterator CoreCall || [[GVIteratorOperationNode#CoreCall|CoreCall]] || Invokes a {{GVESB}} [[service]].
 |-
-| Iterator SubFlowCall || [[#SubFlowCall|SubFlowCall]] || Invokes a {{GVESB}} operation's [[SubFlow]].
+| Iterator SubFlowCall || [[GVIteratorOperationNode#SubFlowCall|SubFlowCall]] || Invokes a {{GVESB}} operation's [[SubFlow]].
 |}

← Older revision		Revision as of 08:18, 5 March 2012
Line 10:		Line 10:

	You might insert into your workflow one of the Nodes described bellow by drag and drop it into the {{VULCON}} Editor View.		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]].	+	When node will be insert into the editor, a new element [[GVIterationOperationNode]] 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:
		+
		+	{\|class="gvtable"
		+	! Iteration node !! GVIterationOperationNode Sub-element !! Description
		+	\|-
		+	\|
		+	\|}