GVNodeCheck - Revision history

G.dimaio at 15:04, 4 March 2013

2013-03-04T15:04:40Z

G.dimaio at 15:03, 4 March 2013

2013-03-04T15:03:21Z

Anonymous: /* {{GVESB}} Configuration */

2012-03-05T10:26:41Z

‎{{GVESB}} Configuration

Anonymous: /* {{GVESB}} Configuration */

2012-02-23T08:54:34Z

‎{{GVESB}} Configuration

Anonymous: Created page with "==Description== This element defines the nodes where {{GVESB}} makes decisions and determines which is the next node to execute. =={{GVESB}} Configuration== Each 'GVNodeCheck'..."

2012-02-23T07:16:21Z

Created page with "==Description== This element defines the nodes where {{GVESB}} makes decisions and determines which is the next node to execute. =={{GVESB}} Configuration== Each 'GVNodeCheck'..."

New page

==Description==

This element defines the nodes where {{GVESB}} makes decisions and determines which is the next node to execute.

=={{GVESB}} Configuration==

Each 'GVNodeCheck' has a basic routing mechanism that chooses the next node only by the presence or absence of errors reported by exceptions. In any case, you can define more sophisticated routing mechanisms defining the sub-elements 'GVRouting', allowing many opportunities for branching flows:
* BASE (without 'GVRouting'): Depending on the type of input (GVBuffer or exception) will be designated as the next node, the one expressed by the attributes 'default-id' or 'on-exception-id'.
* ADVANCED (with 'GVRouting'): Regardless of the type of input (GVBuffer or exception) will assess the conditions for routing the order they are defined. <br/> The first condition is verified the evaluation ends and the corresponding node is designated as the next node of the workflow.<br/> If neither GVRouting condition is met and is considering an exception continues from
the node specified by 'on-exception-id' otherwise continues from the node specified by 'default-id'. <br/> If 'default-id' is not configured will create an exception type it.greenvulcano.gvesb.core.GVCoreException and the node specified by 'on-exception-
id' is the next node to execute.

Routing conditions refer to conditions specified by the items 'Conditions' present on the nodes [[Flow]], [[Service]] and [[Client]] (from high to low priority).

The conditions can be redefined in several places, in case of ambiguity will be considered according to priority.

The GVNodeCheck Element is used by: Flow.

The following table shows the GVNodeCheck element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''flow-node'''.
|-
| op-type || fixed This attribute must assume the value '''check'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVNodeCheck'''.
|-
| id || required || ID of the node. Unique within the 'Flow'.
|}

Might contain the following subelements:
* Description
* [[#GVRouting|GVRouting]]

===GVRouting===

Associates a condition to a node of the workflow.

If the condition is satisfied, the workflow transfers control to the associated node.

The following table shows the GVRouting element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| condition || required || Name of the condition to be verified.
The actual meaning of the condition is specified by the elements 'Conditions' present on the nodes 'Flow', 'Service' and 'Client'.
|-
| next-node-id || required || Node to execute if the condition is verified.
|-
| point-x || optional || X position of the node in the VulCon workflows editor.
Immutable, used by {{L_VULCON}}.
|-
| point-y || optional || Y position of the node in the VulCon workflows editor.
Immutable, used by {{L_VULCON}}.
|}

Might contain the element Description.

@@ Line 3: / Line 3: @@
 This element defines the nodes where {{GVESB}} makes decisions and determines which is the next node to execute.
-=={{GVESB}} Configuration==
+=={{VULCON}}/{{GVCONSOLE}} Configuration==
 Each 'GVNodeCheck' has a basic routing mechanism that chooses the next node only by the presence or absence of errors reported by exceptions. In any case, you can define more sophisticated routing mechanisms defining the sub-elements [[#GVRouting|GVRouting]], allowing many opportunities for branching flows:

@@ Line 15: / Line 15: @@
 The conditions can be redefined in several places, in case of ambiguity will be considered according to priority.
-The GVNodeCheck Element is used by [[Flow]].
+The GVNodeCheck is a [[Flow]] element that extends [[FlowNode]]. It has the following attributes:
 {|class="gvtable"
 ! Attribute !! Type !! Description
 |-
 | op-type || fixed || This attribute must assume the value '''check'''.
 |-
 | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVNodeCheck'''.
 |}
 Might contain the following sub-elements:
 * [[#GVRouting|GVRouting]]

@@ Line 23: / Line 23: @@
 | type || fixed || This attribute must assume the value '''flow-node'''.
 |-
-| op-type || fixed This attribute must assume the value '''check'''.
+| op-type || fixed || This attribute must assume the value '''check'''.
 |-
 | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVNodeCheck'''.
@@ Line 30: / Line 30: @@
 |}
-Might contain the following subelements:
+Might contain the following sub-elements:
 * Description
 * [[#GVRouting|GVRouting]]
@@ Line 56: / Line 56: @@
 |}
-Might contain the element Description.
+Might contain the sub-element Description.

@@ Line 5: / Line 5: @@
 =={{GVESB}} Configuration==
-Each 'GVNodeCheck' has a basic routing mechanism that chooses the next node only by the presence or absence of errors reported by exceptions. In any case, you can define more sophisticated routing mechanisms defining the sub-elements 'GVRouting', allowing many opportunities for branching flows:
+Each 'GVNodeCheck' has a basic routing mechanism that chooses the next node only by the presence or absence of errors reported by exceptions. In any case, you can define more sophisticated routing mechanisms defining the sub-elements [[#GVRouting|GVRouting]], allowing many opportunities for branching flows:
-* BASE (without 'GVRouting'): Depending on the type of input (GVBuffer or exception) will be designated as the next node, the one expressed by the attributes 'default-id' or 'on-exception-id'.
+* BASE (without [[#GVRouting|GVRouting]]): Depending on the type of input ([[GVBuffer]] or exception) will be designated as the next node, the one expressed by the attributes 'default-id' or 'on-exception-id'.
-* ADVANCED (with 'GVRouting'): Regardless of the type of input (GVBuffer or exception) will assess the conditions for routing the order they are defined. <br/> The first condition is verified the evaluation ends and the corresponding node is designated as the next node of the workflow.<br/> If neither GVRouting condition is met and is considering an exception continues from
+* ADVANCED (with [[#GVRouting|GVRouting]]): Regardless of the type of input ([[GVBuffer]] or exception) will assess the conditions for routing the order they are defined. <br/> The first condition is verified the evaluation ends and the corresponding node is designated as the next node of the workflow.<br/> If neither GVRouting condition is met and is considering an exception continues from
 the node specified by 'on-exception-id' otherwise continues from the node specified by 'default-id'. <br/> If 'default-id' is not configured will create an exception type it.greenvulcano.gvesb.core.GVCoreException and the node specified by 'on-exception-
 id' is the next node to execute.
@@ Line 15: / Line 15: @@
 The conditions can be redefined in several places, in case of ambiguity will be considered according to priority.
-The GVNodeCheck Element is used by: Flow.
+The GVNodeCheck Element is used by [[Flow]].
 The following table shows the GVNodeCheck element's attributes:
@@ Line 45: / Line 45: @@
 |-
 | condition || required || Name of the condition to be verified.
-The actual meaning of the condition is specified by the elements 'Conditions' present on the nodes 'Flow', 'Service' and 'Client'.
+The actual meaning of the condition is specified by the elements 'Conditions' present on the nodes [[Flow]], [[Service]] and [[Client]].
 |-
 | next-node-id || required || Node to execute if the condition is verified.