From the lower app bar on the Validation page, you can import new rules. Click Import Rule Set and select an XML rule backup file. This file can be generated by exporting rules from 1Validate. You can load an export containing individual rules, entire rule folders, or a session that references rules. You can import a number of rule files sequentially to build up the correct set of rules.
Rules to be run inside 1Edit cannot contain the following elements:
· Iterating over geometries as if they were collections using the For All In collection element
· Nested values (accessing values nested within other values, also known as user-defined types)
· Array element values
Rules containing constant values (values picked from a named constants metadata store to translate a human readable value into a number) can be supported if there is a suitable enumeration defined in the schema (that is, in the GML xsd that was imported to create the project.) The class name of the named constant must be the name of the enumeration defined in the schema.
The following built-in functions are available in this release:
· angle
· area
· boundary
· count_parts
· intersection
· to_integer
· union
· outer_ring
· is_boundary_left
· is_boundary_right
· point_on_line
· line
· count_inner_rings
· to_string
· count_vertices
· count_parts
· distance
· line_length
To define a default set of rules to be used by all users, load the required rules into the project from which a template is to be created. When the template is created and distributed, those rules will automatically be loaded into all projects that are built using that template (all projects created for jobs within the worklist page are created from a template.)