Release Notes 8.020.0

A request was received to print Plan on the detail lines on the Schedule of Insurance (SOI) and SOI / Production Report. The SOI and SOI / Production Report have been updated in the following ways:

It was found that PP acres were printing on Production Reporting forms when they should not have been. Along with an update to fix this issue, the Production Reporting Worksheet has also been updated the incorporate the new base format that's currently applied to the Schedule of Insurance form. The following changes to the Production Reporting Worksheet have been made for all Crop Years:

The land logic to also include RLU that is used by 98% of the forms that print land was updated in the 8.005 release with TFS #103972. With this ticket, the land logic that the Production Report / Acreage Report uses was updated to include RLU land. This update has been made for all Crop Years.

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

WFRP: A request was received for users to be able to add revised sign dates for the Revised Farm Operation Report on WFRP policies. With this ticket, fields for Revised Insured Sign Date and Revised Agent Sign Date were added to the Commodity page. These fields will only display if the Revised Report checkbox is selected, and once a date is applied to one commodity on the policy, the System will apply the same date to all commodities on the policy. In addition, if the Revised Report checkbox is deselected on all commodities on the policy, the System will remove the revised sign dates from all commodities.

NOTE: If at least one commodity is still marked as a "Revised Report", the revised dates will continue to apply to all commodities. Application/removal of dates on an all or nothing basis is necessary for the related "Missing Revised Farm Ops Sign Date" reports functionality that is being implemented with TFS #106252. This functionality applies to the 2019+ RYs only.

An issue was reported with the navigation on the Detail Lines tab after accessing and closing out of the Manage Land ID popup. When the user saved/exited or canceled out of the popup, the System would return them to the top of the Detail Lines tab rather than returning them to the same place on the page where the popup was originally launched from. This was a pain point, particularly on large policies.

Navigation when accessing and closing out of the Manage Land ID popup has been updated to return the user to the same place on the Detail Lines tab where the popup was originally launched from. In addition, a visual cue was added to show the user which detail line the popup was launched from when they are returned to the Detail Lines tab following their exit from the popup—the detail line will be highlighted with a gray band and will flash for a few seconds.

Mark Complete: The coverage status displays on the View MPCI Coverage grid, and this status changes from incomplete to complete or pending following a Mark Complete process. There was a concern received through the Help Desk that the status wasn't being updated properly during the Mark Complete step; there was also confusion around the reset button and what its purpose was. The scope of this ticket is to refine how this logic works.

The Mark Complete process was updated to only set the status at the end of the Mark Complete after all suspensions have been checked. As a reminder, the Mark Complete process is run across the service bus and contains multiple pieces, with suspensions being only one of the pieces of the logic that is looped through. This change will correct the issue identified when a user refreshed the coverage grid (using the refresh swirl icon at the lower right corner of the page) while the Mark Complete was still being processed on the service bus. Users saw the status changing during the refresh and that was because the Mark Complete process had not finished and actually reflected a point in time in the process. It was confusing for users to see this status changing without realizing what was happening on the backend.

The reset button will only change the status of a coverage to incomplete and delete the corresponding record in the ServiceBus table (which is not used by the service bus to actually process job requests). Once a Mark Complete job is sent to the service bus, a user cannot stop the job from completing because it's running externally to the System. The reset button is intended to allow a user to trigger another Mark Complete if a job is hung up or doesn't complete as expected—it doesn't actually stop the first job from running.

MCEU: As part of the MCEU premium calculation logic, the System sums and stores total acres in each MCEU in the database for use in the premium calculation. A bug was reported where certain MCEU policies were receiving P11-7187 errors and a developer traced this issue back to DC Rice acres. The logic that determines total acres for each MCEU was including DC Rice acres. Since DC Rice acres are duplicates of their parent line acres, they should not have been included in this calculation. The logic that determines and stores total acres in each MCEU has been updated to exclude DC Rice acres.

