Release Notes 8.030.0

Batch Printing: An enhancement request for Batch Printing was received to give users the ability to only print the corresponding detail lines for the selected Acreage Reporting Date(s) on Acreage Reports. This ticket added a new base Batch Printing print option, "Print detail lines for selected Acreage Reporting date(s)", to the following Acreage Reports:

Also, an update was made to the Acreage Report for the Shareholder field to grow to 3+ lines of shareholder data when the CLU Section is printed with the Acreage Report.

RMA released a Catastrophic Risk Protection (CAT) Endorsement that is effective for the 2020 and succeeding Crop Years (CYs) for all crops with a contract change date on or after June 30, 2019 as well as for the 2021 and succeeding CYs for all crops with a contract change date prior to June 30, 2019. 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. The CAT Endorsement that will be effective for the 2020+ CYs for all crops with a contract change date on or after June 30, 2019 as well as for the 2021+ CYs for all crops with a contract change date prior to June 30, 2019 has been implemented.

RMA released an SCO Endorsement for the 2020 and succeeding Crop Years (CYs). 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. The SCO Endorsement that will be effective for the 2020+ CYs has been implemented.

RMA released ARPI Provisions for the 2020 and succeeding Crop Years (CYs). 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. The ARPI Provisions that will be effective for the 2020+ CYs has been implemented.

RO: During the 2020 DSSH review, the following updates were identified for the RMA RO Determined Yield Request and have been made for all years:

WFRP: A request was received to print the Commodity Name and Code on the WFRP Combo Form Farm Op Report page when the form is being pre-printed for next year. The Coverage Level was also not printing on this report. These changes and others were made for all Crop Years unless otherwise specified with this ticket:

MCT identified that a telerik was occurring when there was an alpha character in the Field Number. This type of field number (e.g., 2A, 2B) is set by the FSA and comes in through the CLU layer. MCT updated the printing land coding functionality to not print a telerik error when there is an alpha character in the Field Number. No forms were updated with this ticket, however⁠—just the printing land coding functionality.

NOTE: A user cannot enter an alpha character into the field; a query would need to be done to see if there are any for the AIP that fit this scenario.

This change will impact any form that can prints Land on the form, and MCT focused testing on the following forms:

Other forms were tested, but the main focus of testing was the above forms.

Reminder: When all land has not been selected to print, the primary land will print. When all land has been selected to print, the Primary Land ID will print first. If there is not a primary Land ID selected, the form will print the first Land ID for the unit.

NOTE: MCT found a few minor cleanup items for the Perennial Combo Form that will be worked as soon as they can be fit into an upcoming release. 1) When a Grower has more SBIs than what will fit on page 1 of the Perennial Combo Form, the remaining SBIs print on the SSN_EIN page; there are one too many blank SBI lines printing, so an additional SSN / EIN page prints when it should not. 2) The ARH page has the Measurement Services Statement and Legend being pushed to the next page. Additionally, MCT found a minor cleanup item for the Production Report / Acreage Report that will be worked on as soon as it can be fit into an upcoming release. The land should be top-center justified instead of center-center justified.

Updates have been made to the Mapping module's Hail Data layer. When the Hail Data layer is selected in the Layers panel and a date range is entered for Hail events, the following enhancements were made to the display of the Hail Data layer and the Current Map and Map Booklet printouts:

Perennials: TFS #16817 introduced functionality for users to use the "BF" descriptor to the APH to identify transfer history for Beginning Farmer Rancher (BFR). While that functionality was being developed, it was found that, for Pecans and Strawberries, the APH Override checkbox column did not exist. With this ticket, the Override * column was added in the APH grid to allow users to designate BFR transfer history if applicable for Strawberries and Pecans.

Transmissions: The PASS AIP Test released on 8/21/19 called out the implementation of CR 185838. With this, a new output field, which RMA is calling Disaster Assistance Amount, has been added to the P21 record (field 65 is being inserted for this field). PASS will calculate a Disaster Assistance Amount, which will be a percentage of the prevented planting claim submitted on the P21 record. This percentage will now be captured in the import of a return PASS file and stored in the database for use by the Claims team.

Companion Policy: It was internally discovered that the MpciPremiumLine.CompanionFlag was getting dropped after save of incomplete premium lines if they were missing AR Sign Dates. This was discovered through research on TFS #107290. Some necessary fields were added on the backend to eliminate the Companion Flag being dropped from the premium line.

Navigation: In the 8.020 Release, with TFS #105478, an enhancement was made to the user navigation when leaving the Land ID popup (if accessed via the Detail Lines tab). This enhancement was intended to help users when working a coverage with a lot of detail lines so that the user was returned to the same place on the Detail Lines page from which they entered the Land ID popup. With this functionality, the System highlighted the line the user entered the popup from so the user could easily identify their last line worked. During UAT of this functionality, a few issues were identified and have been resolved with this ticket:

Calculation of a premium discount (e.g., BU discount factor) is based on planted acres only. However, any applicable discount applies to both planted and PP acres for premium calculation. A policy was submitted to the Help Desk where a factor less than 1.000 was applied to the premium calculation of a unit where there were only PP acres reported. If all acres are PP, the System will now correctly set the factor to 1.000.

Each Reinsurance Year (RY), the System's default year is updated to the most current RY. The default year controls the internal processing UI pages (e.g., Add New Policy, Add New Coverage, etc.) in addition to pages like the Internal Transfer Wizard RY dropdown. The scope of this ticket changed the default year from 2019 to 2020 in advance of the 8/31 and 9/30 SCDs.

