Release Notes 12.025.0

Batch Printing: The Batch Printing menu has been updated to support batch printing Livestock Applications (for all plans—LRP, LGM, and DRP). Now, when "Livestock" is selected from the Product Type dropdown in the Batch Printing tool, the following forms and print options will be available in the Selected Forms to Print section:

2023 Blueberry Crop Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

2023 FL Avocado Crop Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

2023 Table Grapes Crop Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

2024 AZ and CA Citrus Crop Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

2024 CA Avocado Crop Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

2024 TX Citrus Fruit Crop Provisions have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

Acreage Report: The Acreage Report has been updated in the following ways for all Crop Years:

API/PRF Combo Form: The Apiculture (API) and Pasture, Rangeland, Forage (PRF) Combo Form has been updated to improve usability. In addition to these changes, a new print option, "Include Extra AR Page", has been added to the form. This print option is available for all report styles and defaults as unselected.

CLU Acreage Report: The CLU Acreage Report (AR) has been updated in the following ways for all Crop Years:

NOTE: This form is not intended to be used for Annual Forage (AF), Pasture, Rangeland, Forage (PRF), Apiculture (API), Category C Crops, Perennial Crops, Plan Code MP (16) associated with a YP or RP coverage, Plan Code MP-HPO (17) associated with a YP or RP coverage, Plan Code STAX-RP (35) associated with a YP or RP coverage, Plan Code STAX-RPHPE (36) associated with a YP or RP coverage, Nursery, or WFRP.

SPOIs were updated and made available from RMA on Aug 24. Special Provisions for 2023 have been downloaded and implemented in the System for API and PRF.

The 2023 Onion Crop Provisions that will be effective for 2023 and succeeding years have been implemented in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

Previously, logic was added that would show when a CLU was no longer valid but did not account for RLUs. This ticket updated the logic so that if the CLU information is not valid but the field is flagged as being an RLU, it will not trigger the invalid CLU logic.

Previously, the Sync menu was updated to allow Sync from AR to bring in planting records/fields from all counties for a grower, not just the current policy. This ticket enabled that same logic for the PRF Wizard.

RMA released a new CLU Layer-September 2022; this has been implemented in the System.

There was previously logic in place that prevented a premium line from being deleted if it was associated with a mapped field; this has been removed.

Users requested 2 changes to Mapping functionality: 1) When searching by Lat/Long, display a noticeable flag and allow a user to store that coordinate as a POR for the policy; and 2) When viewing PORs in the PRF Wizard, allow a user to click on a coordinate in the PRF Wizard window and have the selected POR be highlighted on the map. These were implemented with this ticket.

Users requested the ability to delete all planting records without deleting the underlying fields. This has been implemented. Now, to delete planting records, make the layer active for the plant records you are deleting, and then, go to Tools > Remove All Planting Records.

Users requested to see both field acres and calc acres within the Map Region windows. This has been implemented.

When users were choosing to roll field data forward from 2022 to 2023, if they accidentally chose to include crop data for PRF, it was creating a planting record for each interval of the unit group instead of just one for the whole unit group, which caused issues in printing and syncing. This update will allow the System to skip creating planting records when the crop is PRF and the user roll fields, even if the user chooses to include crop data. In this case, the user would roll fields and then do a sync from AR to bring in the crop/planting data correctly.

Users reported that RLUs did not get included in the roll of field data from 2022 to 2023, which caused issues in the PRF Wizard and sync of PRF to the AR. This has been resolved.

Detail Lines: In TFS 139290, a new Verifiable Record Type Code field was added to the detail line (on the below pages) in order to accommodate for the Marketing Certification an insured may file. This certification would need to be captured on the P11 through PASS and this would help manage this requirement.

A gap in logic was found internally where, when a Verifiable Record Type Code field had been selected on the parent line and a child line applied, the selection was not always being pushed to the child line as expected. With this ticket, the System has been updated to always push field selections from the parent line's Verifiable Record Type Code field to the child line.

Fast Edit AR & PR: Internal testing found an issue with the attachments icon link that was added to the Fast Edit grids in the 12.010 Release. When this icon link is clicked, the System should open a new browser instance, launching the Attachments tab. However, testing found that while the System was opening the new browser for the Attachments tab as expected, it was also opening a third instance and a "Sorry..." error was being thrown. System logic has been updated so that when a user clicks the Fast Edit AR or PR attachments icon link, the System will only open one new browser instance for the Attachments tab and a "Sorry..." error will no longer received.

Land IDs: An enhancement request was received to update the "Place Name" label on the Manage Land IDs popup to "Farm Name" to match what is currently on forms. A System fix was implemented to update the Manage Land IDs popup, changing "Place Name" to now read "Farm Name".

Micro Farm: For the 2023+ RYs, the Risk Management Agency (RMA) has introduced regulatory changes for the Insurance Plan, "Whole Farm Revenue Protection (WFRP) (76)". These regulatory changes include the following: 1) Increasing the Maximum Insurable Revenue for WFRP (0076) from $8.5m --> $17m; 2) Increasing the Maximum Approved Revenue for Micro Farm (9110) from $100k to $350k for New Producers and from $125k to $400k for Carryover/Renewal producers; and 3) Removing Expense Reporting for WFRP (0076). The RMA has indicated that there is increasing pressure to expand these caps for WFRP and Micro Farm so that more growers can participate within the WFRP program. All three of these changes have been ticketed and will be addressed for the WFRP (76) plan code for the 2023+ RYs only.

For Micro Farm (9110), there is a Suspension as well as Revised Reporting Capping Logic that the Maintain Income page uses—both of these will be updated with this ticket.

