Release Notes 11.025.0

Livestock: RMA has added an Effective Date to Livestock Gross Margin (LGM) for the 2022 RY to help support the change to weekly sales. With this ticket, Effective Date has been added to the Livestock Gross Margin (LGM) Swine Schedule of Insurance (SOI). Additionally, on the Livestock policy Print tab, functionality has been added that allows users to select which Detail Line to print on the LGM Swine SOI. If no Detail Line is selected for the SOI, a popup message will display to let the user know they must select a Detail Line.

AR: For all Crop Years, the Acreage Report has been updated to default with the "Plant Acres and Plant Dates Entered" print option as selected.

NOTE: This print option gives users the ability to print acres and plant dates on the form without having an AR Sign Date entered. Once an AR Sign Date is entered for the coverage, the acres and plant dates print what has been entered into the System.

APH: An issue was found internally that where, when saving a Master Yield (MY) non-summary unit, the "Record Type Required" hard-stop validation was not being triggered. Research was conducted, and it was determined that the Yield Type Code within MY non-summary units was persisting a blank character in the most recent Production History Record Year. Since the Yield Type Code in the APH was technically "set", the save logic did not set it to "A" correctly, thus not requiring a Record Type Code.

A change has been made to Master Yield non-summary APH units, so that the Yield Type Code is treated the same when blank, empty, or null values exist. This will result in the Yield Type Code and the Record Type Code being set correctly.

WFRP: TFS #130038 implemented the logic needed to allow an expanded operation adjustment factor greater than 35%. Per RMA procedure, this is only allowed if the expansion is due solely to certified organic sources.

The System was updated to implement a suspension message, that will trigger upon mark complete, if the Expanded Operation Adjustment Factor is greater than 35% and no organic commodities exist on the policy.

System logic was updated to invoke the Grower Wizard when a user makes a change to the TIN, TIN Type, or Agency if the Grower Record is a Prospective Grower. Depending on the user's permissions, the Grower Wizard popup will present the user with the ability to process a revision (current and succeeding RYs) or a correction (all RYs).

NOTE: The access to corrections in the Grower Wizard is generally reserved for AIP level users only. The most significant change made involves the creation of a duplicate grower record. As long as the Prospective Grower only has quotes attached (no policies for any product type in any RY), the System will allow the user to save the updates to the TIN, TIN Type, etc. WITHOUT the creation of a duplicate grower. In these instances, the current Grower Recordwill be updated.

Perennials: A display-only error was reported on the Yield Variability popup. Perennial calculations were accurate, but the "YES/NO" checkboxes in the calculation displayed incorrectly. The System has been updated to correctly display these correctly.

Detail Lines & Mapping: An issue was reported when acreage is synced from Mapping where the Detail Line status was changing to "Incomplete". A System fix was implemented to have a mark complete triggered on premium lines after the planted field/CLU have been synced from Mapping. Detail lines will be at a "Complete" status.

Perennials: TFS #122279 was implemented in the 2021 RY using the Leaf Year definition from the CIH. This was incorrect for Pistachios; the Pistachio Handbook and the PASS validations have the Leaf Year for pistachios as follows, which supersedes the CIH: Commodity Year - Set out year + 1. The System was updated to reflect the correct Leaf Year calculations for Pistachios.

Perennials: An issue was reported where the Leaf Year was calculating incorrectly for FL Citrus Fruit (Plan 90). This issue has been resolved.

Master Yields: Some significant bugs within the Master Yield functionality were discovered internally by our software developers. These bugs were introduced with MY refactoring several releases ago as well as part of the 11.000 release. There are two issues that are at play when building Master Yield Summary units:

These two issues have been fixed within the building process of MY Summary Units. MY Summary Units will now recognize new non-summary APH records keyed and build them according to procedure.

PRF/API: An issue was reported where, when a user was updating/inputting AR sign dates via the Manage Detail Line popup, upon exit, the System was not updating all detail lines to a "Complete" status. The user had to select the Processing Status hyperlink on each individual line in order to have the System set the lines to a "Complete" status. The System has been updated to now run a Mark Complete for all detail lines on the coverage when AR sign dates are synced during the edit of a PRF detail line.