Release Notes 6.085.0

MPowerD: The previous provision document contained a cover page and should not have. The AIP provided a new document to replace the provision, which was added to the 6.085 release, so the manually-placed PDF in 6.080 was not replaced.

The default year was updated to 2018 on both the Private Product Premium Liability Report and the Private Products Recap Report.

eSign: A new dashboard, the eSignature Dashboard (Tools > eSign Dashboard), has been added to the System to allow users to view the status of ePackets. Additionally, a new option, "Remote", has been added to the eSign Options section on the Print forms page (on the Print tab for MPCI policies) so that users can select a policyholder signee(s) to send an ePacket to so that the selected forms can be remotely signed. These additions to the System will allow for policyholder signees and agents to remotely sign eSign-supported forms (i.e., where both parties are signing electronically but not in the presences of each other).

A request has been made to add the Farm Name to the Schedule of Insurance for Production Plan Hail policies. This enhancement will be a base change for all Crop Years for Production Plan products only. This change will affect the Schedule of Insurance in all printing areas. The following update was implemented on the Production Hail Application form: the Farm Name field was added below the Sect/Twshp/Range field on the form.

An enhancement was made to the Private Products view of the Claims & Inspections Register (Reports > Private Product Reporting > Claims Register) to add the Grower Intention column to the grid.

An update was made to the Print Blank Forms Application (Tools > Print Private Product Blank Forms) for Packer Citrus Freeze to print with the form number, "PCFAPP".

APH Database Form: This ticket implemented the Signature Authorization field on the Actual Production History (APH) Database Form plus a few other miscellaneous items to improve the form for growers and agents. These changes have been made:

MPCI Combo Form - ARH Database: MCT was made aware that the data printing in the 100% Rev field on the ARH page in the MPCI Combo Form was not correct. The data printed correctly in the stand-alone ARH Form. This ticket corrected the data printing in the 100% Rev field on the ARH page in the MPCI Combo Form.

Schedule of Insurance (SOI) & SOI / Production Report: Beginning with the 2018 RY, RMA has added a new procedure that allows growers to select to exclude acreage damaged by an unavoidable uninsured fire (UUF) and/or a third party. When a grower makes this election, the Acreage Report must be updated to indicate what acreage was damaged by an unavoidable uninsured fire (UUF) and/or a third party.

NOTE: This requirement is waived for 2017 UUF/Third Party Damage acreage.

RMA has added a new acreage type of "K – Unavoidable Uninsured Fire or Third Party Damage" to the Acreage Type ICE table (ICE D00142) to account for the reporting of UUF/Third Party Damage acreage. TFS #75004 in Release 6.040 added a description to the new Acreage Type of "K" that displays on the detail line, detail line drawer, and CLU grid. On the SOI and SOI/PR, the following changes have been made for all Crop Years:

The Forage UW and Acreage Report was updated to print the unit's reported uninsurable acres when the Acreage Reporting for the current year has been processed (i.e., there is an AR Sign Date) or if acres are entered and the user selects the "Print acres for acres entered" print option.

This ticket implemented some formatting standards to the Raisin Acreage and Tonnage Report and also completed some clean-up. All changes will be rolled out to the Raisin Acreage and Tonnage Report as base changes for all Crop Years.

"~ Indicate type of acreage being reported, see list of Acreage Types under signature fields on last page."

Through TFS #81393, the Private Product Policy Register (Reports > Private Product Reporting > Policy Register) was split into separate fields for First Name and Last Name when exported through Excel. The ability to also sort the Private Product Policy Register by First Name or Last Name was introduced in this ticket.

A 2018 Special Provisions update was made available by RMA on 1/16/2018 and 1/19/2018 and has been implemented in the System.

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

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

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

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

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

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

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

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

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

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

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

NOTE: Once loaded to production, MCT will run queries to determine if any Land IDs exist that have incorrect survey codes for URA and HR based on the new data.

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

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

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

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

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

EU by Practice: Beginning in 2018 for crops with a Filing Date of 11/30/2017 or later and for all crops in 2019, RMA is allowing growers to elect the EP unit structure on a single irrigation practice and elect a BU/OU unit structure on the another irrigation practice. For example, the grower can select EP on their irrigated land and OU on the non-irrigated land. To accommodate this change, the System was updated to allow for the selection of a practice on the coverage, EU/EP validation logic was revised, EU/EP override functionality was updated, and mark complete suspensions were updated. For more information, see RMA's White Paper on Enterprise Units by Irrigation Practice.

Margin Protection: The APH requirements for stand-alone Margin Protection policies were removed beginning with the 2017 RY. Prior to 2017, a standard APH with APH calculations was required for Margin Protection. TFS #77784 was implemented to hide the link for the APH on stand-alone policies since the APH was no longer applicable to the rating.

The scope of this ticket was to restore the APH-like records for stand-alone Margin Protection policies. This APH-like structure should be established for Plan 16 and Plan 17 Margin Protection. Since there are no ADMs that support an APH (e.g., no tyield, etc.), the APH-like record needs to merely store reported production and acres and annual yield. Standard APH logic will not be applicable. The APH structure was modeled from ARPI APH-like records that may be maintained for record keeping only.

Master Yields: With TFS #82980 in the 6.080 release, the Master Yield (MY) logic was updated for the new 2018 Yield Cup procedures. During internal testing of this ticket, two issues were found:

