Release Notes 7.085.0

Previously, the Total Acres in the Coverage Summary and the Premium Summary sections on the Schedule of Insurance (SOI) and SOI / Production Report were displaying duplicate acres when Rice with the Downed Coverage (DC) Endorsement lines were entered. The Crop Summary and Premium Summary sections was updated to not include Downed Commodity Endorsement detail line acres in the Coverage Acres on the Schedule of Insurance (SOI) and the SOI / Production Report.

With the 2019 Crop Insurance Handbook (CIH), RMA removed Prevented Planting +10% (PT). The Schedule of Insurance (SOI) form has been updated in the following ways:

RMA released a Nursery Price Endorsement Provision for 2006 and succeeding Crop Years (CYs), and it has been added to the System. The Nursery Crop Provisions will now print the Price Endorsement Provision when a Nursery coverage has the PO option elected for the 2006 CY. Provisions print with the MPCI Policy Declaration page when the option to print provisions with the form is selected. The MPCI Policy Declaration page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

RMA released updated Hybrid Seed Rice provisions for the 2019 and succeeding Crop Years (CYs). Provisions print with the MPCI Policy Declaration page when the print option to print provisions with the form is selected. The MPCI Policy Declaration page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

In an effort to create a seamless, easy way to contact the AIP, the AIP has moved to one toll-free phone number and one toll-free fax number. The existing local regional office phone numbers will remain the same. The Phone and Fax Numbers on all of the AIP's Processing Regions as well as the Livestock information that prints in the AIP Contact Info section on forms—typically in the top-right corner on the form pages—have been updated. The new Phone Number for all Processing Regions is: (800) 366-2767, and the new Fax Number for all Processing Regions is: (800) 306-3038.

It was found that a duplicate Email Address was printing on the Production Reporting Worksheet Page 1's header in the Agency and Agenct Information Section—the Email Address was printing under the Mailing Address as well as the Email field. The Production Reporting Worksheet has been updated for all years to not print the duplicate Email Address under the Mailing Address in the Agency and Agent Information Section in the header on Page 1.

The Online Help Site was updated with topics as well as with current release notes.

myHudson Agent Dashboard: A new Reinsurance Year filter has been added to the myHudson Agent Portal Dashboard. Every report panel except for the Commissions and Premium History panels have been updated to show one RY only. This includes the report panel charts that previously toggled between Reinsurance Years. From this point forward, users will need to change the RY filter selection in order to see data for different Reinsurance Years. The Premium History and Commission report panels will continue to show all RY data as a summary type of view—those panels should not change when different Reinsurance Years are selected from the filter.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When adding an Authorized Signature to a Livestock policy from the View Grower by Policy page, the user was receiving a "Page Not Found" error. Users were only receiving this error for Livestock policies—no other policy types were affected. The code has been corrected so the page navigates as expected now.

SBIs: When creating a new policy, if there is a prior year policy for the same state that has not rolled to the current year, the System will display a dropdown to allow the user to select the prior year policy on which to create the new current year policy/coverage. When this functionality is utilized, the System effectively rolls the policy into the new year, including any SBI records. And, when creating a new policy in the current year, if other policies exist in the current year for the grower, an SBI Information section displays at the bottom of the Add New MPCI Policy page that allows the user to select SBI records to copy when the new policy is created.

While these two pieces of functionality cover most scenarios, a gap was identified in the functionality to copy SBI records when creating a new policy. This gap occurred when a current year policy did not exist and the user did not select a prior year policy number when creating the policy. To account for this gap, with this ticket, functionality was added to copy SBIs when creating a new policy under a new policy number. So long as a prior year policy is not selected, when creating a new policy, the System will display SBI records from the prior year policy for selection. Any SBIs selected will be copied to the new policy on save.

Grower: An enhancement request was received that users be given a warning message upon initial save of a grower record if the grower record is created without an email address. The Add New Grower page has been updated in the following ways:

NOTE: The E-Mail Address field will NOT be a required field for a grower record.

Fast Edit PR: In TFS #98706, it was discovered that users were not able to enter production for stand-alone MP policies due to lockout. The workaround at the time was to process one coverage/plan at a time in the Fast Edit PR and then the user could return to the Fast Edit PR and process the second coverage and the user wouldn't be locked out. When this was fixed in the 7.075.0 release, it was then noticed that the Fast Edit PR Current Year Production Reporting sign dates were not displaying on the Detail Line or legacy Signature Maintenance pages. This issue could be duplicated in Area Revenue (Plans 04, 05, and 06), Stand-Alone Margin Protection (Plans 16 and 17), and Stand-Alone STAX (Plans 35 and 36) policies where Current Year Production Reporting has been keyed in the Fast Edit PR and sign dates have been applied within Signature Maintenance.

A fix was done for Plans 04, 05, 06, 16, and 17 (standalone) and 35 and 36 (standalone), so that, if Current Year Production is keyed in 2018 RY with signature dates applied, then the System will pull the Production Report Date from the ProductionReported table and the dates will display on the View Detail Line and Signature Maintenance pages for the Production Report for the 2018 RY.

Signature Maintenance: With TFS #98706 it was discovered that users were not able to enter production for stand-alone MP policies due to the lockout. The workaround at the time was to process one coverage/plan at a time in Fast Edit PR and then the user could return to Fast Edit PR and process the second coverage and wouldn't be locked out. When this was fixed in the 7.075.0 release, it was then found that within the legacy Signature Maintenance functionality the wrong Production Reporting Date was displaying. Beginning in the 2019 RY, the ADM is now including Plan Codes 04, 05, and 06 as well as stand-alone policies for Plan Codes 16, 17, 35, and 36 with a published Production Reporting Date. All other Plan Codes have an internally-calculated date that displays on the user interface. Plan Codes 04, 05, 06, 16, 17, 35, and 36 should have been designed to always pull directly from the ADM and not use the System-calculated date. The System was updated to have the UI display the correct Production Reporting Date for Plan Codes 04, 05, and 06 as well as stand-alone Margin Protection (Plans 16 and 17) and stand-alone STAX (Plans 35 and 36); this Production Reporting Date will be pulled from the ADMs and not the System-calculated date within the legacy Signature Maintenance page for Production Reporting.

