Highlights This release includes a couple of new features and fixes some issues handling contracts with one year contract lengths. One of the new features included in this release will add a contract to a MRV project. The MRV’s Northern Plains Cropping (NPC) had a contract and will now utilize this one year contract in the MRV and AdobeSign. Another feature included in this release will change the MRV’s behavior.…
Highlights This release does not include any new MRV features. The NACD SGP Market project had its contract added into the MRV and will now utilize a five-year contract. The MRV will now utilize this contract dynamically and will be the pdf the producer signs in AdobeSign. The full list of release notes has been included below. Added Features The NACD SGP Market project was updated to a five year…
Highlights This release includes the AdobeSign capability. Now, the MRV will utilize AdobeSign documents for its Producer Agreement. The restriction on 2023 producer agreements and onwards has been removed from the MRV. All producers can utilize the AdobeSign regardless of their enrollment/collection year. The MRV no longer has a default contract. Only certain projects have a contract linked and utilized. If a producer is in a project without a contract,…
Highlights This release contains a couple of fixes while the MRV’s AdobeSign work is integrated into other parts of the MRV. Users will notice a couple of behavior changes in the MRV’s Fields and Practice Changes module. When a producer has a field marked with the conversion of cropland to grassland practice change and the “associated areas” are outside of the expected field acreage range, the MRV will ignore the…
Highlights This release contains multiple fixes along with a couple of new items. Fields created in the MRV will now be automatically tied to the correct program region. As users save or edit fields, the field record will store the appropriate program region. If the field overlaps multiple regions then the MRV will take the largest overlap as the region value. Another change included in this release adds another status…
Highlights This release contains mainly changes dealing with the MRV’s stratification capabilities. The MRV will now have a stratification service hosted on Azure and this service will be connected to the application. Once a producer’s Fields and Practice Changes Review has been marked as approved, the appropriate fields will automatically be sent to the stratification service. The service will run these fields in a secluded batch and will store the…
Highlights Text Added Features The MRV’s Fields and Practice Changes Review process has been fully integrated into the application. There will be additional updates to add validation as needed. Once the MRV’s upcoming AdobeSign Contract is integrated, there will be additional updates to handle a field’s QA/QC outside of the initial year, which reduces the amount of checks done. The producer will submit their Fields and Practice Changes module (click the…
Highlights This release contains a couple of new features and fixes but mainly changes how the MRV’s behind the scenes process works. The MRV’s development process has been updated to allow easier tracking between pushed changes. Migration scripts can no longer alter existing database views or functions. The MRV will now have its views and functions in a source file. Going forwards, the migration can only be used to update…
Highlights This release contains a couple of new features and multiple fixes. One of the new features admin and staff will notice is the ability to add soil samplers. This MRV role has been added and allows the sampler to be linked to multiple projects. This role is restricted to only being a “sampler” role and users cannot be assigned this role unless they have been already assigned as a…
Highlights This release continues the needed work for supporting the MRV’s “Conversion of Cropland to Grassland” practice change. Multiple issues related to this practice change and its “associated areas” have been resolved with this release.This release also adds additional validation after the Crops module has been completed. Users will complete their Crops module and then will submit their data. At the submission, the MRV will run a validation check to…