2024:Validate Branch (Command) - Revision history

Dgreenwood: Dgreenwood moved page Validate Branch (Command) to 2024:Validate Branch (Command)

2025-03-02T13:47:57Z

Dgreenwood moved page Validate Branch (Command) to 2024:Validate Branch (Command)

← Older revision	Revision as of 08:47, 2 March 2025
(No difference)

Dgreenwood: Dgreenwood moved page Validate Branch to Validate Branch (Command)

2025-03-02T13:47:29Z

Dgreenwood moved page Validate Branch to Validate Branch (Command)

← Older revision	Revision as of 08:47, 2 March 2025
(No difference)

Dgreenwood at 13:39, 5 September 2024

2024-09-05T13:39:02Z

← Older revision		Revision as of 08:39, 5 September 2024
Line 1:		Line 1:
	{{~~beta~~}}		{{AutoVersion}}

	<blockquote>		<blockquote>

Dgreenwood: Dgreenwood moved page beta:Validate Branch to Validate Branch without leaving a redirect

2024-08-29T20:12:53Z

Dgreenwood moved page beta:Validate Branch to Validate Branch without leaving a redirect

← Older revision	Revision as of 15:12, 29 August 2024
(No difference)

Dgreenwood: /* Validating an entire Grooper Repository in 2024 */

2024-07-10T20:26:28Z

Validating an entire Grooper Repository in 2024

← Older revision		Revision as of 15:26, 10 July 2024
Line 64:		Line 64:

	==== Validating an entire Grooper Repository in 2024 ====		==== Validating an entire Grooper Repository in 2024 ====

			*<li class="attn-bullet"> '''''BE AWARE:''''' Most Grooper users will find it easiest to validate their Grooper Repository by validating each '''Project'''. Very few users will validate their repos as described below. This documentation mostly exists for the sake of completeness.

	Validating an entire Grooper Repository can be done from Grooper Command Console using the <code>connections validate</code> command. This command will display nodes with configuration errors in GCC. It will also write the results to a validation log as a TXT file at <code>C:\ProgramData\BIS\ValidationLogs</code>.		Validating an entire Grooper Repository can be done from Grooper Command Console using the <code>connections validate</code> command. This command will display nodes with configuration errors in GCC. It will also write the results to a validation log as a TXT file at <code>C:\ProgramData\BIS\ValidationLogs</code>.

Dgreenwood: /* Using the Validate Branch command to catch errors */

2024-06-26T13:49:35Z

Using the Validate Branch command to catch errors

← Older revision		Revision as of 08:49, 26 June 2024
Line 29:		Line 29:
	<tabs>		<tabs>
	<tab name="Version 2024">		<tab name="Version 2024">
			[[File:2024 ValidateBranch 01 02 UsingValidateBranch-02.png]]
	</tab>		</tab>
	<tab name="Version 2023">		<tab name="Version 2023">

Dgreenwood at 21:28, 25 June 2024

2024-06-25T21:28:19Z

← Older revision		Revision as of 16:28, 25 June 2024
Line 1:		Line 1:
			{{beta}}

	<blockquote>		<blockquote>
	The '''''Validate Branch''''' command verifies all nodes in a selected branch of the Grooper node tree are configured without obvious errors.		The '''''Validate Branch''''' command verifies all nodes in a selected branch of the Grooper node tree are configured without obvious errors.

Dgreenwood: /* About */

2024-06-25T20:06:35Z

About

Dgreenwood: /* About */

2024-06-25T18:34:25Z

About

← Older revision		Revision as of 13:34, 25 June 2024
Line 7:		Line 7:
	'''''Validate Branch''''' helps ensure Grooper nodes are configured correctly. When executed, it checks the property configurations of each child at every level below the selected node. If any node has a "validation error", Grooper will inform the user.		'''''Validate Branch''''' helps ensure Grooper nodes are configured correctly. When executed, it checks the property configurations of each child at every level below the selected node. If any node has a "validation error", Grooper will inform the user.
	<section begin="validate_branch" />		<section begin="validate_branch" />
	~~<h5>~~What is a validation error?~~</h5>~~		===== What is a validation error? =====
	[[File:2024 ValidateBranch 01 About-01.png\|thumb\|left\|Example validation error]]		[[File:2024 ValidateBranch 01 About-01.png\|thumb\|left\|Example validation error]]
	A validation error is any Grooper generated warning indicating some required property configuration is invalid or missing.		A validation error is any Grooper generated warning indicating some required property configuration is invalid or missing.

Dgreenwood at 18:32, 25 June 2024

2024-06-25T18:32:35Z