As part of the changes in the 6.080 release, logic was added to have the System determine the Prior Year Yield for auto-created MY Summary Units. However, this logic only worked if the policy existed in the System in the prior year. In the scenario of a transfer-in policy, the user needed the ability to set the Prior Year Yield in order for a Yield Cup to apply. In addition, the user needed the ability to set the Yield Cup Opt Out checkbox should the grower elect not to apply the Yield Cup to the MY Summary Unit even though it is the highest calculated yield.

With this ticket, the Yield Cup Opt Out checkbox was added to the MY Summary Unit page for both auto-created and manually-created MY Summary Units. Once the MY Summary Unit is created, the Yield Cup Opt Out checkbox will only display on the Summary Unit and will no longer display on the non-Summary Units. In addition, the page was updated to allow users to edit the Prior Year Yield and Yield Cup Opt Out checkbox on auto-created MY Summary Units.

Cup: The CIH states that cups are not applicable if the T-Yield decreases by 10% or more from one Reinsurance Year to the next. The APH calculation logic has been in place for several years to prevent use of the cup in the calculation of the Approved APH Yield when a T-Yield change occurs and a T-Yield is part of the calculation of the Approved APH Yield. The cup is applicable if there are 4 years' yields in the APH and change T-Yield is NOT used to calculate the approved APH yield.

In 2018 testing, however, it was determined the Prior Year Yield wasn't populated as expected during the roll, resulting in the APH logic in place not triggering the comparison between 2017 and 2018 RY T-Yields during the calculation process. Rather than address as a roll update, the code was refactored to make a comparison during the calculation that will determine whether a 10% or greater change has occurred, reading from the ADM and populating the DB field, APHPriorYearTyield.

With the deployment of this change, it will be necessary for a user to re-save the APH to trigger the logic and code changes implemented with this ticket. A query will be run to identify all 2018 RY APHs that have an Approved APH Yield greater than 0 that fall into a State/County/Crop where a T-Yield change of 10% or more occurred. AIPs will receive this listing so they can complete the manual re-save/underwriting review to ensure a cup wasn't applied incorrectly prior to February 2018.

New Producer: By design, the New Producer checkbox and PHTS selections have been available fields to edit for agency users beyond the standard lockout on the coverage page. Although these specific fields are designed to be outside of the coverage lock-out window, it was reported recently that agent users were unable to select the New Producer status when applicable. This ticket corrected the bug that took this access away.

This field is controlled by the production/acreage offset window established by the AIP. Once an agent user passes the production/acreage processing window for a crop, this access will no longer be available. For example, agents are typically beyond the lockout for production/acreage for fall crops so selection of New Producer for a fall crop should not be available.

An issue was found during internal testing of TFS #85365 where the Change Spring Coverage popup didn't have a date picker or date formatting (so the date had to be keyed correctly or the System wouldn't save it to the coverage). There were no messages presented to the user stating they had keyed the date incorrectly at save. To correct this issue, a date picker was added and the System now automatically formats the date similar to what is on other date fields within the System.

Primary County: During internal testing on a separate issue with "Is Primary County", it was found that after selecting the "Is Primary County" designation, if the user got an error such as "Duplicate coverage already exists" or "Please select a Crop Plan" or others, the "Is Primary County" selection changed back to "Select". If the user didn't notice it, they saved the coverage and the "Is Primary County" designation didn't get saved. The logic was updated to retain the "Is Primary County" designation when errors are thrown.

Peanuts: In the 6.080 release, with TFS #78808, the necessary changes were implemented to account for the 2018 Peanut policy changes. At the time of the 6.080 release, Peanut prices had not yet been released. For this reason, the Weighted Average Price calculation could not be tested. This ticket was created as a testing-only ticket to test the Weighted Average Price calculation once prices were released.

During internal testing of the Weighted Average Price calculation, a bug was identified around SCO child lines. The System was using the SCO child line Guarantee and Projected Price in the Weighted Average Price calculation. In addition, the System was applying the Weighted Average Price to the SCO child lines. Per the 2018 Peanut White Paper, the Weighted Average Price is only applicable to Plans 01, 02, and 03.

With this ticket, the Weighted Average Price calculation was updated to no longer consider SCO child lines in the calculation. In addition, the Weighted Average Price will no longer be applied to SCO child lines.

Written Agreements are not allowed on Margin Protection; however, Native Sod is applicable to Margin Protection. Current Native Sod functionality utilizes the Type 99 Internal Written Agreement, which, as a result, should have been allowed for Margin Protection. Only Native Sod will be applicable; New Breaking T-Yield Overrides are not applicable to Plans 16 and 17.

With this ticket, the Written Agreement logic was updated so only Type 99 (Internal Only) Written Agreements can now be selected for Margin Protection (Plans 16 and 17) coverages. A validation was also added at save to throw an error message if the user tries to select New Breaking rather than Native Sod. The message will read, "New Breaking T-Yield Override is not applicable to Plans 16 and 17."

A new Attachment Type, "STAX Documentation", was added to the MPCI menu in the Attachment dropdown.

An issue was identified internally when users tried to print after adding or editing a Power of Attorney or Authorized Representative on a policy. After saving, if the user tried to print a form, the System would act like it was going to print but the form never generated. Users would have to exit out of that policy and then open it again in order to print any forms. An issue was identified with OIDs in the JavaScript and corrected.

It was found that users were unable to add Production Hail to Wheat in Indiana or Ohio. The System was updated to make Wheat available for Production Hail coverages.