Release Notes 9.025.0

Actuarial Change Request: During the 2021 Handbook review, it was found that the Request for Actuarial Change Form needed some updates to be more in sync with the Written Agreement Handbook (WAH). Since the form was updated to make a few base form standard updates, these changes were also made (for all years) with this ticket.

PR: The Production Report's annual review of enhancement requests has been completed for the 2021 RY and the following have been implemented:

NOTE: Quality Loss (QL) Option updates are being completed in TFS #118432.

SOI & SOI/PR: It was reported that premium information was not printing when a detail line had the DC option on the Schedule of Insurance (SOI). For all Crop Years, the rule for the SOI and SOI / Production Report was updated to print the premium information for detail lines with the DC option.

Livestock: RMA released updated provisions for Livestock Gross Margin (LGM) for the 2021+ CYs. While working on the 2021 LGM Provisions, it was found that the LGM Cattle Schedule of Insurance (SOI) was printing a zero in the Approval Number field when it shouldn't have been. The LGM Dairy Cattle and Swine SOIs were working correctly. With this ticket, the 2021 LGM Provisions for Cattle, Dairy Cattle, and Swine were implemented, and the LGM Cattle SOI was updated to not print a zero in the Approval Number field; instead, the field will be blank when that value defaults to zero. Provisions print with the Livestock Schedule of Insurance (SOI) when the print option to print provisions with the form is selected. The Livestock SOI is available to print from the Livestock policy Print tab.

Provisions: With this ticket, the 2021 LGM Policy Provisions have been implemented in the System for 2021. The following Special Provisions for 2021 have been implemented in the System:

To improve the usability of release notes, some changes were made to how they’re accessed in the Online Help Site. With this ticket, users will be able to access the release notes for all releases from a single page, which contains a high-level summary of release changes and a link to the full release notes if they want to review all changes. This functionality was already in place for Archived Release Notes—we're simply adding the current release to the release notes table and retiring the Current Release Notes page in favor of this more efficient design.

Help Icon Option Changes

In the System, when the Help (?) icon is clicked in the header and either the "Release Notes" or "New Release Notes Available!" option is clicked (only one option will display—the "New Release Notes Available!" option only displays after a new release with release notes is deployed and the first time the user clicks the Help (?) icon after that new release), the previous Archived Release Notes page will now open instead of the "Current" page. The Archived Release Notes page name has been updated to "Release Notes".

Help Site Functionality Changes

With this single-page format, users can find the release they want to view notes for in the tables for each calendar year and read a brief summary of each release's larger changes.

DRP: The DRP QCE form has a new field for the Nonfat Solids Price that was implemented with TFS #116347. Previously, this field was populating with a zero as the value as there was not a direct link to the ADMs. The Nonfat Solids Price is the Protein Test value selected by the insured plus the Fixed "Other Solid Test" value. With this ticket, the Nonfat Solid Price field has been added to the DRP Premium Line UI. This new field displays when the user has selected the Component Pricing Option. The field displays under the Other Solid Test field and is read-only. In addition to the UI change, a new DB field has been added to the LivestockPremiumLine table to correspond with the new UI field. The Forms Team will now be able to map the field on the form to the DB field.

LGM & LRP: It was found that if an SBI on an LRP or LGM policy was submitted to eDas with a share = 0.000 or the sum of all SBI shares on an LRP or LGM policy totaled 1.000, eDas would return an error for the policy. This ticket was set up to make some enhancements to help agents and underwriters identify SBIs with zero shares or shares totaling more than 1.000 prior to the submission process. The following updates have been made to the System for LRP (Plan 81) and LGM (Plan 82) only:

PRF/API WIZARD: The following issues have been corrected with the PRF/API Wizard:

NOTE: The following items will be handled in TFS #119725: 1) Changes to the "name" of the unit group (i.e., Share, Grid ID) are not reflecting in Mapping after refreshing; 2) Temp Unit Groups do not highlight associated fields or allow the Auto-Select POR functionality.

Apiculture: TFS #80518 implemented a change where the percent of value was rolled for Apiculture for the 2019 RY. During UAT of the 2020 RY roll, it was determined that the percent of value did not roll as expected for Apiculture. By the time this was found, it was too late for a code fix for the 2020 RY roll, so a script was run post roll to update the percent of value for 2020 coverages. With this ticket, the 2021 roll code has been updated to roll the percent of value for Apiculture correctly.

PRF/Apiculture: An AIP requested that the lesser of the Insured Acres for PRF or Insured Colonies for Apiculture or the Reduced Acre or Reduced Colony values roll as the Insured Acres/Colonies in the new RY. For PRF (0088) and Apiculture (1191), the roll logic was updated to roll the lesser of the following values (if greater than zero) into the GroupReportedAcres field in the new RY (this is the Insured Acres/Colonies field in the UI):

NOTE: If one of the Reduced Acre values is rolled to the GroupReportedAcres field in the new RY (which is the Insured Acres/Colonies field in the UI), the sum of the MpciPremiumLine.ReportedAcres/Colonies values for each Interval within the Grid ID will likely not be prorated correctly in the new RY since they will roll based on the prior RY's Insured Acres/Colonies value rather than the reduced value. In this situation, when the premium lines are saved in the new RY, they should error and the user will have to correct the prorated values.

