1. Home
  2. Release Notes
  3. Feature / Hot fix release : 8/19/2022

Feature / Hot fix release : 8/19/2022

Feature Enhancements:

Scouting and Trapping Map Layers

While in the Scouting and Trapping feature in AgVerdict NEXT, users will now have the ability to control the information that is displayed on the screen.

These controls can be found in the Map Layers control panel when in the Scouting and Trapping feature. This allows you to only show the information that you want to see, and remove the unwanted map overlays.

Along with new layers, we will allow you to turn off the visibility to the field, block and sub-block boundaries. As well as the field names, and markers. This gives a lot of flexibility to see the information you want on the map.

Addressed Issues

  • Addressed issues with some products and their REI / PHI updating properly when editing the products. This now works as expected.
  • Fixed issue with applications events that were completed in AgLogic not allowing the PUR to be opened and viewed in AgVerdict. This now works as expected for the completed locations.
  • Fixed issue where AgVance tickets for the Coachella location would not pull into AgVerdict. This is now working as expected.

Sampling fixes

  • A bug has been fixed where double clicking on the grid in sampling would cause all points to disappear.
  • A bug has been fixed where deleting a sampling point under certain conditions would clear all sampling points from a grid.

Variable Rate Beta Fixes

  • A bug has been fixed which would cause a failure on save and process
  • A security hole has been patched which allowed direct navigation to VR events when not authorized to view the grower.
  • A bug has been fixed where all locations would occasionally not load in the location select screen for multi-location VR events.
  • VR “In Stock” filter now works correctly
  • An appearance bug has been fixed where the full path would not appear for VR events on sub-blocks
  • When a VR event is processing or failed, a user will now be correctly prevented from accessing VR Reports.
  • A bug has been fixed where a crash would happen if a user navigated to a VR event created on an old boundary
  • The New VR button is now inaccessible when a user does not have feature access to variable rate

Was this article helpful?

Related Articles

Leave a Comment