Related
Release Notes 9.060.0
These release notes provide brief descriptions of changes included in eHarvest 9.060.0.
System Updates
Forms & Reports
DESCRIPTION | ID # | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Pecans: This ticket updated the Revenue Report, for all years, to help the form be more customer friendly. Some of these changes include:
NOTE: The base form standard updates were not made to this form with this ticket but will be made in a future ticket. |
21024 |
|||||||||||||||||||||||||||
Pecans: This ticket updated the Summary of Revenue History with the 2021 DSSH updates, namely removing the Statement Page. It was also found that a few other updates were needed to help the form be more customer friendly.
NOTE: The base form standard updates were not made to this form with this ticket but will be made in a future ticket. |
21025 |
|||||||||||||||||||||||||||
PAW: The following updates have been made to the Hawaii Tropical Fruit (HTF) and Hawaii Tropical Trees (HTT) formats of the Producer's Pre-Acceptance Worksheet (PAW) for all years: HTT PAW Updates:
HTF PAW Updates:
|
120520 |
|||||||||||||||||||||||||||
DRP TOR: The following updates have been made to the Transfer for Rights for Indemnity Form (TOR) for the Dairy Revenue Protection (DRP) Livestock product for all Crop Years:
|
121848 |
|||||||||||||||||||||||||||
LGM TOR: A Livestock Gross Margin (LGM) Transfer of Rights to Indemnity (TOR) form was added to the LRP and LGM Print menu. The following updates have been made for all years:
|
121849 |
|||||||||||||||||||||||||||
LRP TOR:A Livestock Risk Protection (LRP) Transfer of Rights to Indemnity (TOR) form was added to the LRP and LGM Print menu. The following updates have been made for all years:
|
119051 |
Global
DESCRIPTION | ID # |
---|---|
The Online Help Site was updated with topics as well as with current release notes. |
120931 |
Livestock
DESCRIPTION | ID # |
---|---|
LRP Estimates: An enhancement request was received to add the ability for users to email quotes generated from the Create Quick LRP Estimate tool. With this ticket, a new button, Email Estimate, has been added to the Create Quick LRP Estimate tool. This button will only appear once data have been keyed and the Calculate button has been clicked. This new button will display next to the existing Print Estimate button and will allow users to enter the email address for the recipient along with a personal message, if they so choose, before sending the estimate via email. Users will also need to enter their own email address in the CC field, as the emailed estimates will not be stored and will no longer be accessible in the System once sent. |
105863 |
Mapping
DESCRIPTION | ID # |
---|---|
Perennials: This ticket added additional fields to the single field Planting Dialogue for Perennial crops. This ticket will be followed with updates to the Fast Edit Planting and Sync to PAW functionality (future tickets). |
90660 |
Checkboxes were recently added for Land ID/Planted CLU functionality to indicate when a field was brought in from a neighboring county (i.e., with PRF). This ticket will update Sync to AR and Sync from AR to account for the flag when a field is included that is not physically in the county of the coverage (i.e., grid ID crosses county lines and field is in different county from the coverage). |
122479 |
MPCI
DESCRIPTION | ID # |
---|---|
PRF/Apiculture: A scenario was reported where the CLU applicable to a PRF or Apiculture policy was in a different state or county than the State/County on the coverage. While the System would allow the user to key the FSN/Tract, when they selected to add Fields/CLUs, the System was not pulling in any Fields/CLUs since the FSN/Tract was actually in a different county. To resolve this issue, dropdowns for State/County have been added to the Field/CLU section of the Manage Land IDs popup directly under the CLU/RLU tabs. These fields will default to the State/County on the coverage but allow the user to select a different State/County as applicable. When a different State/County is selected, the System will populate the Fields/CLU grid with the Fields/CLUs for the FSN/Tract in the selected State/County in addition to the Fields/CLUs for the FSN/Tract in the State/County on the coverage. Any Fields/CLUs from the State/County that are not on the coverage will be shaded/highlighted to help the user differentiate between Fields/CLUs in the selected county and those in the county on the coverage. Finally, Location State and Location County dropdowns have also been added to the Edit CLU Information popup (accessed by clicking the fields number link) to allow the user to designate a Location State/County different that the admin State/County. These change are applicable to PRF and Apiculture only. NOTE: The new State/County dropdowns on the Manage Land IDs popup will become read-only once the user has selected and saved a CLU from another State/County. In order to edit the State/County dropdowns again, the user must deselect any CLUs from another State/County and then re-save. At this point, the State/County dropdowns will become editable again. |
115884 |
Perennials & Fast Edit PR: An issue was reported within the Fast Edit PR for Perennial crops. When a policy with multiple Perennial coverages with different Types was updated with production but only one of the coverages was being selected for processing, the System was not updating the APHs accordingly. Upon save of the Fast Edit PR grid, the System should have updated both the PAW and the calculated Approved APH yield for the selected coverage. However, the System was only updating the PAW and was NOT calculating an approved APH for the coverage. A fix was implemented within the Fast Edit PR grid, so that upon save, the System is correctly updating both the PAW and the calculated Approved APH Yield for the selected coverage. |
122227 |
CIMS: An issue was reported where the CIMS Request checkbox was not being set (selected) on the initial save of the Add New Policy and Add New Coverage pages. The System was requiring a second save of the Maintain Coverage page (after the Add New Policy page was initially saved) to default the CIMS Request checkbox as expected. A fix was implemented that will default the CIMS Request checkbox to selected when a New Policy or New MPCI Coverage is created. |
122175 |