Release Notes 8.010.0

Beginning with the 2020RY, a new Dual Use (DU) option has been added to Growing Season 1 for Annual Forage. This ticket provides the ability to select DU, the calculation/look up for 40% of the CBV, and an Options field on the printout on the Quick PRF/Annual Forage Estimate.

The following cleanup items have been implemented for the Quick Dollar Plan Estimate:

Veteran Farmer Rancher has been added as an option within the Policy Estimator.

A request was received to allow a user to only print the premium lines that require production to be collected on the Schedule of Insurance (SOI) / Production Report. The SOI / Production Report has been updated in the following ways:

RMA released Hybrid Vegetable Seed Crop 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. Hybrid Seed Crop Provisions that will be effective for the 2020 Crop Year have been implemented. This ticket implemented the updated provisions that were released on June 26, 2019.

It was found that, when a policy had a CAT coverage with no acres and an AR Sign Date entered, those detail lines were printing on the Schedule of Insurance (SOI) and SOI / Production Report. The SOI and SOI / Production Report have been updated so that CAT coverage detail lines now only print when the acres and AR Sign Date have been entered which is how the the other detail lines print.

The Annual Forage Application has been updated in the following ways:

With this ticket, the rule for printing Land data for child lines on the Schedule of Insurance (SOI) (originally implemented with TFS #101550 in the 8.000 release) has been updated for all years. If the child line is a user created child line, a Land section will now print for the child line. An example of a user created child line is Prevented Planting. Examples of System created child lines are SE and SCO.

With this ticket, the Schedule of Insurance (SOI) has been updated for all years so all of the applicable SOI formats print for the coverages on the policy. Previously, when PRF was on a policy with other row crops, only the PRF SOI was printing.

DRP: Regulatory changes were announced on 4/22/2019 for the 2020 Reinsurance Year for Plan 83 - Dairy Revenue Protection (DRP) with PM-19-022. The following items have changed for DRP for the 2020+ RYs:

NOTE: Changes called out in this ticket are specific to Plan 83 – Dairy Revenue Protection (DRP) only.

Users reported being unable to sync from the Mapping module to the Acreage Report (Sync to AR functionality) if an NOL existed for the crop. With this ticket, the System will now allow sync to AR as long as no signature date exists yet for the crop or if the NOL is voided/withdrawn.

Users requested to have the ability to key only the year and no month for Set Out and Grafted dates in the Plant panel. This has been implemented.

CIMS: Users requested the addition of the total cropland acre by farm number (FN) on the printed CIMS report. Now, for the 1- and 5-year reports, Tract displays in the first column for the first line, Total Cropland Acres includes cropland from all tracts within the FN, and Total Acres includes all acres (cropland and non-cropland) from all tracts within the FN.

The Mapping Module was updated with the ability to set the HR (High Risk) checkbox on the Plant panel for a line and have it synced to the AR from Mapping.

NOTE: If multiple map areas exist for a field, the System will not create a child line for the different map areas. That will be handled with TFS #105562. For this ticket, if multiple map areas exist, then on sync, the System will set HR flags as: 1) Multiple high-risk map areas (e.g., AAA and BBB): The System will not set the map area on sync; users will need to verify which applies and manually set. 2) High risk/non-high risk: The field will be marked as high risk with the map area set on sync.

It was reported that child lines were not being pushed from the source policy to the companion policy when the acres were keyed through mapping. This has been corrected.

The June 2019 CLU file has been downloaded from the RMA and implemented in the System.

Companion Policy: An issue was identified with Companion Policy functionality when related STAX coverages existed. An AIP reported that after establishing companion units, when premium lines were updated on the source policy that had related STAX coverages, the companion policy MPCI lines updated correctly but their related STAX lines did not. Companion Policy logic has been corrected to account for related STAX coverages.

Companion Policy: Companion Policy functionality previously did not account for companion links when PP claims were processed and acres were rolled/borrowed creating new child lines. With this ticket, Companion Policy functionality has been updated so that any PP child line created by the claim roll will NOT get any companion linkage flags.

Fast Edit CLU: It was discovered that Planted Acres in the Fast Edit CLU banners, which are dynamically changed when crops and units are selected, were being displayed in the wrong banner for the appropriate Land Description. This was a widespread bug affecting all crops and Land Descriptions within Fast Edit CLU. A code fix was implemented to change the sorting of the Land ID groups to correctly display Planted Acres.

VFR: As part of the new Veteran Farmer Rancher program issued by RMA for 2019 crops with a SCD after 12/20/2018 and for all crops in the 2020+ RYs, a couple of APH benefits apply. First of all, Yield Adjustments are applied at 80% of the t-yield rather than the typical 60%. In addition, a Veteran Farmer Rancher can utilize another person's history if they were involved in the decision making or physical actives of the farm or ranch. With this ticket, the APH benefits for VFR have been implemented. These include:

WFRP: When a new commodity is reported on the Revised Farm Operation Report and that same commodity was not reported on the Intended Farm Operation Report, RMA requires null values to be sent in the intended fields on the P19A record. However, the System was not allowing the user to key blank or zero values in the intended fields on the Commodity page and instead was always requiring intended values greater than zero. To account for this scenario, a new checkbox, New Commodity, has been added to the Commodity page. This checkbox will only display when the Revised Report checkbox is selected and will require zero values in the intended commodity fields.

NOTE: TFS #105152 addresses the transmission changes related to new commodities on the Revised Farm Operation Report. When the New Commodity checkbox is selected, the transmission logic will send all intended values as null on the P19A record.

A bug was reported where users were not able to create an Internal Native Sod Written Agreement for a CAT Coverage. The Add New Written Agreement page has been updated to allow Native Sod Written Agreements to be created for CAT coverage.

VFR: As part of the new Veteran Farmer Rancher (VFR) functionality, a new VFR Qualification Type field was added to the BFR/VFR Application page. This field was designed to only display when the Application Type is "Veteran Farmer Rancher". During internal testing of the updates to the BFR/VFR Application page, a bug with this new field was identified. The System was correctly displaying the field when VFR was the selected Application Type; however, after save of the page, the VFR Qualification Type field was disappearing. With this ticket, the VFR Qualification Type field was updated so that it no longer disappears on save of the BFR/VFR Application page.

An issue was reported by an AIP where acres were being removed from the detail line but not from the CLU when an underwriter accidentally tried to cancel/transfer in the wrong RY when commission was paid on the policy (hard edit was correctly received for the cancel/transfer).

In reviewing the issues reported by the AIP, it was found that the Maintain Coverage page was correctly displaying the warning: "Acres Exist for this Coverage. If this Coverage is canceled all acres, plant dates and associated premium/liability information will be removed from the detail lines." However, when running the same test on the Coverage tab, the System was not triggering the warning as it should have been. The System was removing all acres, plant dates, and associated premium/liability information from the detail line, but the user did not have the ability to cancel out of the functionality in order to not remove all information from detail lines. Also, it was found that when all acres, plant dates, and associated premium/liability information were removed from the detail line and CLU acres were attached the detail line, the CLU acres were not being removed as they should have been.

With this ticket, two changes were made:

When a user was setting up an ARCH/Crop Hail policy and de-selected the Factor Ins/Acre checkbox, the System was not removing the Factor Ins/Acre. Upon the submit of acres, the Insurance per Acre was still being calculated by Share for the Cotton Max Stepladder Endorsement. A correction was made to ARCH/Crop Hail policies so that if the Factor Ins/Acre checkbox is de-selected, then upon the submit of acres, the Share % will not be taken into account for the Insurance per Acre for those lines that have the Cotton Max Stepladder Endorsement on them.

A correction was made to the dashboard time stamp. It was discovered that, when logged in as an agent in a different time zone than Central, the Dashboard was showing different users different times on the time stamp for the dashboard. All timestamps will now be recorded in the Central time zone.

A 2020 Special Provisions Update was made available from RMA on 6/13/2019. The following Special Provisions for 2020 have been downloaded (2020_SPOI_0430.zip):

An ICE 2015 update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2015:

An ICE 2016 update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2016:

An ICE 2017 update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2017:

An ICE 2017 update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2017:

An ICE 2018 update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2018:

An ICE 2019 update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2019:

An ICE 2020 update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2020: