Maven Release 2022.2.31.2611

Version: AgWare Maven 2022.2.31.2611
Release Date: August 30, 2022
Download Link: Download Now

  • Boundary Lines have been changed in regards to how they are handled by the system. This is largely a behind-the-scenes update but there are some UI changes as well. Boundary Lines are now drawn using Google Maps’ built-in drawing control
  • Added an option to adjust Improvement comparisons based on Remaining Life. This is an option for SCA Land Mix and SCA Component Models.
  • The Subject Map has been updated to allow polygons to be drawn in addition to placing a simple Marker. The Marker continues to act exactly as before, however new controls have been added to the bottom of the map that allow polygons to be drawn
  • The Valuation Override Report now lists details of the overridden Sales. Expanding a Valuation index in the grid will list individual Added/Removed Sales and their reasons.
  • Permanent Plantings have been added to the Sale Info popup. It contains two tabs: Blocks and Summary. In the Blocks view each row can be expanded to show Values and Depreciation
  • Controls for adding secondary values to the Property Type, Land Use, and Attribute fields for Subjects have been added. The secondary values are entered by using the buttons attached to the primary inputs for these values:


Graphical user interface, text, application Description automatically generated

The number on the button shows how many secondary values are set for the field. Clicking the button opens a popup where the values can be entered.

Graphical user interface, text, application, email Description automatically generated

The popup has a dropdown menu that contains the same options as the primary input it is attached to. To enter a secondary value, select an option from the dropdown and click “Add”. This will add the selected value to the list in the lower area of the popup. To delete a value, click the ‘X’ next to it in the list.

  • The report template editor has been updated to allow files to be saved with a different name with a Save As command. After opening a template, users can selected Save As to save the modified template as a different name without updating the original file. With this change new templates can also be created in the editor and saved with a name specified.

When specifying a name for the template, a dialog box shows where the user can enter the file name:

Graphical user interface, application Description automatically generated

This will open whenever the Save As option in clicked, or when Save is clicked after creating a new file. If a filename is entered that already exists, but is not the original file that was opened, a confirmation popup is shown to verify that the file will be overwritten:

Graphical user interface Description automatically generated

  • Comparison Values can now use Secondary values for Property Type, Land Use, and Attributes. The formula for coming up with a rating for a Sale Comparison is as follows:

Each Subject value is rated against every Sale value. All of these individual ratings are summed together. The sum is then divided by the number of distinct values between the two sets. By default, these comparisons use the rating scheme of 1 if they match and 0 if              they do not match, however they also support Rating Matrices.


Assume a Subject and a Sale with the following values for their Secondary Land Use:


And the Model being used has the following Rating Matrix applied for Land Use:


The rating for Secondary Land Use would be:

Subject Peas vs. Sale Carrots


Subject Peas vs. Sale Onions


Subject Onions vs. Sale Carrots


Subject Onions vs. Sale Onions*




*Onions is not part of the Rating Matrix, so the default comparison is used (1 if match, 0 if not).

The final rating is the Sum divided by the total distinct values between the two sets, which is 3 (Peas, Carrots, Onions).

Rating = 1.5/3 = 0.500

  • Changes have been made with how signing information is managed when performing a Rollback of a Finalized Report. When a Report is rolled back, the Signature, Name, and Signed Date fields for the Appraiser and Co-Appraiser are cleared out. Other information such as certification and inspection fields are kept
  • Range of Value models can be saved without approval. If attempting to Save a RoV model via the ‘Save’ link above the form that appears after editing a field, the Model should save without warning provided all other fields are valid. Users should no longer receive a “Name field is required” error. When saving an RoV model this way, it will be placed in the “Modified” state. To approve an RoV model a Name must still be entered and the “Approve” button used
  • A new “Sale Search” tab has been added to the Valuation Details form. The tab contains new controls for finding Sale Comparison to add to the report via override. This replaces the old method of only being able to add a Sale Comparison manually by entering in its Sale Index.
  • The grids used to update Valuations in the Override tab have been replaced with new controls for Improvements, Sale Comparisons, and Land Rows (Component Valuations only). The new grids omit the “Update” buttons that used to be needed to push through the changes after entering new values in the grid. Now, the Valuation is updated in real-time once the fields are changed in the grid. For Sale Comparisons, in place of the old method of adding them directly by Sale Index, the Add (+) button now copies whatever value is entered in to the old Sale Index field and copies it to the Sale Index field on the new Sale Search tab and begins a search automatically.
  • “Effective Date” has been added as a new field when choosing a Model and starting a Valuation. The date entered here will be used as the Effective Date of Appraisal, instead of using the Subject’s date has before. The default value of the Effective Date field is the current date.
  • Fields on the Sale Search tab for Valuations are now initialized to default values. The default values are:
