Chaining - Revision history

Carfey at 17:49, 1 July 2016

2016-07-01T17:49:29Z

← Older revision		Revision as of 17:49, 1 July 2016
Line 25:		Line 25:

	=Chaining Results=		=Chaining Results=
	All chaining evaluations are stored. If chaining is triggered, or if it fails based on a conditional evaluation, the [[Admin Job Activity ~~4.0~~\|job activity]] view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or source completion time was outside the constraints of a provided chaining schedule, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.		All chaining evaluations are stored. If chaining is triggered, or if it fails based on a conditional evaluation, the [[Admin Job Activity\|job activity]] view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or source completion time was outside the constraints of a provided chaining schedule, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.

Carfey at 17:06, 1 July 2016

2016-07-01T17:06:30Z

← Older revision		Revision as of 17:06, 1 July 2016
Line 1:		Line 1:
	Obsidian supports dynamic job chaining between two jobs. All chaining configuration is managed in the [[Admin Job Chains ~~4.0~~\|job chains]] portion of the admin web application.		Obsidian supports dynamic job chaining between two jobs. All chaining configuration is managed in the [[Admin Job Chains\|job chains]] portion of the admin web application.

	Chaining can be triggered simply by the state of the queued job, or as of version 1.4, conditionally, based on the saved results of a successfully completed job.		Chaining can be triggered simply by the state of the queued job, or as of version 1.4, conditionally, based on the saved results of a successfully completed job.

Carfey: /* Conditional Chaining */

2016-07-01T16:28:59Z

Conditional Chaining

