Hierarchy Model Rules are used to define the operations that can be performed for each type of entity (model type) under specific hierarchy node types

For example, a Site hierarchy node type can only be added under a Customer hierarchy node type.

Model Details: data/RuleModelHierarchyType

An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title			Description	Details
Model Type *			The model type the rule will be applied for	Field Name: model_type Type: String Format: uri
Operation *			The operation that applies for this rule Default: add	Field Name: operation Type: String Default: add Choices: ["Get", "Add", "Update"]
	Allowed Hierarchy Node Types		The list of Hierarchy Node Types that will be allowed	Field Name: hierarchy_types.[n] Type: Array
		Permitted Hierarchy Node Type	Allowed Hierarchy Node Type	Field Name: hierarchy_types.[n].hierarchy_type Type: String Target: data/HierarchyNodeType Target attr: name Format: uri Choices: [" "]

Model: data/RuleModelHierarchyType

Managing Hierarchy Model Rules

Model Details: data/RuleModelHierarchyType