AgVerdict NEXT iOS app Offline Recommendations
When using an iPad, the Agverdict NEXT iOS app can now write offline recommendations.
This new feature will allow users to write basic unpriced recommendations out in the field with no service. When out of service, the app will do a basic label check, that has about 90% coverage. Then when back into service it will do a full label check to confirm the success of the label check.
Things to know:
- This is available on the iPad only.
- Creation and editing of recommendations is not available within California and Arizona due to required permit support.
- Support is for basic (unpriced) recommendations only.
- Recommendations written on the App cannot be edited from the Web, just viewed.
In Order to Enable Recommendations on the iPad, users must:
- Have access to Recommendations in AgVerdict
- Within Preferences on the app, select “Enable Recommendations”. After recommendations are first enabled, the device will sync product labels and recommendations.
To see more on this feature please navigate to the link below:
More on Offline Recommendations
Land Management
In this release, the ability to manage a grower’s lands has been moved into AgVerdict NEXT. Users can now move lands between growers, inactivate or reactivate lands as needed, and, if necessary, permanently delete a land.
You can navigate to the main page on Land Management for more information by clicking the link below.
More on Land management
Addressed Issues
- Fixed a layout issue with the “New App List” view to ensure the column widths adjust so that the columns extend to the full width of the browser window.
- Addressed issue where column widths on the “new rec list” would not persist and revert back to their original size. This is now working as expected.
- Fixed issue where an incorrect EPA number was showing on specific records. This is now working as expected.
- Addressed an issue where recommendations being saved to a farm plan would throw an error and users had to refresh to continue. This is now working as expected.
- Fixed issue on trapping reports, where they could not be generated with maps if auto traps were on the report. This is now working as expected.