8.035 Release Notes

A request was received to remove "Planted" from the Crop Summary "Total Acres" label on the Schedule of Insurance (SOI). The following changes were also made to the SOI / Production Report to keep the Crop Summary sections in sync with each other:

NOTE: No changes were made to the SOI formats for Annual Forage, API, PRF, and WFRP.

A request was received to print additional coverage lines on Page 1 of the API / PRF Combo Form as only one coverage line was printing on this page.

RMA has introduced Point of Reference with the 2020 Rainfall and Vegetation Index Handbook as an acreage reporting requirement to include Latitude and Longitude with Acreage Reporting. The API / PRF Combo Form has been updated with the following changes for all years:

NOTE: This data will be pre-filled in the field in a later release.

Now that users can select the Dual Use (DU) option for Annual Forage, an Option field was needed on the Annual Forage Acreage Report. Base form formatting updates were also implemented. The Annual Forage Acreage Report has been updated in the following ways:

RMA released revised TX Citrus Trees 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. Revised TX Citrus Trees Crop Provisions that will be effective for the 2020 CY have been implemented.

PRF: By design, once a PRF coverage has been saved for the first time, the Irrigation and Organic Practice fields become read-only. AIPs are reporting issues with agency users keying an Irrigation and/or Organic Practice when one is not applicable. While there is a message on the page instructing users when an Irrigation and/or Organic Practice should be keyed, the message was very lengthy and users may not have been reading it. In an effort to minimize these keying errors, the on-screen message stating when an Irrigation and/or Organic practice should be keyed has been shortened. In addition, the message will display in bold red text. The updated message reads: "Selection of an Irrigation or Organic Practice is only applicable if the Grower has elected different coverage levels or productivity factors by practice."

APH: TFS #103988 added a new banner to the View and Maintain APH page called Additional Company Info. Under the banner is a Late Processed Flag field that only displays for crops specified in the D00066 ICE Table. This field allows AIP users to set an LRR Waiver on the APH. Previously, the Additional Company Info banner was displayed on all APH pages even if the crop was not listed on the D00066 ICE Table and did not qualify for the Late Processed Flag field. With this ticket, the banner was removed from the View and Maintain APH pages for commodities not listed on the ICE Table such as Category C perennials as it was confusing to users.

Caneberries: In the 8.025 Release with TFS #96117, functionality was implemented for Caneberry detail lines and rating. As part of this ticket, a suspension was also implemented that was designed to trigger when less than 4 years of continuous history exists for the Commodity Type. During internal testing, it was found that this suspension was not working. With this ticket, the suspension logic was updated so that the suspension triggers when the following criteria exist:

NOTE: TFS #107435 is related to this ticket.

Plan 55: An issue was reported that the suspension, "Optional Unit numbers may only be applied if a Contract with a type of 'Production and Acreage' is applied to the Coverage' was incorrectly triggering on Hybrid Corn Seed(0062)." The System was adjusted to not trigger the suspension for optional units if the following requirements are met:

Quotes: Internal testing identified a bug that resulted in quotes defaulting sign dates to the current system date when quotes were being created. It's uncertain how long the bug was in production. This bug has been corrected because sign dates should never default to the user interface on a new quote or policy.

SCO: An issue was reported through an AIP where the SCO Coverage Percentage was not allowing the user to update the field with a value other than 55% when the coverage was CAT coverage. The System was updated and it will now allow a user to update and change the SCO Coverage Percentage field with a value other than 55% coverage. Users will be able to key a value from 50% - 100%.

Written Agreements: Recently, adjustments were made as to how the System determines PP eligibility when a written agreement is applicable. TFS #103910 was implemented to update the WA ADM_ICE file import to pull in the ADM 01220 table that wasn't previously importing. RMA moved the WA PP reference from an ICE table to the WA_ADM Guarantee Adjustment (A01220) table for the 2019 RY.

TFS #105414 was implemented to update the WA rating logic to use the WA ADM ICE ADM 01220 table when determining whether the PP checkbox should display. The logic added under this ticket states that if a record is not found in the WA ADM Guarantee Adjustment table for the RY, WA #, State, County, Crop, Plan, Type, Practice, and Map Area, the System will look at the Standard (non-WA) ADM Guarantee Adjustment table for verification. If data was not in either table, the System will determine PP is not applicable.

