Related
Release Notes 15.005.0
These release notes provide brief descriptions of changes included in eHarvest 15.005.0.
System Updates
Entity Management
DESCRIPTION | ID # |
---|---|
Grower: An AIP requested that a hard stop validation be implemented to make the State of Incorporation required before saving the Grower/Grower for Policy page. The GSH requires the insured provide the State of Incorporation in writing on the application if the entity type is "Limited Liability Company" or "Corporation", but it is not a field that is required to be transmitted to RMA or that is required for any other processing. Rather than triggering a hard stop in which the user cannot move beyond, a pop-up warning has been implemented that inform the user when the State of Incorporation is blank. The user will be able to check "Yes" to continue saving without filling in or "No" remain on the page to key the field before save. |
142193 |
Forms & Reports
DESCRIPTION | ID # | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Some clean-up items on the Conservation Compliance Certification Form:
|
132976 |
||||||||||||
VFR: This ticket updated the Veteran Farmer and Rancher (VFR) Application with 2023 DSSH updates and other standardized updates. Some of these changes include:
|
139132 |
||||||||||||
BFR: This ticket updated the Beginning Farmer and Rancher (BFR) Application with 2023 DSSH updates and other standardized updates. Some of these changes include:
|
139140 |
||||||||||||
Livestock: The LGM Dairy Cattle Target Marketing form has been updated with more detail line information for the grower with a detail line format that is similar to the detail line format used on the LGM Dairy Cattle Schedule of Insurance (SOI) for the 2023+ years. |
141544 |
||||||||||||
Provisions: SPOIs were updated and made available from RMA on Oct 18. Special Provisions for 2023 have been downloaded and implemented in the System for Cotton (0021) STAX-RP (35) in TX (48) for the counties of Briscoe (045) and Floyd (153). |
142097 |
||||||||||||
Provisions: 2023 Walnut Crop Provisions have been implemented in the System. |
142396 |
||||||||||||
Provisions: 2023 Pomegranates Crop Provisions have been implemented in the System. |
142403 |
||||||||||||
Provisions: The RMA released 2023 Special Provisions for the 11/30 CCD on 11/16/2022. They have been downloaded and implemented in the System. |
142998 |
||||||||||||
Livestock: A request was received for the Conservation Compliance Certification form to be added to the Livestock Print menus. This has been added to the LGM / LRP Print and DRP Print menus for all Crop Years. |
142936 |
||||||||||||
Livestock: A request was received for the Conservation Compliance Certification form to be added to the Livestock Print menus. This has been added to the LGM / LRP Print and DRP Print menus for all Crop Years. |
142936 |
||||||||||||
Livestock: A request was made for the Beginning Farmer and Rancher (BFR) Application to be added to the Livestock Print menus; this has been done. |
136303 |
||||||||||||
Provisions: The RMA released 2023 Special Provisions for the 6/30, 11/30 and 12/31 CCDs on 11/23/2022. They have been downloaded and implemented in the System. |
143231 |
||||||||||||
Provisions: The RMA released 2023 Special Provisions for the 11/30 CCD on 11/28/2022. They have been downloaded and implemented in the System. |
143294 |
||||||||||||
Provisions: The RMA released 2023 Special Provisions for the 11/30 CCD on 11/30/2022. They have been downloaded and implemented in the System. |
143406 |
||||||||||||
Provisions: 2023 Cabbage Crop Provisions have been implemented in the System. |
142881 |
||||||||||||
Provisions: 2023 Chile Pepper Crop Provisions have been implemented in the System. |
142882 |
Global
DESCRIPTION | ID # |
---|---|
The Online Help Site was updated with topics as well as with current release notes. |
144385 |
Livestock
DESCRIPTION | ID # | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Livestock: An issue was reported where the System was incorrectly allowing the SSN Tax ID Type on the Irrevocable Trust Entity Type on Livestock plans. Per 2022 GSH Part 2 Sec 4 Para 258, EIN is the only accepted TIN Type for the Irrevocable Trust Entity Type. There must be separate and distinct policies if Individuals/Spousal operates as an Irrevocable Trust and no SBI with an entity type of "Irrevocable Trust" is allowed in combination with Individuals/Spousal. With this ticket, for all Livestock Plans, hard stop messages have been implemented on Grower and SBI pages and mirrors what is currently in place for MPCI:
|
139286 |
|||||||||||||||
Livestock: Within the Livestock Policy Management Dashboard (Livestock > Policy Management Dashboard), when LRP is the selected Plan AND the RY is 2023+, an update has been made to the navigation when the + icon in the Quick Links column in the grid is clicked for a policy. Previously, when clicked, the System would take the user to the Coverage tab for the policy. For the 2023+ RYs, the System will now take the user to the Add New Detail Line page for LRP. |
142147 |
|||||||||||||||
Livestock: Recent review of the existing Livestock Lockout functionality resulted in changes to be made for both LRP and DRP procedures. No changes are needed for LGM at this time. With this ticket, the following changes have been made:
|
143185 |
Mapping
DESCRIPTION | ID # |
---|---|
Users reported getting blank map books when printing using portrait orientation; this issue has been resolved. |
144431 |
MPCI
DESCRIPTION | ID # | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
FEC: The Fast Edit Coverage (FEC) page, implemented in 2021, allows users to modify multiple active coverage records at once instead of making individual updates on each record. The first phase of FEC development included coverage validations and the ability to apply Application Signature Dates through the Maintain Signatures popup. With this release, the FEC was enhanced to allow users to add a new coverage within the page. Now, a user can quickly add one or more new coverages which have the same State but different County, Commodity, Insurance Plan Codes, Type Codes, Practice Codes, Coverage Levels, Crop Options, or Price Election % values. However, most Exception Processing is not supported within the Fast Edit Coverage grid. To add a new coverage within FEC, from the Add New Coverage dropdown, select the county of the new coverage you are adding to the policy. A new coverage row, with the selected county shown, appears immediately below the last active coverage. Continue to make all necessary selections for the new coverage. Available fields may change based on your selections.
|
128107 |
|||||||||||||||
Fast Edit AR: An internal review of the Companion Policy functionality identified some opportunities for performance improvements when the Fast Edit AR is processed and a large number of companion units need to be updated. When Companion Policy links are updated, there are several things that need to be done during the syncing process. Previously these calculations were all performed in real time. With this ticket, the Companion Policy process was updated as follows: When the Fast Edit AR is processed for a coverage or multiple coverages where companion units exist, the following changes have been made to enhance the companion policy syncing process.
|
139375 |
|||||||||||||||
Policy: An issue was reported on the Add New Policy page. By default, the SBIs for the Grower are selected at the bottom of the page. However, it was found that if the user deselects the SBI(s) and then tries to save when an error is generated on the page for missing information or any other type of hard stop error, the checkmarks for the SBI(s) are being restored rather than staying empty. The checkboxes should remain unselected once the user has deselected them until the user goes back and re-selects them. This issue has been corrected with this ticket. |
141157 |
|||||||||||||||
WFRP: An enhancement was requested by an AIP concerning a possible WFRP (76) scenario. When Approved Revenue changes in a Previous RY and the Revenue Cup (RC) Option is elected in the current RY, the Prior Year Approved Revenue in the current RY is not updating. This is an issue because premium is affected in the current RY with RC and the Prior Year Approved Revenue figure. To help users with this issue, a new Mark Complete Suspension has been created to trigger when the scenario described happens for either WFRP (0076) and Micro Farm (9110) under the WFRP (76) Plan of Insurance. The following criteria all must be true in order for the Suspension to trigger.
|
141755 |
|||||||||||||||
Fast Edit PR: During internal testing, a bug was identified with the "Added Ins Acreage-Production Min" APH Override. By design, the System is supposed to apply the applicable Variable T-Yields to all years prior to the year of insurability to make 4 years of history. This allows uninsurable production/acreage to remain in the APH but no annual yield is calculated for those years. It was found internally that if production was updated via the Fast Edit Production Reporting page, the System was retaining additional Variable T-Yields rather than rolling them out as actual history is added. This ticket updated the APH logic for the "Added Ins Acreage-Production Min" APH Override to ensure the Variable T-Yields correctly roll out of the APH, as needed, whether production is updated through Fast Edit PR or the Legacy APH page. |
142836 |
|||||||||||||||
Pomegranates: An issue was reported where the Pack Out Average within the Pomegranate APH was not rounding to the nearest whole percent. With this ticket, the System has been updated to now round the Pack Out Average to the nearest whole percent for Pomegranates. |
144076 |
|||||||||||||||
Potential Loss Estimator: During internal testing of the Loss Estimator Price Maintenance tool (Tools > Loss Estimator Price Maintenance), it was found that the Update button was not working as expected. When a user clicked Update, the System was not saving the price entered by the user like it should have. This issue has been resolved. |
144119 |