← Older revision		Revision as of 13:32, 25 June 2024
Line 7:		Line 7:
	'''''Validate Branch''''' helps ensure Grooper nodes are configured correctly. When executed, it checks the property configurations of each child at every level below the selected node. If any node has a "validation error", Grooper will inform the user.		'''''Validate Branch''''' helps ensure Grooper nodes are configured correctly. When executed, it checks the property configurations of each child at every level below the selected node. If any node has a "validation error", Grooper will inform the user.
	<section begin="validate_branch" />		<section begin="validate_branch" />
	~~=====~~ What is a validation error? ~~=====~~		<h5>What is a validation error?</h5>
	[[File:2024 ValidateBranch 01 About-01.png\|thumb\|left\|Example validation error]]		[[File:2024 ValidateBranch 01 About-01.png\|thumb\|left\|Example validation error]]
	A validation error is any Grooper generated warning indicating some required property configuration is invalid or missing.		A validation error is any Grooper generated warning indicating some required property configuration is invalid or missing.

← Older revision		Revision as of 15:06, 25 June 2024
Line 7:		Line 7:
	'''''Validate Branch''''' helps ensure Grooper nodes are configured correctly. When executed, it checks the property configurations of each child at every level below the selected node. If any node has a "validation error", Grooper will inform the user.		'''''Validate Branch''''' helps ensure Grooper nodes are configured correctly. When executed, it checks the property configurations of each child at every level below the selected node. If any node has a "validation error", Grooper will inform the user.
	<section begin="validate_branch" />		<section begin="validate_branch" />
	===== What is a validation error? =====		=== What is a validation error? ===
	[[File:2024 ValidateBranch 01 About-01.png\|thumb\|left\|Example validation error]]		[[File:2024 ValidateBranch 01 About-01.png\|thumb\|left\|Example validation error]]
	A validation error is any Grooper generated warning indicating some required property configuration is invalid or missing.		A validation error is any Grooper generated warning indicating some required property configuration is invalid or missing.
Line 14:		Line 14:
	<br clear=all>		<br clear=all>

	===== Using the Validate Branch command to catch errors =====		=== Using the Validate Branch command to catch errors ===

	Validating nodes is a good way to catch misconfigured nodes in Grooper. The "Validate Branch" command can be applied to a '''Project''' or any node in a '''Project'''. It will validate the selected node as well as all the node's descendants (or in other words that "branch" of the tree).		Validating nodes is a good way to catch misconfigured nodes in Grooper. The "Validate Branch" command can be applied to a '''Project''' or any node in a '''Project'''. It will validate the selected node as well as all the node's descendants (or in other words that "branch" of the tree).
Line 33:		Line 33:
	</tabs>		</tabs>

	===== Validating an entire Grooper Repository =====		=== Validating an entire Grooper Repository ===

	Most Grooper users will find it easiest to validate their Grooper Repository by simply validating each '''Project'''. This is generally the most efficient for Grooper Repositories with few '''Projects'''. However, for larger Grooper Repos with dozens of '''Projects''', this may be more tedious. For those environments, you may want to use an alternate method to validating the entire Grooper Repository. Depending on what version you're coming from, this is done differently:		Most Grooper users will find it easiest to validate their Grooper Repository by simply validating each '''Project'''. This is generally the most efficient for Grooper Repositories with few '''Projects'''. However, for larger Grooper Repos with dozens of '''Projects''', this may be more tedious. For those environments, you may want to use an alternate method to validating the entire Grooper Repository. Depending on what version you're coming from, this is done differently:
Line 39:		Line 39:
	* In version 2024, you can use Grooper Command Console to validate your Grooper Repository.		* In version 2024, you can use Grooper Command Console to validate your Grooper Repository.

	====== Validating an entire Grooper Repository prior to 2024 ======		==== Validating an entire Grooper Repository prior to 2024 ====

	Prior to version 2024, the '''''Validate Branch''''' command can be used on the Grooper Root, effectively validating the entire Grooper Repository. '''''BE AWARE: This can only be done from the Grooper thick client NOT the web client.'''''		Prior to version 2024, the '''''Validate Branch''''' command can be used on the Grooper Root, effectively validating the entire Grooper Repository. '''''BE AWARE: This can only be done from the Grooper thick client NOT the web client.'''''
Line 60:		Line 60:
	\|}		\|}

	====== Validating an entire Grooper Repository in 2024 ======		==== Validating an entire Grooper Repository in 2024 ====

	Validating an entire Grooper Repository can be done from Grooper Command Console using the <code>connections validate</code> command. This command will display nodes with configuration errors in GCC. It will also write the results to a validation log as a TXT file at <code>C:\ProgramData\BIS\ValidationLogs</code>.		Validating an entire Grooper Repository can be done from Grooper Command Console using the <code>connections validate</code> command. This command will display nodes with configuration errors in GCC. It will also write the results to a validation log as a TXT file at <code>C:\ProgramData\BIS\ValidationLogs</code>.