Max Date:Effective Date of the Valuation
Min Date:The “Maximum Sale Age” value of the Model used in the Valuation, or three years if this field isn’t set, prior to the End Date value.
Distance:Double the value of the “Distance Cushion” value of the Model used in the Valuation, or 10 miles if this field isn’t set.
  • The Valuation Override report has had some updates. The Username dropdown has been removed, now only Start Date and End Date are used as parameters. The results from the search will be displayed in two grids: Users and Models. The first tab shows the User report. This is similar to the old grid. The results are shown summarized per-user, with filtering options on the User column. This is the reason the Username search parameter was removed. A new column showing the average change from the original Model-derived value has been added. This shows, as an average, how much that user is overriding the value by. Expanding a User row shows the individual overridden valuations as before. A new column showing how much the value was changed, as a percentage of the original value, has been added. Expanding a valuation will list the overridden sales for that valuation. This has been changed from the old version to include both Added and Removed Sales in the same grid instead of showing them in separate lists. An “Action” column has been added to indicate if the Sale was Added or Removed. This column is filterable. The second tab on the page shows the same data as the first, but grouped together by the Model used instead of by User. A third tab displays all valuations with override, without being grouped by a User or Model. It contains the same data as the second-level grids of the previous two tabs.
  • The db-update tool will now prompt for user input to prevent it from closing after running. This is useful when opening the program from Windows Explorer. A new command line option -c or –close has been added to allow the program to close normally without the prompt.

New statistics are shown after running a Model Evaluation. The new stats are:

  1. Coefficient of Dispersion
  2. Weighted Coefficient of Dispersion
  3. Coefficient of Variation
  4. Weighted Coefficient of Variation
  5. Q1, Q3
  6. Low, High, Mean, and Median price spread
  7. The old “Coefficient of Dispersion” has been renamed to “Quartile CoD”

The Low, High, Mean, and Median price spread values represent summaries of the spread between the lowest adjusted price of a Sale Comparison and the highest. For SCA Land Mix valuations this is simply the spread between the Sale Comparisons. For SCA Component valuations we calculate a spread for each land row, and then use the highest of these to display a spread for the overall valuation.

When the evaluation finishes, the statistics are shown as a summary with just the valued count, average, and Quartile CoD shown:

Graphical user interface, text, application Description automatically generated


Expanding the panel shows all of the statistics:

Graphical user interface, text, application, email Description automatically generated

A Help link is shown in the upper-right corner of a panel and opens up a page explaining the statistics.

  • Sale Comparisons can now be reordered by dragging-and-dropping on the Override tab. To move a Sale, click the icon in the Order column of the grid and drag it to the row on the grid you want it to be in. When moving a Sale up, the Sale it gets dropped onto will be moved down along with all Sales in-between. When moving down, the Sale it gets dropped onto will be moved up along with all Sales in-between.
  • The Valuation Details form has been updated to use the same new layout as other report types. The Override tab contains grids for inputting the unit value for Land and Improvements. Since RoV valuation types do no use Sale Comparisons, the Sale Search tab is not included on the form.
  • When updating the selection of Sales for a Land-Mix valuation, the per-unit value no longer changes, instead a calculated value based on the selected sales is displayed, however the user must manually input the actual per-unit value used by the valuation.
  • When cloning a Sale or Subject to a new Subject, the Date is no longer copied and instead set to the current Date. This may be tricky to test since we no longer show the Date field for Subjects. It’s only real purpose now is for use when generating Subject Indices. To verify this a Subject Index Prefix should be used that incorporates the date.