Release Notes 8.025.0

The 2019 Loss Adjustment Manual (LAM) had an update to the Acceptable Farm Management Records from Producers using Precision Farming Technology Systems (PFTS) Section 821.I.2.b.iii. The following base changes on the PFTS were made for all Crop Years:

In the 2019 LAM Section 2.b.iii, the verbiage above was changed to the following: "FSA farm/tract/field ID number, if applicable;".

A navigation issue was reported where, when working within the Print tab of a policy, if the user selected to print an APH Database form as well as the Schedule of Insurance with the Auto Attach option selected, the user was taken back to the Batch Print page instead of the System printing the forms and attaching the SOI.

During research it was found that users are prevented from printing an SOI with the Auto Attach print option when printing other forms. An error message is coded in to prevent this from happening, but the code was looping through other logic first and essentially bypassed the "Official Schedule of Insurance cannot be printed with other reports" error. With this ticket, this logic has been updated so the user is given the hard stop error message when trying to print the SOI with Auto Attach option with another form.

For the Transfer of Coverage and Right to an Indemnity (TOR) form, the 2020 DSSH updated the "I understand..." verbiage. The following updates have been made to this form:

Attachments: When scanning and attaching paperwork within the System, the current attachment popup requires that agents scroll to select the applicable attachment type. A smart search feature has been added that allows the user to begin typing the attachment type in the Attachment Type field and the System will navigate the user to the attachment name for selection. This smart search feature may be used in place of a user scrolling to find the attachment type in the list of available attachment types.

Companion Policy: An issue was found internally while testing another companion ticket. In the popup that appears when a companion link is hovered over, it was found that, if the Grower Name contained a comma or was long in length, only a portion of the name was displaying due to text wrapping. For example, "MyCropTech Test Farms, LLC" was only displaying as "LLC" in the popup. This logic was updated to display the full name when commas or longer grower names are used.

Companion Policy: An issue was found with an incorrect unit structure on companion policies when revisions were made on the source policy. The issue was due to a full save not being performed on the companion policy detail lines. After processing the acreage changes on the source policy, the user went to the companion policy to apply AR Sign Dates and complete the detail lines but none of the companion policy lines were marked as modified so the System didn’t perform a full save on the detail lines, which caused the unit structure to not get updated. When a companion premium line is updated due to data being changed on its source premium line, the System now checks to see if the Unit Structure (UnitOptionCode) needs to be updated as well.

Perennials: RMA issued a new policy for Caneberries in the 2019 Reinsurance Year. Caneberries are a lag year crop so lag year functionality will be implemented as part of this ticket. In addition, as part of the Caneberry policy, a Summary Yield APH, similar to a PTY Summary Unit, will be created using the history from the 4 most recent crop years, excluding the lag year. The history from the Summary Yield will then be used to complete up to four years of history in any non-summary APHs. This ticket implemented the functionality for the Summary Yield as well as the lag year and other standard APH functionality for non-summary APHs for Caneberries. The following updates were made:

NOTE: A few issues were found during internal testing of this functionality. TFS #107435 has been set up to address the following issues: 1) The message stating the Summary Yield must be recalculated following changes to the non-summary units is not displaying; 2) The option to create a Summary Yield is not consistently displaying in the Additional Functions dropdown even when 4 years of continuous history exist; and 3) The System is not calculating an approved yield on the non-summary yields consistently, even when 4 years of history exist and/or a Summary Yield exists.

Perennials: RMA issued a new policy for Caneberries beginning in the 2019 RY. While Caneberries are a Category B crop, they are not an annual crop. Given this, the detail line functionality now allows a plant date outside of the current RY. In addition, standard Plan 90 rating functionality applies to Caneberries. Finally, in order to qualify for a Caneberry policy, the four most recent years of continuous history, excluding the lag year, must be provided. A suspension was to notify the APH when this history requirement is not met. With this ticket the following changes were made. These changes were made with this ticket.

NOTE: During internal testing a few bugs were identified. First, the suspension requiring 4 years of continuous history for the Commodity Type is not working. TFS #107493 has been set up to address this issue. In addition, the approved yield is not calculating. TFS #107435 has been set up to address this issue. Because of the approved yield issue, premium cannot be tested at this time. Testing of the premium calculations will also be handled under TFS #107435.

IDALS: During internal testing, an issue was found with IDALS Subsidy values existing in the database on zero acre detail lines. Detail lines logic has been updated to remove the IDALS Subsidy value from the database on save of the detail line if acres are updated to zero.

Written Agreements: There are 2 ADM Guarantee Adjustment tables that are referred to as A01220 tables. One is a WA ADM Guarantee Adjustment Table (A01220) and one is a standard ADM Guarantee Adjustment Table (A01220) which also sometimes has WA detail included. The first file referenced always comes to AIPs as part of the WA ADM_ICE file received from RMA; this file contains 24-30 different tables. The scope of this ticket changes the WA rating logic to look at the WA ADM Guarantee Adjustment table for all PP logic. If a record is not found in the WA ADM Guarantee Adjustment table for the RY, WA #, State, County, Crop, Plan, Type, Practice, and Map Area, the System will look at the Standard (non WA) ADM Guarantee Adjustment table for verification. If data is not in either table, the System will determine PP is not applicable.

NOTE: RMA references the ICE Guarantee Adjustment table for late plant and max late plant and the ADM A01220 for PP only.

