1. Home
  2. Release Notes
  3. Feature / Hot fix release : 2/14/2023

Feature / Hot fix release : 2/14/2023

Shared Tank Mixes in Recommendations

AgVerdict now has the ability to share tank mixes within the recommendation. This means that any tank mix you have created, can be shared with other users in AgVerdict. When you have selected one of your tank mixes, there is a button in the lower right side of the screen to “Share Tank Mix”.

Then you can just type either the users name. You can add as many people as you want to share.

Note: If you no longer want to share a tank mix with other users you can remove them by removing there name from the shared list, then updating. Tank Mixes shared with you cannot be shared again to other users.

When viewing your Tank Mixes you will be able to see 3 tabs of tank Mixes.

  • All Tank Mixes
  • My Mixes
  • Shared with me

From this view you will be able to see all your tank mixes, just your created tank mixes. As well as the ones that have been shared with you.

WPS Updates

WPS Status Column

We have updated the information that is displayed in this column. This information is showed in the app event list, and the recommendation list. Now both lists will display the same most updated status.

List Record Counter

In this release, we have added a small UI update that will show you how many records have returned with the applied filters. This can be used to filter on a specific WPS status notification, and quickly see the record count. This can be seen in the upper right hand side of the list grid.

Addressed Issues

  • The Quote and Order tool now supports up to 200 products. Previously we only supported 39 products.
  • Addressed issue with low loading times on the app event list. This has been addressed and loading times have been improved.
  • Fixed issue where new customers that have been added into AgVance were not integrating into AgVerdict properly. This caused issues when attempting to create custom blends for those customer during a recommendation.
  • Addressed issue when a user was updating and saving new grower information, the changes would not actually save. This effected the name of the grower in some cases. This is now working as expected.

Was this article helpful?

Related Articles

Leave a Comment