Release Notes 9.090.0

AOI: An Assignment of Indemnity (AOI) Confirmation form has been implemented in the System for Livestock. The following updates have been made to the System for all years:

NOTE: The Release Date will not print on 2020 DRP policies. The reason why it isn't printing for 2020 is because, for DRP policies, the AOI Assignment was changed from the Detail Line level to the Coverage level for 2021+ policies. Therefore, the Release Date for a 2020 policy is stored in a different field than those for 2021+.

SOI: A request was received to improve the reflection of revised acres / colonies and liability on the Schedule of Insurance (SOI)'s Apiculture (API) and Pasture, Rangeland, Forage (PRF) format. A pre-requisite for this ticket was TFS #122016, PRF/Apiculture - 2020 RY + Add 'revised liability' to grid when acre/colony revisions have been applied, which was implemented in the 9.080 release. With this ticket, the SOI has been updated in the following ways for all years:

LRP: A request was received to add Entity State and County to the Livestock Risk Protection (LRP) Application, and those fields were added with TFS #123997 in the 9.080 Release. With this ticket, the LRP Application has been updated to pre-fill Entity State and County when the form is printed with a pre-headed report style. The LRP Application has been updated in the following ways for all years:

Entity State / County data rules:

ECO: Beginning in the 2021 RY, for crops with an 11/30 or later Contract Change Date, the Enhanced Coverage Option (ECO) will be available for certain state/county/crops. From a system perspective, ECO will work similarly to SCO. TFS Ticket #121141 implemented a supplemental application necessary to support ECO on the main MPCI Application and Policy Change Form.

Now, when ECO has been elected on a coverage and the ECO Application page has been elected to print as pre-filled, then County, Crop(s), Underlying Plan of Insurance, ECO Plan of Insurance, Area Loss Trigger, and Coverage Level will print on the ECO Application page; if any of the ECO data is not available, then the field will be blank.

The updates apply to all years; the System determines if ECO can be selected on the coverage.

An enhancement request was received asking to add an information popup on the Livestock Policy Management Dashboard (Livestock > Policy Management Dashboard) for premium numbers including total (gross) premium, subsidy, A & O, and producer premium. With this ticket, the following changes have been made to the Livestock Policy Management Dashboard:

Attachments: With this ticket, the existing attachment popup (available from the Attachments tab) for Livestock policies has been redesigned to allow multiple files to be attached at one time. This mirrors the functionality currently in place for MPCI policies.

LRP:  An enhancement request was received asking to update the State dropdown on the Create Quick LRP Estimate page (Livestock > Create Quick LRP Estimate) to function as other State dropdowns in the System. With this ticket, the logic for populating the State, Commodity, and Type dropdowns on the Create Quick LRP Estimate page has been updated so that the text display will now display the state/commodity/type name first followed by the respective code in parentheses. Now, the dropdowns are searchable by the user as they type the state/commodity/type name.

Per RMA, a Livestock insured can only have one policy per state. In order to get agents to stop keying multiple policies in the same state, which results in errors, a warning message was added on each livestock coverage entry page (upon selection of the policy state in the State dropdown) where a policy for that state already exists. If the insured has a different county for the same state that they need to enter, they need to do so on the existing policy for that state instead of entering a new one.

With this ticket, a new hard stop validation was added to the Add New Livestock Policy page for all three Livestock plans (LRP-81, LGM-82, and DRP-83) to prevent users from establishing a new Livestock policy for a Grower if a policy for that Grower already exists for that State and Plan combination. Users will still be allowed to add multiple Livestock policies for the Grower using the same state as long as they all have different plans.

NOTE: For LGM and LRP, the validation will be based on the POLICY State, not the Entity State.

When processing the 2020 December CLU Layer from RMA, Arkansas was not included in the released data set; this has been corrected.

