Related
Release Notes 15.015.0
These release notes provide brief descriptions of changes included in eHarvest 15.015.0.
System Updates
Forms & Reports
DESCRIPTION | ID # | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Livestock: For the 2023+ years, the LGM Cattle Target Marketing form has been updated with more detail line information for the grower that displays in a detail line format similar to the detail line format used on the LGM Cattle Schedule of Insurance (SOI). |
142964 |
||||||||||||
Livestock: For the 2023+ years, the LGM Dairy Cattle Target Marketing form has been updated to always print the months in the correct order. |
144689 |
||||||||||||
Pomegranates: With this ticket, the System has been updated to correctly calculate the Age/Leaf Year for Pomegranates based on the updated Age/Leaf Year Calculation from RMA. The new formula is as follows: (X-Y) + 1 = Age/Leaf Year where:
NOTE: For this example, the set out/grafted date is after July 1, which will now place the set out/graft year to the year following the calendar year in which the set out/graft actually occurred (2015). |
144372 |
||||||||||||
SPOIs: 1/31 and 8/31 CCD SPOIs were updated and made available from RMA on Dec 22. The Special Provisions for 2023 have been downloaded and implemented in the System. |
144165 |
||||||||||||
SSN-EIN: This ticket cleaned up a some items on the base Social Security Number (SSN) and Employer Identification Number (EIN) Reporting Form; a few of the updates include:
|
142580 |
||||||||||||
MPCI App/Policy Change: This updated the Sprinkler Irrigated Rice (SIR) Endorsement Application that prints with main MPCI Application and Policy Change Form. During the 2023 DSSH review, it was found that items f and g, included below, needed to be added item #2 of the Good Farming Practices. Additionally, more information is included under each of these items when the form is printed. (f) Planning and implementation of a disease control program. (g) Planning and implementation of a water management program to meet the established evapotranspiration need of rice. |
139285 |
||||||||||||
PR: The Production Report has been updated in the following ways for all years:
|
135599 |
||||||||||||
Actuarial Change Request: During the 2023 Handbook review, it was found that the Request for Actuarial Change Form needed an update. With this update, additional base form standard updates were made. |
143204 |
Global
DESCRIPTION | ID # |
---|---|
The Online Help Site was updated with topics as well as with current release notes. |
145047 |
Mapping
DESCRIPTION | ID # |
---|---|
Updates were made to the import of precision yield records into mapping. Now, the import of the yield uses the harvested crop from the file, not planted crop, and includes the harvest date. |
145215 |
Users reported that fields were not displaying in the mapping Sync from ACRSI tab but did display in the ACRSI pages on the policy; this has been corrected. |
144418 |
MPCI
DESCRIPTION | ID # | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
HIP: Through development and internal research on TFS #128107 - Fast Edit Coverage - Add Ability to Add a New Coverage in the Fast Edit Coverage Grid (Phase 2), a way was discovered where users could theoretically apply Application Signature Dates to a coverage WITHOUT HIP Signature Dates. If a coverage has the HIP Crop Option applied, there are numerous validations across the Add New MPCI Policy, Add New Coverage, Maintain Coverage, and Fast Edit Coverage pages that mandate that HIP Signature Dates be keyed when the HIP Crop Option is elected. However, there is the possibility of coverages within the System being added through the Legacy Add New Coverage or even the new Fast Edit Coverage - Add New Coverage without Application Signature Dates being applied initially. Therefore, on subsequent return and processing of that coverage for Application Signature Dates, there had been existing copy logic that applies the Application Signature Dates keyed to the HIP Signature Dates. This ticket will now close this loophole and add this copy logic to the Legacy Signature Maintenance page to copy the HIP Agent & Insured Signature dates for the coverage marked IF the following conditions are true:
|
143965 |
|||||||||||||||
HR-ACE: For the 2023+ RYs, RMA has extended HR-ACE to Cotton (0021). With this ticket, support has been added for HB option on Cotton (0021).
NOTE: The System will not require the HB option to be on both coverages since this is the option that designates which of the coverages is HR-ACE and which is not.
|
139756 |
|||||||||||||||
Contracts: During the 2023 Fall Train the Trainer, RMA indicated that they will be expanding Contract Price provisions to other Tobacco Types beginning with the 11-30 CCD for the 2023 RY. With this ticket, the following Tobacco crops have been added to the existing Flue Cured Tobacco (0229) contract functionality: Burley (0231), Dark Air (0233), and Fire Cured (0230). For the 2023+ RYs, there will now be two price elections for Burley Tobacco (0231), Dark Air Tobacco (0233), and Fire Cured Tobacco (0230).
|
139758 |
|||||||||||||||
PTY: An issue was reported with PTY Summary Units on Corn with a type of Silage. Rounding of APH yields are based on the unit of measure. Silage has a unit of measure of tons, which, per the Crop Insurance Handbook, should round yields to the tenth. When the PTY summary yields are initially created, the System correctly rounds the approved yields and all other yields in the APH to tenths. If a user then selected to "Recalculate Personal T-yield", the System was updating all yields to round to the whole number instead of to the tenth. With this ticket, the System has been updated so that when a user is recalculating the PTY Summary units, the System will round the PTY Summary Unit yields to the tenths. |
140036 |
|||||||||||||||
SCO/SE: A bug was discovered internally on the Add New MPCI Policy and Add New MPCI Coverage pages where the "Include SE on SCO" flag was not being retained on New Cotton Coverages with SCO & SE. With this ticket, a code fix has been implemented so that the "Include SE on SCO" flag will be correctly set in the database when selected on the Add New MPCI Policy and Add New MPCI Coverage pages. |
144941 |