Conditions - Revision history

G.dimaio at 10:30, 2 January 2015

2015-01-02T10:30:10Z

Anonymous: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-23T12:39:55Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

Anonymous at 12:38, 23 February 2012

2012-02-23T12:38:33Z

Anonymous: Created page with "==Description== =={{VULCON}} / {{GVCONSOLE}} Configuration== The element ''Conditions'' defines the conditions that allow to activate the mechanisms for routing {{GVESB}} workf..."

2012-01-27T15:46:51Z

Created page with "==Description== =={{VULCON}} / {{GVCONSOLE}} Configuration== The element ''Conditions'' defines the conditions that allow to activate the mechanisms for routing {{GVESB}} workf..."

New page

==Description==

=={{VULCON}} / {{GVCONSOLE}} Configuration==

The element ''Conditions'' defines the conditions that allow to activate the mechanisms for routing {{GVESB}} workflows.

The conditions are used in items [[GVRouting]] and [[GVNodeCheck]].

The conditions can be defined depending on the contents of GVBuffer field or according to the exceptions that may occur during the execution of workflows. Can be used in different parts of the configuration.

The following list shows all the elements that can have a sub-element ''Conditions'':
* Service: The element ''Conditions'' of [[Service]] defines all the conditions that apply to routing of all workflows instantiated in the service, for all clients of the service.
* Client: The element ''Conditions'' of [[Client]] defines all the conditions that apply to routing of all workflows instantiated in the service's client
* Flow: The element ''Conditions'' of [[Flow]] defines all the conditions that apply to routing of the single workflow defined in the 'Flow' element.

The above list is sorted according to a growing priority assessment: the same condition can be defined in several different places.
In case of multiple definitions, the definition with the highest priority is used.

@@ Line 11: / Line 11: @@
 The following list shows all the elements that can have a sub-element ''Conditions'':
-* [[Service]]: The element ''Conditions'' of [[Service]] defines all the conditions that apply to routing of all workflows instantiated in the service, for all clients of the service.
+* [[Service]]: defines all the conditions that apply to routing of all workflows instantiated in the service's Operations.
-* [[Client]]: The element ''Conditions'' of [[Client]] defines all the conditions that apply to routing of all workflows instantiated in the service's client
+* [[Operation]]: defines all the conditions that apply to routing of all workflows instantiated in the service's Operation and SubFlow.
-* [[Flow]]: The element ''Conditions'' of [[Flow]] defines all the conditions that apply to routing of the single workflow defined in the 'Flow' element.
+* [[Flow]]: defines all the conditions that apply to routing of the single workflow defined in the Flow element.
 The above list is sorted according to a growing priority assessment. The same condition can be defined in several different places.
@@ Line 22: / Line 23: @@
 * [[GVBufferCondition]]
 * [[ExceptionCondition]]
-* [[JavaScriptCondition]]
+* [[JavaScriptCondition]] '''REMOVED in v3.5'''

@@ Line 8: / Line 8: @@
 Conditions is used in items [[GVRouting]] and [[GVNodeCheck]].
-The conditions can be defined depending on the contents of [[GVBuffer]] field or according to the exceptions that may occur during the execution of workflows. Can be used in different parts of the configuration.
+The conditions can be defined depending on the [[GVBuffer]] field content or according to the exceptions that may occur during the execution of workflows. Can be used in different parts of the configuration.
 The following list shows all the elements that can have a sub-element ''Conditions'':
@@ Line 15: / Line 15: @@
 * [[Flow]]: The element ''Conditions'' of [[Flow]] defines all the conditions that apply to routing of the single workflow defined in the 'Flow' element.
-The above list is sorted according to a growing priority assessment: the same condition can be defined in several different places.
+The above list is sorted according to a growing priority assessment. The same condition can be defined in several different places.
 In case of multiple definitions, the definition with the highest priority is used.