TFS #103366 updated the premium calculation changes initially when the previous Yield Limitation flag was 03 and the YC option had been applied. Some policies were found to still be in error with a P11-7187 error. A request was submitted to RMA for additional information on how the M13 calculations were being applied to those units that had a Yield Limitation flag of 03 in the prior year. Based on RMA's clarification, an update was required to the calculations being used. In the 2018+ RYs' Plans 01, 02, and 03 Rate Calculator, if the premium line is YC and the previous Yield Limitation flag is 03 for EU, the System will now get the Prior Year Enterprise Unit Residual Factor from the ADM CoverageLevelDifferential table rather than calculate the value.

2020 Roll: TFS #83397 added an AIP Approval Date to the coverage on WFRP policies in the 2018 RY. AIPs use this date field and a correlating suspension to track policies that require review by a UW. This date rolled from 2018 to 2019 and a script was required to remove the dates post-roll. The 2020+ Roll logic has been updated to no longer roll this date to the new RY.

2020 Roll: TFS #74783 adjusted WFRP System logic to account for a lag year for Late Fiscal Year Filers when keying Income/Expense data for 2019. During testing, it was determined that the year-end roll logic wasn't accounting for this new base period.

The Base History Period on the Income/Expense table for WFRP Early Year Fiscal Filers is:

The Base History Period on the Income/Expense table for WFRP Late Year Fiscal Filers is:

The 2020+ Roll logic has been updated to now roll the correct Income/Expense Base History Period for WFRP Late Fiscal Year Filers. The Base Period did not change for Early Year Fiscal Year filers.

2020 Roll: TFS #80158 updated the 2019 roll to roll the Percent of Value for Apiculture Intervals to mirror PRF roll logic. However, it was determined that the roll should also include the Reported Acres for Apiculture as well. The 2020+ Roll logic has been updated to roll Apiculture Colonies to the new RY.

2020 Roll: An AIP reported that a Written Agreement did not roll for a particular policy when the 06-30 CCD roll completed in Production. It was determined that there was some reversed logic around the multi-year flag in the new roll logic and multi-year WAs did not roll. The roll logic has been updated to reflect the correct logic for multi-year WAs (logic now matches Legacy roll code). MCT will identify 2019 WAs that should have rolled as part of the 04-30 and 06-30 CCD roll jobs and try to figure out a way to get them rolled to 2020.

APH: A bug was reported to the Help Desk on 7/24 that AIPs identified due to P15A-10232 errors at RMA. Within the APH, there were multiple duplicate years persisting and, when transmitted, the APH records were being rejected. The created date for the APH in the System indicated that the APHs were created in conjunction with AR processing when added land and/or New Producer was applied to the APH. APHs where the variable tyield is > SA Tyield appear to be unaffected. The only way MCT could recreate this behavior was to do the following steps:

NOTE: The test policy must be an added land SA that is greater than the variable tyield.

Post release, AIPs will need to manually clean up APH records impacted by this bug. AIPs should verify their current error report to identify policies to test with. If no policies are rejecting, this part of the ticket will not be able to be tested.

Re-creation of the bug uses a series of actions that are not common in the creation of an added land unit or APH. This bug impacted a small number of policies and may not have even occurred with every AIP's policies.

Per the CIH, when multiple crops are insured on the same policy, the insured has until the latest acreage reporting date for the planting season (fall/winter or spring) to report their acres for all crops. The fall planting season is considered to be anything with a final planting date prior to December 31st of the current RY-1. The spring planting season on the other hand is considered to be anything with a final planting date of December 31st of the current RY-1 or greater.

An issue was reported where the Acreage Reporting Date lockout logic was not taking into account the latest ARD by planting season for all crops on the policy when determining the lockout date. ARD lockout functionality has been updated to determine the latest ARD by planting season for all crops on the policy. This is the ARD that will be used to determine the lockout date. For example, if Corn with a 06/15 ARD and Soybeans with a 05/15 ARD exist on the same policy, the System will use the 06/15 ARD to determine the lockout date for both Corn and Soybeans.

NOTE: In the 8.015 release with TFS #54399, the agency lockout functionality was redesigned for the 2020+ RYs to separate the PRD and ARD lockout functionality into two separate lockout dates. For the 2019 and prior RYs, both PRD and ARD lockouts are combined in a single lockout date determined by the ARD.

