Release Notes 6.055.0

eSign: The APH/AR APH Database and Acreage Report has been modified and enabled for use within the eSign Wizard. For this form, the eSign Wizard will:

The report styles available for the form when using eSign are "Pre-Filled" and "Pre-Filled with Land ID". "Pre-Filled with Land ID" is the default selection.

Perennial Combo Form: During internal testing of TFS #76468, some inconsistencies were found with print options. With this ticket, the "Include Extra SSN and EIN Reporting Page" print option is now displaying for every report style. Also, blank lines now print on the SSN / EIN page with the "Pre-Headed w/ Insured and Agency info" report style as they do on the "Pre-Filled" report style.

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:

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

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

A 2018 ADM 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 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 tables have been updated for 2015:

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 tables have been updated for 2016:

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:

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

Fast Edit PR: An issue was found with the current year production roll logic for Skip Row Cotton. When production is keyed via the current year production reporting grid in Fast Edit PR, it is stored in a staging table and rolled to the APH when the policy rolls to the next RY. An issue was found where the total production for Skip Row Cotton was rolling to the net production field on the APH rather than the gross production field. The current year production roll logic for Skip Row Cotton has been updated to roll production to the gross production field.

Perennials: During internal testing, a bug was found where Perennial crops covered under the Davis RO were not utilizing the RO UG for High Variability-Trending specified in Section C, Par 1. Per the 2018 Davis RO UG, the guidelines are applicable to 2019 CY Citrus, Avocados, and Macadamia Nuts and all 2018 CY Category C crops in AZ, CA, HI, and UT.

System logic has been corrected to apply 2018 RO UG for High Variability - Downward Trending to 2019 CY Citrus, Avocados, and Macadamia Nuts and to all 2018 CY Category C crops in AZ, CA, HI, and UT.

If an APH database meets the standard downward trend testing guidelines from 2018 CIH Par. 1862 E:

APH: An issue was found in the APH where, for the 2018 RY, the Yield Used field wasn't consistently populating (display issue) and was not being used in the Approved Yield if YE applied. This has been corrected.

Perennials: System logic was updated to only allow the APH Override of "Organic Transitional T-Yld" if less than four years of Actual/Assigned Yields exist in the database. Then, if selected, the Yield Override field is available and 100% of the value entered into the override field is applied to the Current Year T-Yield field and the most recent one to four years of non-actual yields in the database necessary to complete the four year base period. The Yield Type of "OF" will be applied to the most recent one to four years of non-actual yields in the database necessary to complete the four year base period.

NOTE: When less than four years of Actual/Assigned yields exist in the database, the Override value and "OF" Yield Type will be used to complete the four year base period.

The Yield Type of "OF" cannot be preceded by Actual/Assigned Yields in the database ("OF" cannot follow Actual Yields). For example, if an Actual/Assigned Yield exists in Yield Year 2017, the "OF" Yield Type cannot exist in 2018 and later; the "OF" Yield Type can only exist in 2016 and prior.

Transmissions: In the 6.050.0 release, TFS #74949 added stand-alone Margin Protection (MP) production reporting logic to the existing ARPI/stand-alone STAX grid. Margin Protection written as a stand-alone policy has a production reporting requirement per the established ADM date. This ticket created the P26 Record for the Transmission when production is reported for a stand-alone MP policy.

APH: In the 6.045 release, APH functionality was implemented for the new UUF/3rd Party Damage procedures. This included allowing the new "FA" Yield Types in the APH. This new Yield Type is an actual yield that is eligible for TA, YA, YE, etc. (See "74343" and "78605" in "Release Notes 6.045.0" for more information.) During internal testing of this functionality, it was found that the "FA" Yield Type was not being consistently retained. On save of the APH, the System was overriding the "FA" yield type with "A". This issue has been resolved. The System will now retain the "FA" Yield Type when keyed.

APH: In the 6.045 release, APH functionality was implemented for the new UUF/3rd Party Damage procedures. This included allowing the new "FD" Yield Type to be keyed so long as Production and Acres are "0". The "FD" Yield Type can be keyed directly in the Misc. grid on the APH or keyed in the Production History grid, and on save, the System will move the year to the Misc. grid. (See "74343" and "78605" in "Release Notes 6.045.0" for more information.) During internal testing of this functionality, a few bugs were identified:

