Admin Job Chains (3.x.x and earlier) - Revision history

Carfey: /* Conditional Chaining Configuration */

2016-07-01T17:01:02Z

Conditional Chaining Configuration

← Older revision		Revision as of 17:01, 1 July 2016
Line 46:		Line 46:
	As of Obsidian 1.4, conditional chaining is supported. Conditional triggers are similar to Completed triggers, in that they only fire when a job successfully completes. The Conditional state, however, lets you indicate various output conditions which determine if the chain is triggered.		As of Obsidian 1.4, conditional chaining is supported. Conditional triggers are similar to Completed triggers, in that they only fire when a job successfully completes. The Conditional state, however, lets you indicate various output conditions which determine if the chain is triggered.

	If you select the Conditional trigger state, the ''Result Conditions'' area will be revealed below the state selector. In this section, you must specify at least one condition which is used to determine if the chain will fire. Each condition must be matched for the chain to be triggered. See [[Chaining\|Job ~~chains~~]] for complete details on how conditional chaining works.		If you select the Conditional trigger state, the ''Result Conditions'' area will be revealed below the state selector. In this section, you must specify at least one condition which is used to determine if the chain will fire. Each condition must be matched for the chain to be triggered. See [[Chaining\|Job Chains]] for complete details on how conditional chaining works.

	Each condition has the following fields, all of which are mandatory when presented: Variable Name, Operator, and Value. Note that the Value field is not shown for the ''Exists/Not Exists'' operators, and supports multiple values for the ''In/Not In'' operators.		Each condition has the following fields, all of which are mandatory when presented: Variable Name, Operator, and Value. Note that the Value field is not shown for the ''Exists/Not Exists'' operators, and supports multiple values for the ''In/Not In'' operators.

Carfey: Carfey moved page Admin Job Chains to Admin Job Chains (3.x.x and earlier) without leaving a redirect

2016-07-01T16:52:29Z

Carfey moved page Admin Job Chains to Admin Job Chains (3.x.x and earlier) without leaving a redirect

← Older revision	Revision as of 16:52, 1 July 2016
(No difference)

Carfey: /* Chain Tree View */

2015-05-15T15:02:42Z

Chain Tree View

← Older revision		Revision as of 15:02, 15 May 2015
Line 14:		Line 14:
	== Chain Tree View ==		== Chain Tree View ==

	Complex chain setups can be difficult to understand at times. To facilitate understanding how the chains ~~related~~ to each other, Obsidian provides a tree view of chains as of version 3.3.0. Click on the ''View Tree'' link at the top of the table to view the tree diagram.		Complex chain setups can be difficult to understand at times. To facilitate understanding how the chains relate to each other, Obsidian provides a tree view of chains as of version 3.3.0. Click on the ''View Tree'' link at the top of the table to view the tree diagram.

	Enabled jobs are always shown as a root job in addition to any chain source jobs not found in another tree. If a job is not Enabled and is found in another chain tree, it will not be shown as a root job.		Enabled jobs are always shown as a root job in addition to any chain source jobs not found in another tree. If a job is not Enabled and is found in another chain tree, it will not be shown as a root job.

Carfey: /* Chain Tree View */

2015-05-15T15:02:29Z

Chain Tree View

← Older revision		Revision as of 15:02, 15 May 2015
Line 14:		Line 14:
	== Chain Tree View ==		== Chain Tree View ==

	~~An option for getting an overview~~ of ~~your~~ chains is the View Tree link at the top of the table~~. This will give you a~~ tree ~~view of your chains~~.		Complex chain setups can be difficult to understand at times. To facilitate understanding how the chains related to each other, Obsidian provides a tree view of chains as of version 3.3.0. Click on the ''View Tree'' link at the top of the table to view the tree diagram.

	Enabled jobs are always shown as a root job in addition to any chain source jobs not found in another tree. If a job is not Enabled and is found in another chain tree, it will not be shown as a root job.		Enabled jobs are always shown as a root job in addition to any chain source jobs not found in another tree. If a job is not Enabled and is found in another chain tree, it will not be shown as a root job.

Craig: /* Adding or Updating a Job Chain */

2015-05-15T13:59:00Z

Adding or Updating a Job Chain

← Older revision		Revision as of 13:59, 15 May 2015
Line 31:		Line 31:

	The trigger states indicate which source job termination states will trigger the target job run. Default trigger states are selected when creating a new chain since they are the commonly used options, but they may be changed to whatever is required.		The trigger states indicate which source job termination states will trigger the target job run. Default trigger states are selected when creating a new chain since they are the commonly used options, but they may be changed to whatever is required.

			A description is optional for use on the View Chains page. A description is generated if none is provided.

	A schedule is optional and can be specified to restrict which times the target job may be spawned - if the source job terminates at a time that doesn't match the schedule, the target job will not be created.		A schedule is optional and can be specified to restrict which times the target job may be spawned - if the source job terminates at a time that doesn't match the schedule, the target job will not be created.

Craig at 13:55, 15 May 2015

2015-05-15T13:55:12Z