Because of the previous logic, AIPs/Agents were prevented from entering a PP designation on a Written Agreement detail line where the Written Agreement had not excluded PP coverage.

Quotes: An issue was reported where the Select Practice for EP field was not displaying on the Add New Quote page. This was causing issues when the quote was converted to a policy because the practice for the EP field was populated as NULL in the database. With this ticket, the Select Practice for EP field has been added to the Add New Quote page.

NOTE: This field only displays when Enterprise Units by Practice is elected on the coverage.

MCEU: In the 2019 RY, RMA issued a Contiguous County ICE table to assist AIPs in determining which counties were contiguous for purposes of MCEU. Beginning in the 2020 RY, RMA is forgoing the ICE table and issuing a Contiguous County ADM table. With this ticket, MCEU logic has been updated to use the Contiguous County ADM table for 2020+ RYs in place of the Contiguous County ICE table. The System uses this table to determine which coverages should display in the Related Coverage dropdown in the Manage Unit Structure popup when MCEU is elected.

Annual Forage: As part of the Annual Forage updates for the 2020 Reinsurance Year (RY), RMA issued a new Dual Use (DU) option. The majority of the functionality for this new option was implemented in the 8.000 release with TFS #102178, and the remaining rating functionality was implemented in the 8.015 release with TFS #103939. However, at that time, testing could not be completed due to incomplete ADMs. This ticket was set up for testing of the Annual Forage Rating functionality once ADMs were available. RMA has issued the necessary updates to the Price ADM table, so the Annual Forage Rating functionality could be tested. Testing was completed successfully.

NOTE: Due to an issue with ICE D00162 Planted Date Range, users will receive a hard error on save of an Annual Forage detail line with a planting date in the 2020 RY. This ICE table currently lists the same date ranges in the 2020 table as are listed in the 2019 table. Once RMA updates this table on their end, users will have the ability to enter valid dates. RMA has been notified of this issue with their ICE table.

New Crop P/T: During UAT of the new lockout functionality that separates the PRD and ARD lockouts, an issue was found with adding New Crop P/T APHs. With the implementation of a PRD specific lockout date, agency users are locked out of editing all APH- and production-related page following the PRD plus the offset number of days. The one exception to this is that agency users will be allowed to create new APHs until the ARD lockout date so long as the APHs have an override of Added Land or New Crop P/T.

The issue identified during UAT of this functionality is that users were sometimes receiving the lockout message when attempting to add a new APH for New Crop P/T. When an override of New Crop P/T is selected, the system determines the Simple Average T-Yield and compares it to the T-Yield. If the Simple Average T-Yield is higher, the System applies the Simple Average T-Yield and the New Crop P/T Override remains on the APH. However, if the System determines the T-Yield is higher, the T-Yield is applied to the APH and the New Crop P/T Override is removed. It is this second scenario where the users were receiving the lockout message. Since the System was removing the New Crop P/T override, the lockout functionality was not seeing the APH as a New Crop P/T or Added Land APH and throwing the lockout error. With this ticket, the lockout functionality was updated to allow a New Crop P/T APH to be created up after the PRD lockout date and until the ARD lockout date, even when the override is removed by the System. So long as the override is originally applied, the System will allow the user to create the APH.

Forage Underwriting Report: While researching an issue on the Forage Underwriting Report with TFS #99514, it was discovered that an error was being thrown within the Forage Underwriting Report when selecting Add MPCI Detail Line. This issue has been resolved, and the System will no longer throw a "Sorry..." error when a user selects Add MPCI Detail Line within the Forage Underwriting Report.

Forage Underwriting Report:While researching an issue on the Forage Underwriting Report with TFS #99514, it was discovered that during the initial save of data on the Forage Underwriting Report, if acres were ALL Uninsurable, these acres were not being pushed to the detail line. This issue has been resolved, and the System will now push the Uninsurable acres to the detail line accordingly from the Forage Underwriting Report.

ICE: The Increased Coverage Election - AY option has been updated to include the crop, Almonds. Users will now be able to create an ICE policy from an associated qualifying MPCI Almonds coverage to add the Private Product to. The pages have now been updated to capture the unit of measurement for Almonds on these policies as well as the rating for Almonds.

On Private Products, the Refresh Log previously logged messages to let users know if acres had been imported or if the acres were prevented from importing to the Private Product policy for any reason. The logged messages for this have been updated to include where the imported acres originated from. For instance, the Refresh Log will tell the user if the acres were imported brought in because of Mark Complete, Submit Acreage, a Suspension being released, etc.

A 2015 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2015:

A 2015 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2015:

A 2016 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2016:

A 2016 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2016:

A 2017 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2017:

A 2017 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2017:

A 2018 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2018:

A 2018 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2018:

A 2019 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2019:

A 2019 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2019:

A 2020 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2020:

A 2020 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2020:

A 2020 ICE update was made available by the RMA and implemented in the System. The following tables have been updated for 2020:

A 9999 ICE update was made available by the RMA and implemented in the System. The following table has been updated:

A 9999 ICE update was made available by the RMA and implemented in the System. The following table has been updated:

An ADM 2020 update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2020:

An ICE 2020 update was made available by the RMA and has been implemented in the System. The following table has been updated for 2020:

An ICE 2019 update was made available by the RMA and has been implemented in the System. The following table has been updated for 2019: