Related
Release Notes 7.115.0
These release notes provide brief descriptions of changes included in AgWorks 7.115.0.
Videos
System Updates
Forms & Reports
DESCRIPTION | ID # | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The Schedule of Insurance form was updated to implement the following changes:
|
101557 |
||||||||||||||||||
It was found that the AIP tagline in the footer that was turned on with TFS #86683 was turned off in error. The below language was added to the AIP footer tagline that prints on the Statement Page in the same place that the "See last page..." prints between the Form # (Revision Date) and Age Number: "Policy issued by Church Mutual Insurance Company, 3000 Schuster Lane, Merrill, Wisconsin 54452. www.churchmutual.com" |
104296 |
||||||||||||||||||
An enhancement request was received to add Practice to the Yield Stack Confirmation of Coverage form. This ticket implemented the requested change. Practice was added to the Yield Stack Confirmation of Coverage form, and this field will populate with the corresponding data on the associated policy. |
102898 |
||||||||||||||||||
Policy Register: The following bugs have been fixed on the Policy Register (Reports > MPCI Reporting > Policy Register):
|
103360 |
||||||||||||||||||
Policy Notes: During the testing of TFS #103120 in the 7.110 release, it was found that the Policy Notes report (Reports > MPCI Reporting > Policy Notes) was failing to build the grid. The report has been updated and will no longer fail after selecting display results. |
103572 |
Livestock
DESCRIPTION | ID # |
---|---|
LGM Dairy Cattle: An issue was found with LGM (Plan 82) Dairy Cattle (0847) premium calculation logic. Recent changes were made with TFS #99674 when RMA implemented rounding changes mid-year for LGM. The premium error found was a result of the changes made for that ticket. With this ticket, premium calculation logic has been updated to correctly calculate all Expected Feed Costs for LGM Dairy Cattle for Insurance Periods starting with February 22, 2019 sales and forward. NOTE: Changes on this ticket are only applicable to LGM Dairy Cattle. |
103138 |
Global
DESCRIPTION | ID # |
---|---|
The Online Help Site was updated with topics as well as with current release notes. |
103894 |
Notifications: Billing Notification functionality for Revised Combo and Grower batches has been implemented. Each Agency has a new flag, Notifications Enabled, which must be set to "Yes" for that Agency's Agents or Growers to receive Notification Emails. When the Notification feature is enabled in the environment, this new flag is visible on the Agency record and can be set by editing the Agency in the System. Each Grower has a new flag, Notification Key Account. When the Notification feature is enabled in the environment, this new flag is visible on the Grower page and can be modified by editing the Grower record. |
103071 |
Mapping
DESCRIPTION | ID # | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The default colors for unplanted fields and non-cropland fields have been adjusted to lighter shades. Users reported that when selecting fields, they couldn't see a difference between the selected fields and the other unplanted fields.
|
102890 |
||||||||||||
Companion Policies: With this ticket, the System has been updated to set the correct flags and upload to the correct premium line when a companion linkage exists for lines being synced to the Acreage Report from the Mapping system. |
99290 |
||||||||||||
This ticket created support for Skip Row codes/factors from ProAg's Mapping Webservice. The following four fields are now received through the Webservice: PlantPattern, SkipRowCode, SkipRowWidth, and SkipRowFactor. |
99972 |
MPCI
DESCRIPTION | ID # | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Fast Edit: The following navigation enhancements have been made to aid users while processing Production and Acreage Reports via Fast Edit pages.
|
101645 |
||||||||||||||||||||||||
Margin Protection: For the 2019 RY, RMA made several rating changes for Plans 16 and 17. AIPs may reference the M13 premium calculation exhibits for additional detail. All code changes have been incorporated for the 2019 RY. |
100448 |
||||||||||||||||||||||||
Added/Primary County: An issue was reported with the Added County functionality where users were unable to designate both a coverage and its related high risk coverage (due to either HB or HR options) as the Primary County. The Added County procedures state that the same options and endorsements must exist on an Added County coverage that exist on the Primary County coverage. Given this, the System should allow both the high-risk coverage and its related base coverage to be designated as the Primary County. A fix has been implemented to allow this. In addition, the functionality to create an Added County coverage has been updated to allow Added County coverages to be created for both the high risk and base coverages. |
102601 |
||||||||||||||||||||||||
Enterprise Units: A bug was reported where, when EU or EP was elected on the coverage but either the System determined EU/EP did not apply or the user applied an override to remove EU/EP, if the Use BU checkbox was selected on the detail line, the System was continuing to apply OU rather than BU unit structure. Several releases ago, the unit structure code was refactored. During development to fix this bug where the System was not accounting for the Use BU checkbox, it was found that this logic is already in place following the refactor a few months ago. Given that this change was implemented with the refactor a few months ago, no code changes were implemented with this ticket. Therefore, this was a testing-only ticket to confirm the System applies the BU unit structure if it determines EU/EP does not apply or an override to apply BU/OU is selected and the Use BU checkbox is selected on the detail line. |
99357 |
||||||||||||||||||||||||
Enterprise Units: A bug was reported where the System was displaying a System Determined Unit Structure of "EU" in the Manage Unit Structure popup; however, the System was actually applying the OU unit structure to the detail lines. After reviewing the policy, it was found that the System Determined Unit Structure displayed in the Manage Unit Structure popup was correct and the System was applying the incorrect unit structure to the detail lines. The Enterprise Unit functionality has been updated so the System now correctly applies the System Determined Unit Structure in this scenario. |
104011 |
||||||||||||||||||||||||
Primary County: When designating a coverage as the Primary County for Added County purposes, if another coverage for the same crop is already designated as the Primary County, the System displays a popup notifying the user that another coverage is already designated as primary and asks the user if they want to change this designation. This popup is designed to open as soon as the user selects the Primary County designation on the coverage. Over the years, as different programs have been implemented, this logic used by this popup has been revised to also consider Plan Code, Type, Practice, and even Option Codes in certain scenarios. Because of this, it was found during internal testing that the popup was triggering multiple times in certain scenarios; one of which was when creating a new Margin Protection coverage. To prevent the Primary County popup from displaying multiple times when creating a new coverage, the Primary County dropdown has been moved further down on the page and now displays after the Crop Options on the Add New Policy, Add New Coverage, Maintain Coverage, and View Coverage pages. This will allow the System to have all the necessary information, including Plan Code, Type, Practice, and Crop Options, before determining if the popup should display to prevent the popup from displaying multiple times. |
100314 |
||||||||||||||||||||||||
Fast Edit CLU: A bug was identified over this past winter that was related to the Fast Edit CLU page, which was introduced for the 2018 RY spring processing cycle. During Save and Exit from the Fast Edit AR grid, the System performs a validation of the premium line unit structure for BU/OU. If a single detail line in a basic unit series is planted, the System applies the BU unit option and premium calculation. This functionality has always existed in the System and ensures the BU/OU unit reference is correct after acres are updated. It was found that this validation was not included in the scope of the Fast Edit CLU page when it was introduced. The report received was that the OU unit structure was maintained on a premium line where it qualified for the use of BU. A resave of the premium line by the user reset the unit structure and recalculated the premium values. The Fast Edit CLU page should now function the same as the Fast Edit AR page. All validations to the detail line unit structure were completed as expected. |
100960 |
||||||||||||||||||||||||
High Risk: When the High Risk Alternative Coverage Endorsement (HB Option) is elected, procedures require the same options/endorsements exist on the high risk HB option coverage as on the base non-high risk coverage. To account for this, a suspension was implemented several years ago that trigger when the same option/endorsements are not applied to both coverages. The only exceptions to this are the HB option, which will only be applied to the high risk coverage and the MC option. A bug was reported with this suspension when a Margin Protection coverage also exists on the same policy as the HB option and base coverages. In this scenario, the System seemed to be comparing the options on the Margin Protection coverage rather than the base coverage when determining if the same options exist on the HB option coverage. This was causing the suspension to trigger incorrectly. The suspension logic has been updated to consider Plan Code 01, 02 and 03 coverages only. |
102266 |
||||||||||||||||||||||||
Margin Protection: This is a testing-only ticket for Margin Protection premium for Companion and Stand-alone Margin Protection policies. RMA has added additional calculation changes, and premiums are now expected to match RMA Expected Values. |
95728 |
Private Products
DESCRIPTION | ID # |
---|---|
For WATTS products, if the policy was restored back to placeholder lines and, during the restore, the placeholder didn't match the MPCI coverage, a "restore failed" message displayed for the user, but this message did not indicate why the restore failed. A note will now be added to the Refresh Log as to why the restore failed. In this instance, the note would explain that the System could not match the sales data to the MPCI coverage because the Plan Code was different. |
103756 |
System Infrastructure
DESCRIPTION | ID # | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
A 2019 Special Provisions Update that was made available from RMA on 2/16/2019. The following Special Provisions for 2019 have been downloaded (2019_SPOI_0131.zip and 2019_SPOI_0228.zip):
FL (12) - multiple counties
FL (12) - multiple counties
FL (12) - multiple counties
FL (12) - multiple counties
FL (12) - multiple counties
FL (12) - 1 county
FL (12) - multiple counties
FL (12) - 1 county
LA (22) - multiple counties |
102862 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2019 ICE update was made available by the RMA and has been implemented in the System. The following table has been updated for 2019:
|
104001 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2019 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2019:
|
103730 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2015 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2015:
|
103828 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2016 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2016:
|
103829 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2017 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2017:
|
103830 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2018 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2018:
|
103831 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2019 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2019:
|
103832 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2020 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2020:
|
103833 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 9999 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 9999:
|
103834 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The ICE D00169 and D00170 tables were added to the base ADM ICE tables. |
103927 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2019 ICE update was made available by the RMA and has been implemented in the System. The following table has been updated for 2019:
|
104259 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2019 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2019:
|
104291 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2020 ICE update was made available by the RMA and has been implemented in the System. The following tables have been updated for 2020:
|
104292 |