PRF/Apiculture: Code refactoring around the save process on Plan 13 PRF and Apiculture detail lines has been implemented, and work has been completed to speed the overall save time (including the time required to return validation errors to the UI should validations apply at save). These changes have been performed within the PRF/Apiculture Detail Line modal that was introduced prior to the 2020 RY.

APH: An issue was found internally where, when the SF APH used the CC yield and YA was applied, the System was blanking out the Current Year yield limitation flag on the SF APH. The System was updated to apply the "09" Yield Limitation code to the SF APH from the CC APH when "Use CC Yield" applies.

PRH Pilot: Production and Revenue History (PRH) is a new pilot program insuring Strawberries in select counties within the state of Florida for the 2021 RY. PRH is a pilot program that provides protection for Strawberries against loss of production and revenue that the insured expects to earn or will obtain from commodities produced during the insurance period. Coverage is based on individual historical production and revenue of the insured crop. The pilot will be expanding to select counties within the state of California for the 2022 RY, replacing the existing ARH plan. The program is eligible to persons who have either grown Strawberries commercially or have participated in managing a commercial Strawberry farming operation in at least three of the last five years. PRH will be offered under the Common Crop Insurance Policy Basic Provisions.

Insureds will have a choice of yield coverage or one of two revenue coverages, Revenue or Revenue Plus. The yield plan accounts for production shortfalls due to adverse weather, fire, earthquake, volcanic eruption, failure of irrigation supply, wildlife, insects, and plant disease. The revenue plans will account for loss of revenue due to a production shortfall previously described, a price decline, or both. Uninsured causes of loss include crop injury due to equipment or poor handling, failure to market or harvest in a timely manner (unless due to a covered cause of loss), or soil salinity (in California only). Under the three types of coverages, the Yield guarantee will be the same as the APH, and the price will be based on the producer's own revenue history, which will require additional reporting to generate more tailored guarantees.

This ticket accounts for the changes needed on Coverage pages (Add New Policy, Add New Coverage, Maintain Coverage, and View Coverage) as well as the validations within those pages to account for the new PRH program. The coverage pages will utilize the current ARH (Plan 47) Strawberry logic with a couple of modifications called out below. These changes will be applicable to only the new PRH Plans for the 2021+ RYs.

Quality Loss: While testing TFS #117744 for Quality Loss exception calculations (MY, CC/SF, SAT, and PTY), a bug was found with the Apply Current Year SA-T-ylds functionality accessed from the Additional Functions dropdown. The System was incorrectly calculating the Approved Yield for Added Land- Simple Avg. The System was taking into account the newly calculated SA T-yld approved yield for the unit instead of the prior yield before the "Apply Current Year SA-Tyields" function was selected to apply to the units. This has been corrected.

Display Issue: It was internally discovered that the Crop Options hover icon under the "Processing Status" column and the Commodity Type hover icon under the "Type" column on the Detail Lines tab were misaligned. Also, the popups that displayed when the icon was hovered over were not displaying in the correct location. These issues have been corrected.

HIP & Enterprise Units: As part of the System's enterprise unit functionality, the System validates whether or not a coverage meets at least one of the enterprise unit qualification rules during Mark Complete. This logic sums acres by land ID to determine the number of acres in each unique land ID for purposes of the 20/20 rule and/or the 660+ acre rule. By design, this logic excludes acres from any System-generated child lines, such as SE or SCO, since these acres are duplicates of the parent lines. Now that HIP functionality is in place in the System and includes the creation of HIP child lines, the enterprise unit logic needed to be updated to exclude HIP child lines. This has been done with this ticket.

HIP: As part of the Hurricane Insurance Protection (HIP) policy, if a hurricane hits prior to the Acreage Reporting Date (ARD) + 14 days, the number of eligible acres is reduced. When eligible acres are reduced, a HIP Acre Limitation Factor is applicable and premium/liability is reduced. Per Manager's Bulletin MGR 20-011, if a hurricane hits prior to the ARD + 14 days, the number of eligible acres will be the lesser of:

Because of the late implementation of the HIP policy on RMA's end, the requirement for an intended acreage report was not added until after most agents had collected the application for HIP, and therefore, an intended acreage report was not collected and most HIP policies do not have intended acres applied in the System (the functionality for HIP intended acres was implemented with TFS #116562). Due to the lack of an intended acreage report for the majority of HIP policies, RMA revised HIP procedures to allow the highest number of acres planted in any one of the immediate past four crops years to be used in place of intended acres.

System functionality is now being added to account for this new value. In an effort to get this functionality in place in order to pay claims related to the recent hurricane that hit Texas, this process will be mostly manual for the 2020 Reinsurance Year (RY). First, a new Greatest Acres in Previous 4 Years field was added to allow AIPs to key the highest number of acres planted in any one of the immediate past four Crop Years. For 2020, this will be a manual determination by the AIP's UW/Claims staff, and a value should only be keyed in this field if the determined value is less than reported acres in the current RY and a claim exists. This is necessary because the existence of this value on the coverage will be used as the "trigger" for the System to determine when the reduced premium calculation applies.

NOTE: The transmission logic related to this change will be handled with TFS #118642, #119171, and #119036.