Release Notes 16.070.0

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

System Updates

Forms & Reports

DESCRIPTION ID #

MCT noticed a sentence in the verbiage under the title of the Master Yield (MY) Comparison Worksheet that was removed due to the 2022 enhancement that was done to allow quoting with and without Master Yield for new or transferred policies.

Changes that were made:

Applicable for all years.

"This form only supports calculations for coverages that had a Master Yield in place in the prior RY and have been updated with an AIP-applied Master Yield Utility." was removed from under the title.
Version date was updated to "03-2024".

136218

2024 RY SPOIs released on Jan 9, 2024 Pecan Trees 1/31 CCD 5/15 SCD.

Changes that were made:

Pecan Trees 2024 SPOIs were updated and made available from RMA on Jan 9. The Special Provisions for 2024 were downloaded from 2024_SPOI_0131.zip.

156114

MCT noticed that in the #9 in the "Also, I understand..." section was missing on the Nursery Value Report (NVR).

Changes that were made:

The form logic was updated to display #9 in the "Also, I understand..." section.

157994

RMA released a technically corrected 2022 Dry Bean Revenue Endorsement (DBRE) on March 11, 2024. The DBRE printed with YP (01), RP, (02) and RP-HPE (03) plans.

Provisions printed with the MPCI Policy Declaration Page when the print option to print provisions with the form was selected. The MPCI Policy Declaration Page was available to print from the MPCI Print tab in an individual MPCI policy and from the Batch Printing menu.

Changes that were made:

The system was updated to print the technically corrected 2022 DBRE provision.

158295

Livestock

DESCRIPTION ID #

This ticket was to print the "Grantee" in the Grantee Statement on the Livestock Risk Protection (LRP) Specific Coverage Endorsement (SCE) form.

Changes that were made:

Updated for all years.

LRP SCE form was updated to print the "Grantee" in the Grantee Statement.

155794

Mapping

DESCRIPTION ID #

February 2024 CLU Layer.

Changes that were made:

RMA released a new CLU Layer - February, 2024

For Mapping Module Users:

Open mapping for a policy/grower.
Turned the CLU Layer on.
Verified the layer displayed and CLUs can be selected/copied up to the field layer.
Selected the copied CLU and verified the CLU Date was: 02/2024 on the Field Info Tab.

For Non-Mapping Module users:

From the Land ID screen, viewed and attached a planted CLU to the Land ID and clicked Save Fields.
After save was completed, clicked on the field hyperlink.
In the Edit CLU dialog, verified that the CIMS CLU Date was set to 02/2024 to verify that the CLU data pulled from the latest CLU Layer.

158116

MPCI

DESCRIPTION ID #

The Online Help Site was updated with topics as well as with current release notes.

156598

While testing 16.065 ticket 157281, MCT found that Claim Records were not loading into SYPR Mode of Fast Edit PR if Policy Production Records existed before the Claim was Paid. Instead, the policy production records were loading. If claim production records exist, they should always take precedence over policy production records.

This was happening because of some logic in the nightly Claim Production roll job that was not allowing Claim records to load into Fast Edit PR until the APH was updated with the claim information in the next RY. This was only impacting new or updated claim records that were flagged to have the APH updated during that night's claim production roll.

Changes that were made:

When determining when to load claim production records into Fast Edit PR, it shouldn't matter if the APH was updated in the new RY yet or not. Therefore, the Claim Production roll logic that was requiring this was removed.

158248

System Infrastructure

DESCRIPTION ID #

A new security validation was added to the MPCI, Livestock, and Private Product policies within the system that looks for invalid characters ($ : <> and !) within the filename of the files being uploaded and attached to the policies. If the filename contained invalid characters a popup message appeared and an Elmah error was created.

Changes that were made:

The User was unable to attach a file with an invalid character, and trigger the following:
The User received the following error message: "Error occured when proccessing current request."
An Elmah Error occured with the message: "File names must only contain letters, numbers, dashes and underscores. Please correct the file name and try again."

157386