Release Notes 10.030.0

These release notes provide brief descriptions of changes included in eHarvest 10.030.0.

System Updates

Forms & Reports

DESCRIPTION	ID #
Provisions: RMA released ARPI Provisions for the 2022 and succeeding Crop Years (CYs). The ARPI Provisions that will be effective for the 2022 RY have been implemented.	128424
Provisions: The 2022 Hurricane Insurance Protection (HIP) Data Provisions and Wind Index Endorsement were implemented.	128421
SPOIs: Wheat AYP SPOIs were updated and made available from RMA on July 21. The Special Provisions for 2022 have been downloaded and implemented.	128936
MPCI App & STAX App: With this ticket, the main MPCI Application form was updated with base form standards and requests. Additionally, the 2022 DSSH updates to the STAX Application were implemented. These updates are for all years.	126920
Provisions: RMA released Triticale Crop Provisions for the 2022+ Crop Years (CYs) in June 2021. The Triticale Crop Provisions that will be effective for the 2022 RY have been implemented.	127961

Global

DESCRIPTION	ID #
The Online Help Site was updated with topics as well as with current release notes.	128082

Livestock

DESCRIPTION	ID #
An issue was found where users were able to future date the Insured and Agent Signature Dates on Livestock coverages with no errors being thrown. The Agent and Insured Signature Date validation logic on the Add New Policy, Add New Coverage, and Maintain Coverage pages for Plan 81 (LRP), Plan 82 (LGM), and Plan 83 (DRP) has been updated to not allow future dates to be entered and saved. If a user tries to save an Agent Signature Date or an Insured Signature Date that is greater than the current System date, a hard stop error will now be triggered to notify the user of the issue and prevent the save. NOTE: For NEW LGM Coverages, the System will default the signature dates to correspond with the selected Insurance Period. When LGM Coverages roll from the prior RY, the signature date fields will be blank and the user will need to key updated sign dates for the applicable Insurance Period. Additionally with this ticket, a formatting issue was fixed so that if a user enters a date in the MMDDYYYY format and tabs out of the date field, the System will now automatically correct the format as it does within other pages in the System.	118723
An issue was found where, when notes were added via the Information Messages page (Coverages tab > Coverage Processing Status link) for Livestock policies (MPCI policies were not affected), they were not displaying in the Notes grid below. Users had to navigate to the Notes tab of the policy to see the saved notes. The Coverage Mark Complete Results page was updated to show items in the Notes grid based on whether the user is viewing a Livestock policy or an MPCI policy. Previously, this page was only loading notes associated with MPCI policies, so it was only working for MPCI coverages; Livestock policies were not loading anything.	123862

DESCRIPTION

ID #

An issue was found where users were able to future date the Insured and Agent Signature Dates on Livestock coverages with no errors being thrown. The Agent and Insured Signature Date validation logic on the Add New Policy, Add New Coverage, and Maintain Coverage pages for Plan 81 (LRP), Plan 82 (LGM), and Plan 83 (DRP) has been updated to not allow future dates to be entered and saved. If a user tries to save an Agent Signature Date or an Insured Signature Date that is greater than the current System date, a hard stop error will now be triggered to notify the user of the issue and prevent the save.

NOTE: For NEW LGM Coverages, the System will default the signature dates to correspond with the selected Insurance Period. When LGM Coverages roll from the prior RY, the signature date fields will be blank and the user will need to key updated sign dates for the applicable Insurance Period.

Additionally with this ticket, a formatting issue was fixed so that if a user enters a date in the MMDDYYYY format and tabs out of the date field, the System will now automatically correct the format as it does within other pages in the System.

118723

An issue was found where, when notes were added via the Information Messages page (Coverages tab > Coverage Processing Status link) for Livestock policies (MPCI policies were not affected), they were not displaying in the Notes grid below. Users had to navigate to the Notes tab of the policy to see the saved notes.

The Coverage Mark Complete Results page was updated to show items in the Notes grid based on whether the user is viewing a Livestock policy or an MPCI policy. Previously, this page was only loading notes associated with MPCI policies, so it was only working for MPCI coverages; Livestock policies were not loading anything.

123862

Mapping

DESCRIPTION

ID #

A new mapping layer for August 2021 was released by the RMA and has been implemented in the System.

129688

PAW: In order to get to PAW information already keyed on the server side, including Density and Stand Percent, a PAW Line selector was added to the Planting panel, which allows the selection of an existing PAW line that is associated with a premium line (the user must select the premium line in Mapping to get PAW lines) which then prefills all PAW information as stored on the server.

125341

PRF Wizard: Users requested that when they click on a specific field in the PRF wizard, the field will then be highlighted on the map. This has been implemented. In the PRF Wizard, click on the field number in the field listing to highlight the single field; then, click on the # of fields link to highlight all fields that are part of the farm/tract.