← Older revision		Revision as of 16:28, 1 July 2016
Line 9:		Line 9:
	=Conditional Chaining=		=Conditional Chaining=

	Release 1.4 introduced conditional chaining. This feature allows for jobs to be triggered when a successfully completed source job saves [[Implementing_Jobs#Job_Results\|~~Job Results~~]] which match a set of defined conditions. When setting up the conditional evaluations, you specify one or more variable evaluations that must be matched to cause the chain to fire. A condition is comprised of the variable name, an operator, and one or more values		Release 1.4 introduced conditional chaining. This feature allows for jobs to be triggered when a successfully completed source job saves [[Implementing_Jobs#Job_Results\|job results]] which match a set of defined conditions. When setting up the conditional evaluations, you specify one or more variable evaluations that must be matched to cause the chain to fire. A condition is comprised of the variable name, an operator, and one or more values

	For numeric operators, your conditions are coerced to the numeric value types that your source job saves (e.g. integer, etc.).		For numeric operators, your conditions are coerced to the numeric value types that your source job saves (e.g. integer, etc.).

Carfey at 16:28, 1 July 2016

2016-07-01T16:28:43Z

← Older revision		Revision as of 16:28, 1 July 2016
Line 1:		Line 1:
	Obsidian supports dynamic job chaining between two jobs. All chaining configuration is managed in the [[Job Chains]] portion of the admin web application.		Obsidian supports dynamic job chaining between two jobs. All chaining configuration is managed in the [[Admin Job Chains 4.0\|job chains]] portion of the admin web application.

	Chaining can be triggered simply by the state of the queued job, or as of version 1.4, conditionally, based on the saved results of a successfully completed job.		Chaining can be triggered simply by the state of the queued job, or as of version 1.4, conditionally, based on the saved results of a successfully completed job.

Carfey: /* Chaining Results */

2016-07-01T16:25:39Z

Chaining Results

← Older revision		Revision as of 16:25, 1 July 2016
Line 25:		Line 25:

	=Chaining Results=		=Chaining Results=
	All chaining evaluations are stored. If chaining is triggered, or if it fails based on a conditional evaluation, the [[Job Activity 4.0\|job activity]] view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or source completion time was outside the constraints of a provided chaining schedule, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.		All chaining evaluations are stored. If chaining is triggered, or if it fails based on a conditional evaluation, the [[Admin Job Activity 4.0\|job activity]] view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or source completion time was outside the constraints of a provided chaining schedule, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.

Carfey: /* Chaining Results */

2016-07-01T16:24:40Z

Chaining Results

← Older revision		Revision as of 16:24, 1 July 2016
Line 25:		Line 25:

	=Chaining Results=		=Chaining Results=
	All chaining evaluations are stored. If chaining is triggered, or if it fails based on a conditional evaluation, the [[Job ~~History~~]] view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or source completion time was outside the constraints of a provided chaining schedule, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.		All chaining evaluations are stored. If chaining is triggered, or if it fails based on a conditional evaluation, the [[Job Activity 4.0\|job activity]] view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or source completion time was outside the constraints of a provided chaining schedule, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.

Carfey: /* Conditional Chaining */

2016-06-09T02:35:10Z

Conditional Chaining

← Older revision		Revision as of 02:35, 9 June 2016
Line 13:		Line 13:
	For numeric operators, your conditions are coerced to the numeric value types that your source job saves (e.g. integer, etc.).		For numeric operators, your conditions are coerced to the numeric value types that your source job saves (e.g. integer, etc.).

	'''Note:''' All conditions must be met for the chain to be successfully ~~trigger~~ (i.e. they are ANDed together). Additionally, operators match if ''any'' saved value matches the operator. This is important to remember if a job saves more than one value under the same variable name.		'''Note:''' All conditions must be met for the chain to be successfully triggered (i.e. they are ANDed together). Additionally, operators match if ''any'' saved value matches the operator. This is important to remember if a job saves more than one value under the same variable name.

	The supported operators are:		The supported operators are:

Carfey: /* Conditional Chaining */

2016-06-09T02:34:32Z

Conditional Chaining

← Older revision		Revision as of 02:34, 9 June 2016
Line 9:		Line 9:
	=Conditional Chaining=		=Conditional Chaining=

	Release 1.4 introduced conditional chaining. This feature allows for jobs to be triggered when a successfully completed source job saves [[Implementing_Jobs#Job_Results\|Job Results]] which match a set of defined conditions. When setting up the conditional evaluations, you specify one or more variable evaluations that must be ~~match~~ to cause the chain to fire. A condition is comprised of the variable name, an operator, and one or more values		Release 1.4 introduced conditional chaining. This feature allows for jobs to be triggered when a successfully completed source job saves [[Implementing_Jobs#Job_Results\|Job Results]] which match a set of defined conditions. When setting up the conditional evaluations, you specify one or more variable evaluations that must be matched to cause the chain to fire. A condition is comprised of the variable name, an operator, and one or more values

	For numeric operators, your conditions are coerced to the numeric value types that your source job saves (e.g. integer, etc.).		For numeric operators, your conditions are coerced to the numeric value types that your source job saves (e.g. integer, etc.).

Carfey at 03:30, 7 November 2013

2013-11-07T03:30:37Z

← Older revision		Revision as of 03:30, 7 November 2013
Line 23:		Line 23:
	* '''Regexp''' - Regular expression match based on Java's Pattern class.		* '''Regexp''' - Regular expression match based on Java's Pattern class.
	* '''Less Than/Less Than Or Equal/Greater Than/Greater Than Or Equal''' - Numeric only: values are coerced to an integer or decimal value.		* '''Less Than/Less Than Or Equal/Greater Than/Greater Than Or Equal''' - Numeric only: values are coerced to an integer or decimal value.


	=Chaining Results=		=Chaining Results=
	All chaining evaluations are stored. If chaining is triggered, or if it fails based on a conditional evaluation, the [[Job History]] view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or source completion time was outside the constraints of a provided chaining schedule, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.		All chaining evaluations are stored. If chaining is triggered, or if it fails based on a conditional evaluation, the [[Job History]] view shows which jobs a source job triggered and also which job triggered a chained job. When chaining misses because the source state didn't match any of those configured, target job is in an unchainable state, chaining configuration is disabled or source completion time was outside the constraints of a provided chaining schedule, a detail record with state Chain Skipped will still be available for review with the detail of why chaining was not triggered.

Carfey at 19:25, 29 October 2012

2012-10-29T19:25:41Z

← Older revision		Revision as of 19:25, 29 October 2012
Line 1:		Line 1:
	Obsidian supports dynamic job chaining between two jobs. All chaining configuration is managed in the [[Job Chains]] portion of the admin web application.		Obsidian supports dynamic job chaining between two jobs. All chaining configuration is managed in the [[Job Chains]] portion of the admin web application.

	Chaining can be triggered simply by the state of the queued job, or as of version 1.4, conditionally, based on the saved results of a completed job.		Chaining can be triggered simply by the state of the queued job, or as of version 1.4, conditionally, based on the saved results of a successfully completed job.

	A job can be chained to any other job. By default, chaining between two jobs will trigger when the source job either completes or fails, but any source termination state can be selected to trigger the chain. Chain configurations can be disabled and re-enabled at any time. Chaining can also be constrained to a schedule, using a standard cron schedule.		A job can be chained to any other job. By default, chaining between two jobs will trigger when the source job either completes or fails, but any source termination state can be selected to trigger the chain. Chain configurations can be disabled and re-enabled at any time. Chaining can also be constrained to a schedule, using a standard cron schedule.
Line 9:		Line 9:
	=Conditional Chaining=		=Conditional Chaining=

	Release 1.4 introduced conditional chaining. This feature allows for jobs to be triggered when ~~the~~ source job saves [[Implementing_Jobs#Job_Results\|Job Results]] which match a set of defined conditions. When setting up the conditional evaluations, you specify one or more variable evaluations that must be match to cause the chain to fire. A condition is comprised of the variable name, an operator, and one or more values		Release 1.4 introduced conditional chaining. This feature allows for jobs to be triggered when a successfully completed source job saves [[Implementing_Jobs#Job_Results\|Job Results]] which match a set of defined conditions. When setting up the conditional evaluations, you specify one or more variable evaluations that must be match to cause the chain to fire. A condition is comprised of the variable name, an operator, and one or more values

	For numeric operators, your conditions are coerced to the numeric value types that your source job saves (e.g. integer, etc.).		For numeric operators, your conditions are coerced to the numeric value types that your source job saves (e.g. integer, etc.).