Feature rules are methods and triggers that process data accordingly to predefined algorithms. For example, rules perform complex consistency and dependency checks at certain events, such as before inserting or after modifying a feature. You can edit some aspects of the default rules provided with industry models.
Feature rules are provided with Infrastructure Map Server. However, if you have some experience with PL/SQL triggers, you can define your own server-side feature rules via Oracle triggers and the API. Please refer to the respective manuals.
|Feature Rule Properties||Description|
|Feature Class||Name of the feature class|
Server Side (PL/SQL)
Client Side (.NET) Feature rules can be server-side or client-side.
|Click the respective tab. You can define only server-side feature rules.|
|Applied Rule Bases||Lists feature rules that are currently assigned to the feature class. The assigned feature rules are recorded in the system table TB_RULE_BASE. |
The TB_RULE_FCLASSTYPE table defines which feature rule is available for which feature class type. Example: Calculating the length is valid for LineString feature classes but not for point feature classes.
|Priority||Defines the execution order of the feature rules. A feature rule with a lower priority value is executed before a rule with a higher value. |
Example: Validate the geometry of a feature before calculating the area.
Use the Up and Down buttons to change the order and modify the priority.
|Rule Base Definitions|| Lists all feature rules (TB_RULE_DEF) and rule groups (TB_RULE_GROUP) that are available for the current feature class. |
If you select a group, all included rules are added to the Applied Rule Bases list.
|New Group|| A group can contain several feature rules that define other rules, such as one Before and one After rule. |
Server-side rules must adhere to the Oracle trigger limitations. In particular, row triggers cannot query or modify tables in jobs, except for the changed row. Because of this, most server-side rules are implemented as a group of rules. A group of feature rules consists of a before-action rule on the row that inserts the ROWID of modified features into a temporary table, and an after-action statement rule doing the actual work.
You can add feature rules only if they do not yet belong to another rule group. Also, you cannot add the system feature rules to a new customer rule group.
|Event||Event to which a feature rule reacts.|