Following deployment of these changes, 1 AIP reported continued errors with 1 policy. Although the user was able to select the PP checkbox on a WA-related line, the System was still not calculating a correct guarantee and premium. The developer determined an adjustment to the logic was required. The StateCode and CountyCode were removed from the logic on the GuaranteeAdjustment table (from the WA ADM). This was causing an issue when there were a reference state and county that was different from the actual state and county. The WA ADM GuaranteeAdjustment table always has the records listed within their actual state and county. Because the lookup is by WA Number, there is no need to also have the StateCode and CountyCode as part of the logic.

Written Agreements: AIPs reported an issue where certain Written Agreements did not roll to the next Reinsurance Year (RY). Research determined these Written Agreements did not roll due to a missing Sales Closing Date. The Sales Closing Date was never populated on these Written Agreements because a user never resaved the Written Agreement following the import of the Written Agreement file and, therefore, an SCD never populated. In an effort to prevent this issue in the future, a suspension was implemented that will trigger when the following criteria exist:

Written Agreements: The 2020 RY Written Agreement Handbook has new wording in regards to MCEU. The 2020 RY WAH states that MCEU is not applicable for OP and XC Written Agreement types. With this ticket, logic was added to prevent users from creating a Written Agreement if the insured has elected MCEU on the coverage. Validations were added to the Add Written Agreement, Maintain Written Agreement, and Add New Coverage pages when the Written Agreement Type is "OP" or "XC".

NOTE: Changes called out above are only applicable when the Written Agreement type is "OP" or "XC".

CIMS: MCT identified a bug with the drag and drop column header feature on the CIMS Producer Summary page. The drag and drop column header feature is a common user feature on all grids within the System and allows the user to filter and sort the columns differently. An error was being returned when columns were modified in the filtering on this page, however. This bug has been resolved.

Perennials: Improved work flows for entry of PAIR dates were requested by AIPs if the dates were the same so users didn't have to enter the date on each premium line. In TFS #93968 for FL Citrus crops, a change was implemented and additional logic was added that would push the Last Inspection Date from the PAW to the detail line. FL Citrus is the only crop that contains the Last Inspection Date in the PAW. All other Perennial premium lines contain the PAIR Date which is then used to trigger suspensions. The PAIR date for Perennials is currently keyed on the detail line and the System then pushes the date to the PAW and the date is read-only and not an editable field on the PAW.

For the scope of this ticket, the same logic as FL Citrus will be adopted for the date of Last Inspection and PAIR fields being updated amongst the PAW and detail lines no matter where the dates were updated. The PAIR Date field will be adjusted to be an editable field and will no longer be just a read-only field as it currently is on the PAW.

Upon Save/Save and Exit of the detail line or PAW, the System will compare the PAIR dates from each area and apply the latest date to both fields. The PAW and the Detail Line (PAIR Date) will be in sync with one another and always store the latest date entered by the user. In order for a user to be able to correct a date, and if it is an earlier date, a checkbox, Correct PAIR Date, has been added to the detail line, and a checkbox, Correct Last Inspection Date, has been added to the PAW.

Insurance Per Acre: IPA limit issue was found when the user was editing the IPA on a parent line and selecting "Save & Next" after canceling out of the child line, it was giving an error message that IPA was too high when the user was changing the amount back to the original IPA. This has been corrected.

ICE: Increased Coverage Election for Almonds needed a modification to the AY policy option page. Almonds uses a set ICE Price that is elected at the time the coverage is set up instead of having a calculated ICE Price similar to Corn, Soybeans, and Wheat.

With this ticket, the Sales Record page for AY Almonds on Increased Coverage Election policies will now have an ICE Price field with the elections of $.25 or $.50 to select from at the time of policy creation. This ICE Price will also now carry into the Policy page and be used to calculate premium. The % of Available Price column will default to N/A on Almonds as that is not an election made for this commodity.

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

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

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

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 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: