Content Comparison

...

For a detailed description of rule format, examples, and the full rules data model, please see the Business Logic MobileMap documentaiton pagedocumentation page. For details on how MobileMap handles these business rules when collecting tree and log data please see MobileMap: Tree and Log Data Collection .

Managing Validation Rules in Inventory Manager

In order to assist with the mangement management of Validation Rules, InventoryManager provides a dedicated interface for creating and editing validation rules.  The screenshot below shows this user interface in a typical InventoryManager implementation. 

...

• Select the layer that the rule should act upon

  Click on

  (required).

  • In the example above the rule is applied to the Trees table.

  • Selecting the desired layer in from the dropdown list.

• Define the criteria that must be met prior to applying the test (optional). 

  • In the example above, the test should only be applied if the field '

  Contract_or_State

  • Species' has a value equal to '

  Contract

  • HWD' for hardwoods. If the

  field 

  • '

  Contract_or_State' is null or

  • Species' has a value that is null or not equal to '

  Contract

  • HWD', the test portion of the rule will not even be assessed.

  • Many rules do not require criteria because they should always be true

  • If a criteria is needed:Enter the criteria value

    • Select the field(s) from the field selection box.  If more than one field is needed, click on the first field name, then hold CTRL and click on additional field names.

    • Select the criteria operator from the dropdown list.

    • Enter the text or number in the

    input

    • value which will be evaluated. 

    If the criteria value is null

    • Typically this value is simply typed in with no punctuation (e.g., LP). When testing if a field or fields have a null value, enter as 'Null' (capitol N, without quotes).  If the value is coming from

    a

    • another field (uncommon), enter in the field within curly brackets { } (e.g., '{

    Contract

    • Saw_

    or_State

    • Stopper}' without the quotes

  • Select the criteria operator

  Click on the desired operator in the dropdown list

  • • .

• Select the criteria field.

• Click on the field name in the selection box.  If more than one field is needed, click on the first field name, then hold CTRL and click on additional field names

  • If no criteria is needed because the test should always be applied (see examples 1, 2 and 6 above):

    • Uncheck the 'Include criteria' checkbox

• Select the test inputsDefine the main rule logic

  • Select the

  test field.Click on

  • field(s) from the field

  name in the

  • selection box.  If more than one field is needed, click on the first field name, then hold CTRL and click on additional field names.

  • Select the

  test

  • criteria operator

  Click on the desried operator in the dropdown list

  • from the dropdown list.

  • Enter the text or number in the value which will be evaluated.  Typically this value is simply typed in with no punctuation (e.g., LP). When testing if a field or fields have a null value, enter as 'Null' (capitol N, without quotes).  If the value is coming from another field (uncommon), enter in the field within curly brackets { } (e.g., '{Saw_Stopper}' without the quotes.

• Select the error type

  • Select 'Error' or 'Warning' from the dropdown list

  • Errors will prevent the user from saving the record (or closing the tree list)

  • Warnings will be displayed once to the user, then will allow save (and close of tree list)

• Enter the error (or warning) message to display to the user

  • Enter the full message that should be displayed to the user if the features does not pass the validation rule

  • This should be a short message that will help the user address the problem. It is best to reference field Aliases (rather than field names) so it matches what the user sees on their screen. Providing the expected value helps users enter correct values.

Related Domains

Related domains define the relationship between two fields that each use coded value domains to provide a list of allowed values for that field.  Related domains restrict the choices in one attribute field based on the values selected in a related attribute field (e.g., if Plot Type is 'Variable Radius', Plot Size options should only include variable radius plot sizes and NOT fixed area plot sizes).  To achieve this, a set of related domains records are added to the Related_Domains table.  Each Related Domains record lists a value in the second field (target) dropdown list that should be available only if the specified value in the first field (source) dropdown list has been selected.  To do this, related domains utilize a source field, source value, target field and target value.  If the specified source value is selected for the source field, then the specified target value will be in the dropdown list for the target field.

...

In order to assist with the mangement management of Related Domains, InventoryManager provides a dedicated interface for creating and editing validation rules.  The screenshot below shows this user interface in a typical InventoryManager implementation.  Even if your organization is not using InventoryManager to manage your MobileMap data collection, the screenshot below is still helpful to explain the process and inputs for creating and editing Related Domains.

...