With this ticket, these issues have been resolved. The System will now automatically populate the annual yield field with "0.00" when the user deletes the existing values. In addition, when the user keys a year in the Misc. grid with the "FD" Yield Type and that same year exists in the Production History with a "Z" Yield Type, the System will update the Production History grid to no longer include the "Z" year and allow the year in the Misc. grid. Finally, Fast Edit PR functionality was updated to no longer display lines when the acres are updated to "0" and saved.

Perennials: A bug in the detail line status logic was identified internally while testing perennial PAWs. If a perennial detail line status was "Complete" and the user navigated to the Maintain PAW page and changed the answer to a Required Question, the System set the detail line status to "Incomplete" upon save even if the changes did not result in a suspension. A fix has been implemented to correctly apply a detail line status of "Complete" if the Required Questions on a PAW are edited on a previously "Complete" detail line (if all detail lines status requirements are met).

Shareholders: It was found it was possible for a user to associate shareholder records with Master Yield (MY) and Personal T-Yield (PTY) Summary lines from the Maintain Detail Line and Maintain APH pages by launching the Shareholder modal after clicking on the Add/Edit button on the Shareholder Information banner. Shareholder records do not apply to these lines, so with this ticket, the Add/Edit and Remove buttons were removed from the Shareholder Information banner on the following two pages for MY and PTY Summary Units:

STAX: For the 2017+ RYs, RMA has updated their calculator for STAX SE Cotton detail lines. As such, the calculator in the System was updated to round the Expected Revenue Amount to 2 decimal places prior to being multiplied by the Coverage Range and Price Election percent.

WFRP: In the 6.045 release with TFS #78935, validation errors were added to require the user to enter the correct beginning month based on the tax year selected on WFRP policies. For early fiscal year, the beginning month must be February - August, and for late fiscal year, the beginning month must be September - December.

During testing of this ticket, an issue was found with the late fiscal year validation. The validation was previously requiring the beginning date to be in September, October, November, or December of the Reinsurance Year on the policy. Since the coverage for late fiscal year filers will begin in November of the year prior to the Reinsurance Year on the policy, the System should allow a beginning date in September, October, November, or December of the policy RY-1. For example, a 2018 WFRP policy with a late fiscal year tax year will have a beginning month of September, October, November, or December of 2017. The validation for the late fiscal year beginning date has been updated to require a date in September, October, November, or December of the RY-1 rather than the RY.

WFRP: In the 6.050 release, with TFS #80730, a bug was fixed where the total Expected Revenue and qualifying commodities were not recalculating when commodities were added, updated, or removed. (See "80730" in "Release Notes 6.050.0" for more information.)

During internal testing of this ticket, it was found that the System was not refreshing the Income & Expenses tab when commodities were added, updated, or removed. This made it appear as if the premium was not recalculating. While the premium was recalculating, the display was not updating until the user either saved the Income & Expenses Record or closed out of the policy and re-opened.

The Income & Expenses tab has been updated to refresh when the user selects the tab.

NOTE: During internal testing, a bug was found with the date picker on the Income & Expense tab. If the user enters a date as "11212017" rather than "11/21/2017", the System sits at saving and does not finish processing. TFS #82153 has been created to address this issue. In the meantime, users must enter the slashes in the date to save.

The AIP requested that the Margin Protection (MP) plan be added as an allowable Plan of Insurance to create an associated Supplemental Replant Coverage (SRC) policy from. The user will now see SRC as an electable Private Product if they have MP set as their MPCI Coverage plan.

NOTE: If the grower has either a YP, RP, or RPHPE plan on their MPCI crop/county as well as MP, the SRC will be associated with the YP, RP, or RPHPE plan.

Annual Crop Hail policies display a Carryover Policy checkbox on the policy page. If that checkbox has been selected, there will now be an option in the Private Products Policy Register (Reports > Private Product Reporting > Policy Register) so the user can select to only show carryover policies once the report is generated.

There was an issue where the Cash Discount was being applied to Price Flex Prime policies even though a Cash Discount does not apply to this product.

Price Flex Prime has been updated to ensure Cash Discount will not be applied to new Price Flex Prime policies. Also, the System was updated to ensure that Cash Discount may only be available for Hail, Continuous Hail, and/or Production Hail policies if applicable for the Product Type/State.

NOTE: A script was previously provided to the AIP in order to remove the Cash Discount from existing Price Flex Prime policies in production on November 20th.

This update set the PAR product to be able to import organic practice lines to meet the requirements of the policy language for the product. This ticket is for the PAR product only. With this update, when acres are submitted on a PAR policy, any acreage with an organic practice will be brought over to the Private Product PAR policy.