Attribute rules are used to automatically populate or update attributes. For example, they are used to correctly align the point symbol at the end or on a line when the point object is set down. Another example is managing the symbology based on different attributes.
Modify / Delete: The content of VertiGIS Networks’ attribute rules must not be changed. Rules can be disabled.
•The existing attribute rules must not be deleted from the database. They may be disabled if necessary.
•When disabling, we recommend marking the attribute rules that have been disabled with a tag. In this way, the administrator can better recognize which VertiGIS rules were disabled by him or his colleagues and also turn them on again in a systematic manner. When switching on again and removing the "disable date", please ensure that existing VertiGIS tags are not deleted.
In the case of an update (not yet available), the values of VertiGIS default attribute rules would overwrite existing settings.
Create:
New attribute rules can be added. The name must be unique.
The description should be completed so that it is easier to understand what the rule is doing.
Tags help to identify the purpose of the rule and thus to manage and maintain these rules.
Naming conventions of VertiGIS models:
Syntax: trigger_target_SubType{_Text}
Meaning of the name parts: see table below.
Naming convention for extension (customize)
Syntax: CUS_trigger_target_SubType{_Text}
It is mandatory to start the name of the attribute rule with the "CUS_" prefix.
Values |
|
|---|---|
Trigger |
c: create u: update d: delete cu: create and update cud: create update and delete
n: stands for "none". No Create/Update/Delete checkbox is checked in the rule definition. |
Target |
•"Self": if the target of the expression is the object that the rule triggers •“Other”: if the expression acts on other objects, regardless of whether UN and/or non-UN objects |
Subtype/asset group |
•Name of the subtype/asset group. If too long, the code can also be used •Use “all” if all subtypes/asset groups can trigger the rule |
Additional text |
Optional. Keyword for the purpose or number to ensure the rule name is not ambiguous |
Internal (R&D):
•For all attribute rules for our product, the tag 'VertiGIS Networks' is entered by R&D. This is to ensure that for upcoming updates we can identify the attribute rules of the standard product.
•Formatting Arcade expressions: We use JavaScript formatting so that the Arcade formulas are legible.
•Arcade expressions: Set version date as a comment, as well as for the update date if it was changed during an update of a version. (// Version xxxxxx //Update Versions xxxx)
•When naming the attribute rules, we always use the name of the subtype for the product and not the code.
Examples
These examples show how attribute rules can be named. The listed ones do not correspond to the defined rules in VertiGIS Networks data models and do not purport to be them.
•d_other_All_Document: Deleting a water assembly object triggers an adjustment of linked documents;
•cu_self_FlowControlDevice_Symbology: Creating or adjusting a field value or the geometry (e.g. AssetCatalogItem) of a FlowControlDevice controls the content of the fields sym_style and/or sym_color;
•cu_self_ All_SymRotation: Symbol rotation is calculated when an object is recorded or adjusted;
•u_self_ All_NETMainLifeCycleStatus: Any change to an existing WaterDevice (e.g. by DetailLifeCycleStatus attributes) tracks the value of the NET_MainLifeCycleStatus network attribute;
•c_self_ FireDevice_DefaultValues: Set default values when creating a hydrant (if not controlled by templates);
•cu_self_ All_Label: Populate and update attribute for the labeling content of a line when this line is generated or changed. Note: it has not yet been defined how the labels will be defined in the future in the VertiGIS models.
The following tags are used in the attribute rules by VertiGIS. A user can define the same and/or other tags for additional rules.
•Symbology
•Label: (labeling)
•Annotation: influence on annotation type labeling
•Relation: influence on objects that are related via Esri relationship class
•Association: concerns object connected via utility network connectivity and association rules
•Network: edit network attribute
•Spatial: concerns the object geometry (x, y, z values)
•Catalog: interaction with the entries of a catalog table
Permissible attribute-rule field lengths in AssetPackage, as of July 2023. UN version 5 on ArcGISPro 2.9.x:
Field length 64, description length 256, tags 2000 characters, field 31, type 11, script expression 30000
