Release Notes 15.060.0

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

System Updates

Forms & Reports

DESCRIPTION ID #

Annual Forage: For the 2024+ RYs, the RMA has modified Annual Forage (0332) to reflect 12 Growing Seasons instead of 4. Sales Closing Date (SCD) is July 15th for all Growing Seasons. With this ticket, an update was made to a change implemented in the System with TFS 129055 in the 15.055 release for the Annual Forage Application that consisted of assisting with the scenario of pre-keying data and then printing the application to gather signatures. For the 2024 CY, when the Annual Forage Application is printed pre-filled, the form will print pre-filled with 2024 coverage data.

149039

With this ticket, the 2024 Fresh Market Peppers (0083) Crop Provisions have been implemented in the System.

148090

With this ticket, the 2024 Fresh Market Tomato (0086) Dollar Plan (50) Crop Provisions have been implemented in the System.

148089

Global

DESCRIPTION ID #

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

146843

Livestock

DESCRIPTION ID #

LGM: An issue was reported where, when trying to add a Livestock Gross Margin (LGM) detail line for Swine with a large number of head, a hard stop error was received upon save. The hard stop error would not allow more than 50,000 head of swine to be keyed. The hard stop error was traced back to a 2020 RY Regulatory ticket where RMA removed the LGM per endorsement and per year limitations. When the # of head limitations were removed with that ticket, "Sorry..." errors were thrown when trying to key large numbers of marketings. This was due to the simulated losses being too large to store in the database. To handle this, hard stops were added that were substantially larger than the previous RMA limitations to try to avoid the "Sorry..." errors.

With this ticket, this LGM logic has been reviewed and updated as follows:

• The # of Head inputs for LGM Swine and Cattle were updated to allow a max of 999,999 rather than the previous 50,000.
• Database columns were updated to increase the number of digits allowed on some calculated fields.
• A try-catch around the save of the premium line was added to catch the error if it still occurs to return a hard validation error about reducing the total number.

NOTE: With LGM Cattle, users can still get the error if they enter the max of 999,999 in more than 4 months with the max deductible or more than 1 month with the min deductible, due to the Liability being calculated to too many digits. The Liability column is the same number of digits that the P16 M13 shows currently, so the number of digits on it cannot be increased at this point.

149067

LRP: For Livestock Risk Protection (LRP), RMA only allows one Type/Practice combination per RY/Policy/Commodity/Effective Date combination. An enhancement was requested to add a warning to the Add New Detail Line and View Detail Line pages for LRP to alert users that a duplicate Type/Practice combination exists in the Specific Coverage Endorsement Details grid for a RY/Policy/Commodity/Effective Date combination. With this ticket, for 2024+, a new warning has been implemented on the LRP Add New Detail Line and View Detail Line pages to alert users of duplicate Type/Practice combinations across rows in the Specific Coverage Endorsement Details grid when save is initiated. This warning allows the user to continue with the save or return to the page and update rows in the grid.

147083

Mapping

DESCRIPTION ID #

An issue was found where when importing fields from SMS (Precision Ag), the field name was being updated if a new field was being created, but if the field already existed, it was not being updated. This issue has been resolved.

148948

Layers: When a user clicks the save icon for a section in the Layers panel, the System remembers which layers are turned on, the settings for each layer, and whether the layer was marked "Active". Specifically, it remembers if the Adjuster or Parcel Layers are active. This information is retained and the settings are loaded when the user returns to Mapping. With this ticket, the logic for saving the Layers preferences was updated to account for all layers in the Reference Layers, Crop Information, and TX Layer sections. Since last updated, the UDGO and NOAA Layers have been added to the Reference Layers and new Precision Ag Layers have also been added.

136011

MBAR: This ticket addressed some issues reported when printing the Map Based AR and SOI.

148730

MPCI

DESCRIPTION ID #

Annual Forage: During testing, it was found that a red error screen was displaying when a user tried to add a new coverage for the same state/county as an existing coverage. This was resolved.

148845

Annual Forage: This was clean-up ticket for some items discovered during the testing of TFS 147375 Edit/Maintain AF Coverage Changes for 12 Growing Seasons. With this ticket, the following items have been addressed:

• The Disclaimer Date on the Add New/Maintain Coverage pages is no longer allowing future dates.
• The tooltip text displays on the Productivity Factor field on the Add New/Maintain Coverage pages.
• These two validations were removed after finding they no longer applied:
• The Experience Factor must be greater than zero.
• A Dispute Date cannot be entered if a Dispute Code is not selected.
• Index Interval select was updated so that reinstating a coverage automatically selects the row's corresponding checkbox and selecting a canceled status automatically removes the row's corresponding checkbox.
• The RY is now centered on page title banner on the Add New/Maintain Coverage pages, and the word "canceled" now only includes one "l".

148754

Coverage: With this ticket, additional validations were added to the Annual Forage Add New/Maintain Coverage pages. These validations are now triggered when the correct scenario occurs:

• Selected Intervals cannot have date ranges that overlap with another selected interval.
• Interval (Practice Code) can only be used once.

148453