| 
				   | 
				
| 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]]  | 
		Revision as of 09:48, 19 January 2012