The B_AttributeRules table is used to define the attribute rules for features in a utility network.
The table or feature class that will have the rule applied.
The name of the attribute rule.
A description of the rule. The description is limited to 256 characters.
The type of attribute rule to add. The following are valid inputs:
The subtype to which the rule will apply if the input table or feature class has subtypes.
The field in the asset package that will have an attribute rule applied to it.
Defines whether the field is editable. To define a field as editable, set the value to True.
Trigger on Insert
Defines whether the attribute rule will be triggered when a feature is added.
Trigger on Delete
Defines whether the attribute rule will be triggered when a feature is deleted.
Trigger on Update
Defines whether the attribute rule will be triggered when a feature is updated.
The expression that defines how the field will be populated when the attribute rule is triggered.
The error number that will be returned when the rule is violated.
The error message that will be returned when the rule is violated. A descriptive message will help the editor understand the violation.
Exclude from Application Evaluation
Specifies whether the rule will be evaluated before edits are applied. Because not all clients may have the capability to run all of the available rules, you can choose to flag a rule.
Specifies whether the rule will be executed in batch mode.
The severity of the error. A value within the range of 1 through 5 can be chosen to define the severity of the rule. A value of 1 is high, being the most severe, and a value of 5 is low, being the least severe.
A set of tags to identify the rule (searchable and indexable) as a way to map to a functional requirement in a data model. To enter multiple tags, use a semicolon delimiter, for example, Tag1;Tag2;Tag3.
Determines if a rule is enabled after creation. To disable, set to False.
When rules are evaluated, the order controls the sequence in which rules are evaluated. For calculation rules, the order in which rules are evaluated on a dataset is important, as this can cause the result of the rule evaluation to differ.
A system-generated integer value that defines the rule category, if applicable.
A system-generated JSON value that defines the configuration of a Data Reviewer-based rule.
Script Expression Backup
The fully qualified database name and schema for all Arcade script expressions found in the database.