Perennials: During internal testing of TFS 137679, it was found that when a user removed a value from the insurable or uninsurable acres fields and saved, a hard stop was received of either "The Stage' ' TreesInsurable field is require" or "The Stage ' ' TreesUninsurable field is required" for Plan 40 Stage 1 Tree crops.

The System has been updated to only allow for numeric characters and a minimum value of 0 (the System will always default back to the minimum value of "0" if no value exists) within the insurable and uninsurable fields on Plan 40 Tree Crops.

Perennials: The Davis RO office has issued the 2023 RY Underwriting Guidelines for Category C crops. The only changes involved were the Maximum Yields allowed within the Approved Yield of the APH calculations. The System automatically applies the higher yield request procedure when Almonds are in the 6th, 7th, 8th, or 9th leaf year and the 2022 RY actual yield in the APH is at least 95% of the 2021 RY actual yield. If these conditions are met, the System will apply the higher yield calculation.

With this ticket, the Maximum yield factors (outlined in the 2023 RY Underwriting Guidelines) to be used within the Approved Yield of the APH Calculations have been updated.

Perennials: The Davis RO Policy Exceptions includes calculation of approved APH yields for Grapes and Stonefruit that do not meet the minimum production included in the policy provisions.

If an APH has not reached the minimum production requirements, a simple average may be calculated for the Approved APH yield if:

The System is calculating the correct approved APH yield in both situations; however, it was found that the suspension (see below for suspension text) that is supposed to notify the UW of the calculation did not appear to be working in either situation (entering an AR sign date is required to trigger suspension logic).

With this ticket, the System has been updated, and the suspension will now trigger for CA Grapes and Stonefruit when the minimum production requirements have not been met.

Suspensions: An issue was reported where units flagged as No Longer Farming (NLF) were triggering the suspension message, "APH Reference Years are different across coverages for the County/Commodity. A Save of an APH may be required to determine the correct Reference Years. Underwriter Review Required."

In researching the reported issue, it was found that TFS 132077 (Release 11.035) implemented this above mentioned suspension. This suspension was added to the Mark Complete logic to indicate to users that Reference Years were different across coverages where coverages by type were applicable. This would help notify users to correct APHs that have different Reference Years across coverages.

With this ticket, System logic has been updated to no longer include No Longer Farming units in the suspension logic for APH Reference Years being different across coverages.

TOGA: For the 2023 RY, RMA is funding the Transitional and Organic Grower Assistance (TOGA) subsidy program. The TOGA program assists producers that transition to and continue using organic agricultural systems. This crop insurance aims to address the economic challenges that arose due to the COVID-19 pandemic to support growers as part of building more and better markets for American growers and consumers and to increase the resilience of the food supply chain. During the organic transition period, producers traditionally face lower yields without the increased prices received from organic production, which TOGA will help offset.

TOGA premium assistance will be based off plan of insurance and the commodity as well as the organic cropping practice. For WFRP, qualifying producers will receive an additional 10% premium assistance on their qualifying policies if any acreage is reported as transitioning to organic or already organic certified. For other plans of insurance that are not Annual Forage or endorsements, producers will receive up to 10% premium assistance for all crops that are reported as organic transitional or organic certified. Lastly, for qualifying producers with organic grain and feed crops covered under non-WFRP plans that are not endorsements, there will be premium assistance of $5 per insured acre.

TOGA can be stacked with other subsidies, such as state subsidies from IA, IL, IN, and soon, WI. PCCP can also be applied if this subsidy is offered again for the 2023 RY. Written agreements and prevented plant acreage are eligible for these subsidies. TOGA only applies to coverages with additional/buy-up coverage. The subsidy is limited to no more than the total premium amount owed. TOGA does not apply to endorsements (SCO, ECO, HIP, PACE, related MP, or related STAX) on an underlying policy. Standalone MP and standalone STAX are eligible for TOGA. No enrollment paperwork is required for TOGA. Eligible producers who already have an active 2023 policy will receive the subsidy.

Eligible organic grain and feed crops: Alfalfa Seed, Barley, Buckwheat, Corn, Cultivated Wild Rice, Dry Beans, Dry Peas, Flax, Forage Production, Forage Seeding, Fresh Market Sweet Corn, Grain Sorghum, Hybrid Seed Corn, Hybrid Popcorn Seed, Hybrid Sorghum Seed, Hybrid Sweet Corn Seed, Millet, Oats, crops insured under the Pasture, Rangeland, Forage policy, Peanuts, Popcorn, Rice, Rye, Safflower, Sesame, Silage Sorghum, Soybeans, Sunflowers, Sweet Corn, Triticale, and Wheat.

For the 2023 RY, with the standard file import process, the RMA determined TOGA subsidy values will be imported and stored on the applicable detail lines in the database. The Mark Complete process will then sum these values for the coverage. The summed value(s) for the coverage(s) will be included on the Billing Statement. There will be NO UI display of this value on the coverage or detail line. The values are provided by RMA. Within the System, the TOGA program will work like state subsidies and PCCP, which are also values received from RMA that are printed on the Billing Statement.

UDGO: A spinoff from TFS #138375. As part of the UDGO functionality, a Section Equivalent ID is required on the P11 record; however, if UDGO is not elected, Section Equivalent IDs are not allowed. This ticket added logic to delete section equivalent values if the related UG Written Agreement is deleted.

UDGO: A spinoff from TFS #138377. The new UDGO functionality requires the user to select a Unit Structure override from the Manage Unit Structure popup to apply EU (EU, EC, EI, ET, MC) to UG premium lines. As part of this, the System should not trigger any EU-not-qualified suspensions/validations. Users must determine whether EU applies. With this ticket, all suspensions/information messages for EU not qualified when UG is applied have been hidden if UG and any form of EU is elected.