WFRP: In TFS #97361, logic was implemented to populate the SCD Approved Revenue and the SCD Approved Expense fields within the Income/Expenses tab on a WFRP policy in order for the values to print on the Farm Operation Report even after a Revised Report has been submitted. During UAT, it was found that the SCD Approved Revenue and Expenses fields were populating as expected but the values were not updating accordingly.

A fix was done so that the SCD Approved Revenue will be the lesser of the Historic Average Revenue or the Total Expected Revenue, calculated using intended commodity values only, and that SCD Approved Expense calculation will depend on whether the Historic Average Revenue or the Total Expected Revenue applies.

Fast Edit PR: During testing of TFS #98777, where related Margin Protection coverage premium lines were not displaying in Fast Edit PR, an issue with the Signature Maintenance page was found. On the Fast AR Signature Maintenance page, Margin Protection coverages with a related coverage do not display in the Signature Maintenance grid. However, in testing of #98777, it was found that Margin Protection coverages with a related coverage are displaying in the Fast Edit PR Signature Maintenance grid. By design, these coverages should not have been displaying.

A fix was done in order for the System to no longer display the Margin Protection coverage (Plans 16 and 17) with related coverages on the Fast Edit PR Signature Maintenance grid.

WFRP: Due to an accidental removal of code that was done in TFS #97361, this ticket was opened to again re-implement this same code. In TFS #97360, the System was updated to add two new database fields in the AgrIncomeExpense table to store the SCD Approved Revenue and SCD Approved Expenses. This ticket will update the System to populate these new database fields in the Add New and Maintain Income Expense page for them to print on the Farm Operation Report even after a Revised Report has been submitted.

Prior to these changes, there was only one database field for the Approved Revenue and Revised Approved Expenses and the values were updated when a Revised Report was keyed. Once the Income and Expense Record was updated with the revised values, the Approved Revenue and Approved Expense values in the database were updated to the revised values. With the addition of the new SCD Approved Revenue and SCD Approved Expense fields, the System will continue to populate the existing Approved Revenue and Approved Expenses database fields as they are currently since these fields are used for premium calculations. In addition, the System will populate the new fields with the Approved Revenue and Approved Expenses at the sales closing.

Coverage: In TFS #96626, it was discovered that when the user was selecting OK to the pop-up question of "Primary County Election already exists on Policy … for the selected Grower and Crop. If you would like to remove the existing designation(s) and apply it to the current coverage, please select ‘OK’ (change will be made when current coverage is saved))", the changes were not correctly taking effect. The System was not removing the current "National" Primary County selection on noted policy number and then setting new policy as the new Primary County—it was incorrectly setting both policies with the Primary County equal to "National". During internal testing of this ticket, it was found that, for Margin Protection (Plans 16 and 17) and STAX (Plans 35 and 36) plan codes, the System was not triggering the popup as it was for Plans 01, 02, 03, and 90. The Plan Code should only be taken into account for Margin Protection and STAX and not the other plan codes when the Primary County Election flag is set.

A fix was done so the System to correctly set the Primary County flag when the user selects "OK" to the popup and wishes to change the Primary County election from the current policy to the new policy being added via Add New MPCI Coverage.

Margin Protection: An issue was found during the testing of TFS #93227 for High Risk (HR or HB) 2019 RY+ acres insured on base coverage that are not insurable under the related Margin Protection coverage. If a user has selected (or does select) a Type on the Margin Protection coverage (Plans 16 or 17) and then also keys a base coverage (or the base coverage already exists and a change is elected), upon save, the user will receive a pop-up warning: “Since this crop has been elected to be insured by type all coverages for this crop must have a Crop Type selected”. This warning was being received within the Add New and Maintain Coverage page. Then, when the “Type” was removed from the Margin Protection coverage, the pop-up warning was no longer received on the base coverage.

The System was updated so the warning message is no longer received if a Type has been keyed on the Margin Protection coverage (Plans 16 or 17) and a base coverage exists.

Grower: An issue was found internally where a label on one of the pages of the Create New Grower popup (i.e., the Grower Wizard) displayed "Select Agent" when it should have displayed "Power of Attorney" when a Power of Attorney existed on the coverage. The label on the Power of Attorney selection page of the Grower Wizard has been updated to read "Power of Attorney" rather than "Select Agent".

WFRP: An issue was found during internal testing of the premium on a WFRP policy. In #TFS 51771, there was a suspension added to suspend policies when a grower has a WFRP policy but an MPCI CAT coverage also exists for the same grower. To be eligible for a WFRP policy, a grower must elect buy-up coverage for any crop they insured under a separate MPCI policy. If a CAT MPCI coverage exists at the time for any crop covered by the WFRP policy, the grower is ineligible for a WFRP policy. The issue that was found was where the WFRP policy is suspending due to a CAT coverage level policy existing for the grower and the coverage is a canceled policy with all coverages showing as "Canceled".

A fix was implemented so a suspension is no longer received on a WFRP policy if an MPCI CAT coverage exists but is a canceled coverage. The System should not look at canceled coverages during mark complete for this suspension.

When adding additional coverage to a linked Private Product policy, the premium was not calculating. An update was made to correct this issue.