Detail Lines: TFS #122239 was implemented in the 9.085 release and converted most of the standard premium lines to a detail line popup. All plans and crops are impacted except plans 04, 05, 06, 16, 17, 35, 36, 40, 41, 43, 90, and 50 as well as the following crops: Peanuts, Annual Forage, Mac Trees, and Nursery.

PTY: While working on the PTY Comparison Worksheet, it was found that the calculation logic was pulling from 2 different places.

This ticket addressed this duplication—combining the logic for regular and batch quote PTY calculations—and refactored the code surrounding PTY calculations.

WFRP: For the last two years, a roll issue caused incomplete base periods for some WFRP policies in the new RY. There was no way to fix this within the user interface, so a script had to be run to wipe out the Income & Expense Records along with their related Income & Expense History records and then users were required to re-key everything from scratch in the new RY.

It's believed that the roll issue has been fixed and will not impact the 2022 RY roll, but it was decided it would still be a good idea to make the years within the WFRP base period editable in case there is ever a need to edit the information in the future.

The WFRP base period grid within the Income/Expenses tab was updated to be editable but only when the Override Entire Income/Expense Record checkbox, available to AIP users, is selected.

As with all other System override functionality, it is up to the user to ensure the correct base period information is keyed as there will be no other System validations other than what was described above.

Detail Lines: During internal testing, it was found that when adding or editing a Nursery or Nursery Value Select (NVS) detail line, the user had to save the detail line and then click the Edit/Add Nursery Locations button. Since Nursery locations are required in order for a detail line to be considered complete, it was decided to add a button for Save & Edit/Add Nursery Locations on both the Add New and Maintain Detail Line pages for Nursery and NVS. This new button will be located at the top and bottom of the page next to the existing Save buttons. If this new button is clicked, the System will save the detail line and take the user to the Policy Nursery Location page. This new process will save the user from the interim step of saving the detail line and then selecting the button to add/edit Nursery locations.

ECO: With TFS #120332 in the 9.070 release, coverage functionality for ECO was implemented. As part of this functionality, a warning and suspension were implemented to require the same ECO Area Loss Trigger on all coverages for the same county/crop. RMA has since clarified that if the HR-ACE endorsement is elected, then the grower can choose different Area Loss Triggers for ECO.

With this ticket, the coverage functionality for ECO was updated to account for different Area Loss Triggers when the HR-ACE endorsement is elected; this includes the addition of new warnings and suspensions.

Hybrid Specialty Seed: This ticket implemented the unit structure and rating changes needed for the new Hybrid Specialty Seed Pilot Crop for Hybrid Sweet Corn Seed (0093) and Hybrid Popcorn Seed (0334) for the 2021+ RY.

The System was updated with the following changes:

Fast Edit AR: During testing of Companion Policy functionality, it was found that when a Companion is linked to the Source policy using the Shareholder modal within the Fast Edit AR, the companion link icon was not displaying until the user exited Fast Edit and returned. The icon should have appeared when the link was established and should not have required the System to leave the Fast Edit AR page. With this ticket, the logic was updated within the Fast Edit AR so that when a Companion link is established within the page, the link icon displays immediately.

ARH Cherries: An issue was found, where due to premium in error, RMA was rejecting ARH Cherries for the 2020 and 2021 RYs. With this ticket, a System fix was made to update the APH calculation for ARH Rate Yield to correctly push to the premium line to resolve this issue.

Companion Policies: With the implementation of a new Fast Edit Companion button in the near future, the available real estate for our current Fast Edit buttons was re-evaluated. The page banner on the View Detail Line page already contained Mark Complete, Fast Edit PR, Fast Edit AR, and Fast Edit CLU, so the addition of Fast Edit Companion caused crowding. With this ticket, adjustments were made to the location of these buttons to account for the growing number of buttons on the banner. Now, a vertical ellipsis displays to the right of the Mark Complete, Fast Edit AR, and Fast Edit PR buttons. Once selected, the Fast Edit CLU and Fast Edit Companion buttons will display in a dropdown and are available for selection.