129034

PRF: Users requested that the PRF Field Listing export be added to the Mapping print menu. This has been implemented.

123832

RLUs: There was a need to maintain RLUs separate from the Grower Fields layers so that users could delete/re-add Grower Fields without losing previously approved RLU information. To do this, users can turn on the RLU layer (the user's rights will affect how this layer displays—all objects vs only RLUs). Then, they can go to Tools > Maintenance. The RLU Maintenance popup opens and displays any RLUs that exist. For each RLU, a select box, thumbnail image of the field, acres, RLU status, RLU ID, and details hyperlink will display.

There are two important buttons—Assign RLU and Submit to RMA—and one icon—the Delete icon—on the RLU Maintenance popup:

•

Assign RLU—When using Assign RLU, objects selected from other layers (i.e., Grower Fields, Adjuster Fields, CLU) are copied into the RLU layer.

System will create new object for the RLU layer.

System will also set the RLU Status to Assigned and apply the AIP RLU Key, Ownership, and RLU AIP Code automatically.

If selected objects overlap an existing RLU, a message will display indicating that the System cannot add an RLU where one already exists.

If selected objects (individually) are > 5000.00 acres, a message will display indicating an RLU cannot exceed 5000.00 acres.

•

Submit to RMA

If status = Assigned or Error, the System will update the status to Submitted and send to RMA.

If status = Deleted (and not already sent), the System will leave the status as Deleted and send to RMA.

If status = Submitted, Approved, or Rejected, the System will not perform any action.

•

Delete (icon)

If status = Accepted, the System will update the status to Deleted and will display in red font with (Pending) until the field is submitted to RMA for deletion.

Once submitted to RMA (Deletion Submitted Date is not null), the font will display in black and no longer show (Pending).

A previously Accepted RLU that is deleted will be displayed for users when the Hide Deleted checkbox is not selected.

If status = Assigned, Error, or Rejected, the object and all accompanying information will be completely deleted from the System.

If status = Deleted (and has previously been transmitted as deleted to RMA) or Submitted, the System will not perform any action.

The Copy Fields tool will allow a user to associate an existing RLU to create an object for Grower Fields or Adjuster Layers.

129410

MPCI

DESCRIPTION	ID #
Enterprise Units: Several System modifications have been required to support Enterprise Units by Type (ET) (first discussed in Release 10.020). TFS #127699 addressed the Coverage functionality and TFS #127700 addressed the detail line and validation logic needed to support ET. For this ticket, an enhancement was added to the coverage functionality to improve user experience. The enhancement added a new field for “Selected Types:” to show in a read-only format with the type codes that are selected with the Select Type(s) for ET multi-select dropdown. The purpose of this new field is to show the selected types for ET because the multi-select dropdown cannot show the types selected without navigating into the dropdown. This new field will be modeled after the Crop Options multi-select dropdown and subsequent Selected Options read-only field. This new Selected Types field will show the type codes so that the user can see what is selected without going back into the Select Type(s) for ET multi-select dropdown. Enterprise Units by Irrigation Practice (EI) and Enterprise Units by Cropping Practice (EC) both use single-select dropdowns that persist the selection on the page, so no changes were made for EI/EC on the coverage pages.	128934
Enterprise Units: The Enterprise Units by Type (ET) rating logic was added for Wheat, Dry Beans, and Dry Peas for Insurance Plan Codes 01, 02, 03, and 90. Enterprise Units by Type (ET) was first discussed in Release 10.020.	127704

DESCRIPTION

ID #

Enterprise Units: Several System modifications have been required to support Enterprise Units by Type (ET) (first discussed in Release 10.020). TFS #127699 addressed the Coverage functionality and TFS #127700 addressed the detail line and validation logic needed to support ET. For this ticket, an enhancement was added to the coverage functionality to improve user experience. The enhancement added a new field for “Selected Types:” to show in a read-only format with the type codes that are selected with the Select Type(s) for ET multi-select dropdown. The purpose of this new field is to show the selected types for ET because the multi-select dropdown cannot show the types selected without navigating into the dropdown. This new field will be modeled after the Crop Options multi-select dropdown and subsequent Selected Options read-only field. This new Selected Types field will show the type codes so that the user can see what is selected without going back into the Select Type(s) for ET multi-select dropdown. Enterprise Units by Irrigation Practice (EI) and Enterprise Units by Cropping Practice (EC) both use single-select dropdowns that persist the selection on the page, so no changes were made for EI/EC on the coverage pages.

128934

Enterprise Units: The Enterprise Units by Type (ET) rating logic was added for Wheat, Dry Beans, and Dry Peas for Insurance Plan Codes 01, 02, 03, and 90. Enterprise Units by Type (ET) was first discussed in Release 10.020.

127704