A bug was reported with Native Sod and prevented planting (PP) acreage. Prevented planting is only allowed on Native Sod when Native Sod acreage makes up less than 5% of total acres. Because of this, when the PF option is elected on the coverage, rather than the System automatically applying the PF option on detail lines designated as PP, if the detail line is marked as Native Sod, the user has to manually apply the PF option, if applicable. The bug identified was that the System was incorrectly using the PF option to calculate premium, even when it was not selected on a Native Sod detail line marked as PP. The premium logic has been updated to only apply the PF option when calculating premium and liability if the PF option is actually selected on the detail line.

NOTE: Any detail line currently in error for this issue will need to be resaved following the 8.030 release.

An issue was identified when a user was using Additional Functions within an MPCI policy. When the user selected to use the Copy Detail Line function from the Additional Functions dropdown, the Save & Exit button on the popup wasn't working. The user was able get the detail line to copy but had to click Cancel to actually exit the popup. The same issue was identified if the user was utilizing the Copy APH/PAW function. A null reference exception in the validator was found to be causing the issue and has been removed.

NOTE: During internal testing, an issue was found with the Copy Detail Line tool when Written Agreements exist. TFS #82915 will correct this issue.

APH: An issue was reported where, for the 2019 RY, the t-yield was not being pulled into the APH Database. The issue was narrowed down to Added Land - Variable t-yield units with New Producer status. It was found that during APH calculation, in the case of Skip Row, the System was requiring at least 1 year with acres in order to apply New Producer logic. This old logic was removed.

Detail Line: When discussing TFS #107290, an issue was discovered with the "Incomplete" processing status on detail lines even though AR sign Dates were applied to the coverage. It was found that some validations that were implemented within Fast Edit AR for contracts and the CP crop option (TFS #98646 and #102737) were not set up to check the validations for the legacy Maintain Detail Line page and the Processing Status logic.

With this ticket, the System has been updated to run the same contract and CP crop options validations on the legacy Maintain Detail Line page as well as the Processing Status logic as those that were implemented for Fast Edit AR.

NOTE: The changes made on the legacy Maintain Detail Line page are not applicable to Peanuts, as they are processed through the Additional Functions dropdown OR Fast Edit AR.

Suspensions: With TFS #44879, the System currently allows that a policy can have one coverage for Barley with YP(01) and the specialty type checkbox applied and a second coverage with RP/RPHPE Plan 02 or 03. The user also has to have a contract keyed for the YP(01) with a specialty type applied to that contract in order to not receive the suspension upon Mark Complete for the duplicate coverage warning when multiple coverages exist for the same RY/State/County/Crop. If no contract has been applied to the YP(01) coverage and acres are zero, the System will trigger the duplicate coverage warning. For the scope of this ticket, a requirement has been added to the current code that the suspension not trigger unless acres are greater than zero, an AR Sign Date exists, and no contract has been keyed.

Peanuts: When testing logic for an issue that was reported for TFS #107290, it was found that on a Peanut policy the detail line status was not going to a complete status when a contract had been keyed and attached to the coverage for Peanuts. Back on TFS #98646 and #102737, logic was put into place to allow the user to be able to apply the CP option and the contract price election within Fast Edit AR.

Peanuts is processed differently for contracts than normal contracted crops, and the functionality was implemented in TFS #88808. The contract is added via the Additional Functions dropdown or from within Fast Edit AR when the Apply Contracts checkbox is selected to attach the contract to detail lines where acres are greater than zero and the approved yield is greater than zero. The user could previously apply the contract to the coverage BUT when the detail line was marked as dirty and the user saved and exited from Fast Edit AR, they were receiving an error that a contract price must be selected. This error should not have been received for Peanuts.

For the scope of this ticket, logic for Peanuts has been corrected so that the System will not throw a hard error that a contract price must be selected if the crop is Peanuts, as Peanuts contracts are applied through the Additional Functions dropdown OR Fast Edit AR with the Apply Contracts checkbox. Therefore, no contract price needs to be selected in order to be able to save and exit from Fast Edit AR.

Peanuts: An issue was reported on Peanuts where the System was using uninsurable acres when calculating the contract's weighted average price value. Peanuts logic has been updated so now when the System calculates the WAPP (contract price), it excludes uninsurable acres from the calculation and does not apply the WAPP to the uninsurable premium lines.

Perennials: An issue was reported where, when a user changed type codes within the Maintain Coverage UI, the crop options were not updating accordingly with all options available per actuarials when the type was updated. This issue has been resolved. The System will now update the crop options pick list accordingly when selections for crop type, coverage level, and price percentage have been elected.

Continuous/Annual Hail: It was found that, when a user changed the optional endorsement to increase the IPA amount, the System was not validating the IPA Max limit. This has been corrected.

On policies that had multiple county and crop coverages, when the refresh log was displaying a message about 1 of the coverages not qualifying, it was listing the same message for each coverage, including those that will qualify. On policies that have multiple county and crop coverages, the refresh log will now list the specific coverage that does not qualify and will no longer list the message as a default on all coverages.

Previously, if a user wanted to select multiple detail lines on a Private Product policy to, for example, delete lines, they had to select them one at a time. With this ticket, a checkbox has been added to the heading at the beginning of detail lines that will allow users to select all applicable lines on the Hail, Named Peril, Production Hail, or Replant policies. When this checkbox is selected, the System will select all detail lines that are able to be amended on the policy at once. Likewise, the user can deselect this checkbox and the System will deselect all detail lines that were selected as a result of selecting the checkbox originally.

NOTE: At times, like when a claim is present on a unit, the user will not have the option to select a detail line even with Select All indicated, as that line will not have a selection box to the left of the line number link.