Palette - Revision history

Anonymous at 10:42, 22 February 2012

2012-02-22T10:42:58Z

Anonymous at 08:50, 19 February 2012

2012-02-19T08:50:18Z

Anonymous at 16:30, 23 January 2012

2012-01-23T16:30:39Z

Anonymous at 16:30, 23 January 2012

2012-01-23T16:30:25Z

Anonymous at 16:11, 23 January 2012

2012-01-23T16:11:37Z

Anonymous: /* Palette */

2012-01-23T15:07:05Z

‎Palette

Anonymous: /* Palette */

2012-01-23T14:56:22Z

‎Palette

Anonymous at 14:41, 23 January 2012

2012-01-23T14:41:48Z

Anonymous: Replaced content with " You can choose the types of operations"

2012-01-19T09:48:52Z

Replaced content with " You can choose the types of operations"

Anonymous at 09:40, 19 January 2012

2012-01-19T09:40:59Z

@@ Line 3: / Line 3: @@
 From the Palette on the right you can choose the types of nodes.
-*[[main nodes]]
+* [[Main nodes]]
-*[[Operations ]]
+* [[Operations|Operation nodes ]]
-*[[Iterations ]]
+* [[Iterations|Iteration nodes ]]
-As seen in the [[{{VULCON}} first flow]] N nodes is done by just select and drag a node in the graphical editor for designing the flow starts. The nodes are interconnected by arrows in the graphical editor , {{VULCON}} arrows in three, and are distinguished three different colors:
+As seen in the [[{{VULCON}} first flow]] N nodes is done by just select and drag a node in the graphical editor for designing the flow starts. The nodes are interconnected by arrows, named Connection, present in the top of the Palette view.
-*Blue arrow: operating conditions if, switch.
+{{GVESB}} has configured three types of Connections. Those are:
 {{VOTE}}

← Older revision		Revision as of 08:50, 19 February 2012
Line 15:		Line 15:

	*Black arrow: identify the sequence of nodes of a flow.		*Black arrow: identify the sequence of nodes of a flow.
		+	{{VOTE}}

@@ Line 5: / Line 5: @@
 *[[main nodes]]
-*[[Operations node]]
+*[[Operations ]]
-*[[Iterations node]]
+*[[Iterations ]]
 As seen in the [[{{VULCON}} first flow]] N nodes is done by just select and drag a node in the graphical editor for designing the flow starts. The nodes are interconnected by arrows in the graphical editor , {{VULCON}} arrows in three, and are distinguished three different colors:

@@ Line 5: / Line 5: @@
 *[[main nodes]]
-*[[Operations]]
+*[[Operations node]]
-*[[Iterations]]
+*[[Iterations node]]
 As seen in the [[{{VULCON}} first flow]] N nodes is done by just select and drag a node in the graphical editor for designing the flow starts. The nodes are interconnected by arrows in the graphical editor , {{VULCON}} arrows in three, and are distinguished three different colors:

@@ Line 9: / Line 9: @@
 *[[Iterations]]
-As seen in [[{{VULCON}} first flow]] is made from N nodes. The nodes are interconnected by arrows in the graphical editor , {{VULCON}} arrows in three, and are distinguished three different colors:
+As seen in the [[{{VULCON}} first flow]] N nodes is done by just select and drag a node in the graphical editor for designing the flow starts. The nodes are interconnected by arrows in the graphical editor , {{VULCON}} arrows in three, and are distinguished three different colors:
 *Red arrow: manage the flow of exceptions.

← Older revision		Revision as of 14:41, 23 January 2012
Line 1:		Line 1:
		+	==Palette==

		+	From the Palette on the right you can choose the types of nodes.

−	~~You can choose the types of~~ [[~~operations~~]]	+	[[main nodes]]
		+
		+	[[Operations]]
		+
		+	[[Iterations]]

← Older revision		Revision as of 09:48, 19 January 2012
Line 1:		Line 1:
−	~~==Start==~~

−	~~Add img Nodo start~~
−
−	~~Represents the node of a flow started.~~
−
−	~~==Check==~~
−
−	~~Add img Nodo Check~~
−
−	Is the node where {{GVESB}} makes decisions and determines what the next node to execute. Each Check node has a basic routing mechanism that chooses the next node only of the presence or absence of errors indicated by exceptions.
−
−	~~==Wait==~~
−
−	~~inserire img~~
−
−	~~Allows you to insert delays in the execution of a stream.~~
−
−	~~==Notification==~~
−
−	~~inserire IMG~~
−
−	It allows a notification to signal on the process flow.For each 'NotificationNode' is associated with a list of notifications (Notification) that handle the type of message to send and the medium on which to write the notification.
−	~~ES: log4j, JMX~~
−	~~The order in which notifications are performed is the insertion order.~~
−	~~A notification can be described as 'critical', which is vital for the proper execution of the flow.~~
−	~~If a notification 'critical' throws an exception, the flow fails, and the exception is inserted into the buffer specified by the 'output' of NotificationNode.~~
−	~~The NotificationNode not read an input buffer, as may be specified a different one for each notification.~~
−
−	~~==ChangeGVBuffer==~~
−
−	~~inserire IMG.~~
−
−	~~It lets you make a change in the data buffer.~~
−	~~You can perform manipulations on the data buffer, set new properties or modify existing ones using scripting languages such as JavaScript or OGNL.~~
−
−	~~==SavePoint==~~
−
−	~~inserire img~~
−
−	~~DB allows you to save the state of execution of the workflow. They can also be stored business information in the form of name-value pairs.~~
−
−	~~==End==~~
−
−	~~inserire img~~
−
−	~~End the flow execution.~~

	You can choose the types of [[operations]]		You can choose the types of [[operations]]

← Older revision		Revision as of 09:40, 19 January 2012
Line 46:		Line 46:

	End the flow execution.		End the flow execution.
		+
		+	You can choose the types of [[operations]]