An issue was reported where the detail line was displaying the Late Plant Reduction will Apply when the Plant Date was prior to the SubCounty Code Final Plant Date. A System change was done to correct the MPCI Premium line page where it was displaying the incorrect Reduction Guarantee.

ARD: During internal testing of the Acreage Reporting Date lockout functionality, a bug was found with the lockout logic as it relates to the following functionality:

The Acreage Reporting Date lockout functionality has been updated to prevent agency users from using the functionality listed above if the current date is past the lockout date + the offset. In addition, the Lockout Bypass ARD System Function has been updated to allow agency users access to the functionality listed above after the lockout date.

Companion Policy: An issue was identified where the Modified Acreage Code (MAR) flags were not being set for companion policies once they had been set on the source policy. The users had to go in and re-save each detail line on the source policy to get it to sync down to the companion policy. The syncing logic was updated so the MAR flags are now being set as expected.

PRD: During internal testing of the Production Reporting Date lockout functionality, a bug was found with the lockout logic as it relates to the following functionality:

The Production Reporting Date lockout functionality has been updated to prevent agency users from using the functionality listed above if the current date is past the lockout date + the offset. In addition, the Lockout Bypass PRD System Function has been updated to allow agency users access to the functionality listed above after the lockout date.

Suspensions: An issue was reported that the inconsistent yield validation was triggering an unwanted suspension. The System was including No Longer Farming yields in the 115% calculation for the Approved yield. The policies would not be suspending if the System was not figuring the No Longer Farming yield in the calculation.

In reviewing the Crop Insurance Handbook, if more than one APH database contains actual/assigned yields for the same P/T/TMA for the policy/crop/county, the System then determines the simple average of the approved APH yields for all databases. The System will then multiply that simple average by 1.15. The user will then compare each individual APH yield to the result. Approved APH yields that exceed this result are considered inconsistent approved APH yields. If acres are greater than zero, an AR sign date exists, and the database qualifies as an inconsistent yield, the System will trigger a suspension at mark complete.

The System was including the No Longer Farming units into the simple average of the Approved APH yield. This was incorrect, and the System should have been excluding these units when determining the simple average. This ticket updated the simple average of the approved APH yields for all databases to NOT INCLUDE No Longer Farming units in this average.

A request was made to distinguish between Production Hail types—Continuous and Annual—on Private Products batch reports and policy registers. An enhancement was made to the Private Products Policy Register and Batch Report pages. Once the user selects the product type to be Production Hail, then they will see a Policy Term field with three options in it: All, Annual, or Continuous.

An enhancement was made to the Private Product Factor Insurance/Acre by Share checkbox. The user will only have the ability to edit this checkbox if the detail line is in the placeholder line status. Once the line has been updated from the placeholder line status, the user will no longer be able to edit this checkbox.

Internally, an issue was found where, when a user was editing a Private Product optional endorsement and not selecting an optional endorsement or changing the optional endorsement, the System was not saving the selected optional endorsement. An enhancement was made to Private Products so that when a user is editing an optional endorsement, the change will be saved.

Previously, when a user had a placeholder on a Hail or Production Hail policy that had an endorsement attached, changing the parent line policy form did not validate that the already attached endorsement was still valid under the new policy form that it was being assigned to. With this ticket, on save of the line, the System will ensure the endorsement is valid for the new form code as it was with the old. If the endorsement is found to be invalid, the endorsement line will be canceled and not allowed to be reinstated to the parent.

An issue was found internally where, when a user was creating a Continuous Hail policy and they submitted coverage, no coverage was being created and the System was throwing an Elmah error. A correction has been made so that when creating Private Product Continuous Hail policies, the user is able to click Submit Coverage and the coverage will be created without an error.

An issue was found when users were entering Private Product information for a linked policy—when a user selected a policy form code that had a MinimumLimitPerAcre and entered an Insurance Per Acre amount that was less than the minimum allowable, the placeholder would not complete but no edit message was received. The System has been updated so that, when applicable for a policy form, if the user enters an amount that is below the Minimum Insurance per Acre allowable for that policy form code, they will now receive an edit message that lets them know they must update in order to save.

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

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

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

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

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

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