← Older revision		Revision as of 13:55, 15 May 2015
Line 11:		Line 11:

	[[Image:3.3.0.ViewChains.PNG]]		[[Image:3.3.0.ViewChains.PNG]]

			== Chain Tree View ==

			An option for getting an overview of your chains is the View Tree link at the top of the table. This will give you a tree view of your chains.

			Enabled jobs are always shown as a root job in addition to any chain source jobs not found in another tree. If a job is not Enabled and is found in another chain tree, it will not be shown as a root job.

			'''Asterisks (*)''' mark jobs that will not be executed due to their current job state (e.g. Disabled or Ad Hoc Active).

			'''Hash signs (#)''' mark the target job of a chain that is not currently active.

			[[Image:3.3.0.ViewChainTree.PNG]]

	== Adding or Updating a Job Chain ==		== Adding or Updating a Job Chain ==

Craig: /* Job Chain Listing */

2015-05-15T13:47:10Z

Job Chain Listing

← Older revision		Revision as of 13:47, 15 May 2015
Line 10:		Line 10:
	To create a new Job Chain, click the ''Add Chain'' link in the top left of the results table, or ''Add Chain'' in the navigation bar from any place underneath the Jobs tab.		To create a new Job Chain, click the ''Add Chain'' link in the top left of the results table, or ''Add Chain'' in the navigation bar from any place underneath the Jobs tab.

	[[Image:2.5.0.ViewChains.PNG]]		[[Image:3.3.0.ViewChains.PNG]]

	== Adding or Updating a Job Chain ==		== Adding or Updating a Job Chain ==

Craig: /* Adding or Updating a Job Chain */

2015-05-15T13:45:02Z

Adding or Updating a Job Chain

← Older revision		Revision as of 13:45, 15 May 2015
Line 26:		Line 26:
	'''Note:''' The question mark icon that appears next to the form title indicates inline help. Click on the icon to see help related to the current page.		'''Note:''' The question mark icon that appears next to the form title indicates inline help. Click on the icon to see help related to the current page.

	[[Image:2.6.0.ConditionalChain.PNG]]		[[Image:3.3.0.ConditionalChain.PNG]]

	== Conditional Chaining Configuration ==		== Conditional Chaining Configuration ==

Carfey: /* Conditional Chaining Configuration */

2014-07-08T22:37:48Z

Conditional Chaining Configuration

← Older revision		Revision as of 22:37, 8 July 2014
Line 30:		Line 30:
	== Conditional Chaining Configuration ==		== Conditional Chaining Configuration ==

	As of Obsidian 1.4, conditional chaining is supported. Conditional triggers are similar to ~~the~~ Completed triggers, in that they only fire when a job successfully completes. The Conditional state, however, lets you indicate various output conditions which determine if the chain is triggered.		As of Obsidian 1.4, conditional chaining is supported. Conditional triggers are similar to Completed triggers, in that they only fire when a job successfully completes. The Conditional state, however, lets you indicate various output conditions which determine if the chain is triggered.

	If you select the Conditional trigger state, the ''Result Conditions'' area will be revealed below the state selector. In this section, you must specify at least one condition which is used to determine if the chain will fire. Each condition must be matched for the chain to be triggered. See [[Chaining\|Job chains]] for complete details on how conditional chaining works.		If you select the Conditional trigger state, the ''Result Conditions'' area will be revealed below the state selector. In this section, you must specify at least one condition which is used to determine if the chain will fire. Each condition must be matched for the chain to be triggered. See [[Chaining\|Job chains]] for complete details on how conditional chaining works.

Carfey: /* Conditional Chaining Configuration */

2014-07-08T22:37:13Z

Conditional Chaining Configuration

← Older revision		Revision as of 22:37, 8 July 2014
Line 30:		Line 30:
	== Conditional Chaining Configuration ==		== Conditional Chaining Configuration ==

	As of Obsidian 1.4, conditional chaining is supported. ''Conditional'' triggers are similar to the ''Completed triggers'', in that they only fire when a job successfully completes. The ~~conditional~~ state, however, lets you indicate various output conditions which determine if the chain is triggered.		As of Obsidian 1.4, conditional chaining is supported. Conditional triggers are similar to the Completed triggers, in that they only fire when a job successfully completes. The Conditional state, however, lets you indicate various output conditions which determine if the chain is triggered.

	If you select the ''Conditional'' trigger state, the ''Result Conditions'' area will be revealed below the state selector. In this section, you must specify at least one condition which is used to determine if the chain will fire. Each condition must be matched for the chain to be triggered. See [[Chaining\|Job chains]] for complete details on how conditional chaining works.		If you select the Conditional trigger state, the ''Result Conditions'' area will be revealed below the state selector. In this section, you must specify at least one condition which is used to determine if the chain will fire. Each condition must be matched for the chain to be triggered. See [[Chaining\|Job chains]] for complete details on how conditional chaining works.

	Each condition has the following fields, all of which are mandatory when presented: Variable Name, Operator, and Value. Note that the Value field is not shown for the ''Exists/Not Exists'' operators, and supports multiple values for the ''In/Not In'' operators.		Each condition has the following fields, all of which are mandatory when presented: Variable Name, Operator, and Value. Note that the Value field is not shown for the ''Exists/Not Exists'' operators, and supports multiple values for the ''In/Not In'' operators.