Release Notes 7.110.0

These release notes provide brief descriptions of changes included in AgWorks 7.110.0.

Videos

System Updates

Claims & Inspections

DESCRIPTION ID #

With 2019, the ability to have SRC as an endorsement in IL, IN, and OH has been introduced. With this ticket, it was verified that the auto-generation feature works for the SRC product today. When a claim NOL is opened on the MPCI side when there is a Hail policy attached that has one or more endorsements of SRC, the attached Private Product policy should have an NOL opened up on it as well. This is to create a claim header, and the user will be the one to complete the claim through the normal claim processing process. No details will be brought into the claim in the auto-generated process.

When opened, the Grower Intent will be set to Replant. There is a new cause of loss as well that will be available, EXCESS MOISTURE/PRECIP/RAIN, that will be assigned to the claim. This new cause of loss is applicable to the SRC endorsement and will be provided with an NCIS code of 34 to be used to send in transmissions (unless manually updated and changed on the claim lines by a user). This will be the default on the lines that are opened to enter the claim details as well.

When keying the claim, recall that this is a Hail policy so the page will be the Hail page that is used for claim detail entry. Since SRC is paid at 100% loss, the user will need to key the 100 into the agreed percent of loss field. If the user keys any other percentage, the other percentage will be used in the calculation.

103293

Estimator

DESCRIPTION ID #

Policy Estimates: With this ticket, the Policy Estimate's Detail Lines, Scenarios, and Calculations UIs have been updated to allow standalone Margin Protection scenarios to be quoted. In addition, any Margin Protection selections that are on the policy will be automatically selected on the corresponding Policy Estimate.

97900

Policy Estimates: With this ticket, a bug on the Policy Estimate printout was corrected to ensure that a field for Expected Margin will appear in the Unit Information section any time that a Margin Protection scenario is included (was previously being suppressed if an ARPI plan was also selected).

101185

Policy Estimates: With this ticket, the Policy Estimate's printout was updated to allow standalone Margin Protection scenarios to be quoted.

101189

Forms & Reports

DESCRIPTION ID #

LRP SOI: With this ticket, the Livestock Risk Protection (LRP) Schedule of Insurance (SOI) listing on the print menu has been updated in the following ways for all years:

• The "Level of Detail" label and the dropdown that only had "Pre-filled Form" were removed from the print menu for the form. This form is only available to print pre-filled, so a dropdown was unnecessary.
• "(LRP)" was added to the form title for the LRP SOI to be consistent with the other LRP form titles on the print menu.

102521

VFR Application: Section 12306(b) of the Agriculture Improvement Act of 2018 added the definition of Veteran Farmers and Ranchers to Section 502(b) of the Federal Crop Insurance Act (7 U.S.C. 1502(b)) (as amended by section 11101) and amended Section 508 of the Federal Crop Insurance Act (7 U.S.C. 1508) to add "or Veteran Farmer or Rancher" after "Beginning Farmer or Rancher," giving Veteran Farmers or Ranchers (VFRs) the same benefits as Beginning Farmers or Ranchers (BFRs).

With this ticket, a standalone Veteran Farmer or Rancher (VFR) Application has been implemented and is now available for the 2019+ Crop Years. This form has been set up for Batch Scanning, is a permanent form with the Attachment Type of VFR Application, and will have a QR Code when printed with a pre-headed report style. Users can print this form from the MPCI policy Print tab and the Batch Printing tool. Available report styles are blank and pre-headed.

101657

Global

DESCRIPTION ID #

Notifications: Billing notification functionality for MPCI, Private Products, Livestock, and Agency Bill 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 received 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.

99204

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

102752

Livestock

DESCRIPTION ID #

LRP: An issue was found on an LRP policy where the grower was set to Out of Compliance. The Producer Premium and Subsidy values that were displaying on the LRP detail line were not matching the SOI or the premium within the Policy Balance tab of the policy. Refactoring was done for LRP (Plan 81) premium calculations. Previously, some of the calculations were done on the fly as screens were loading, and as a result, those specific values were not being stored in the DB tables. Values displayed on the UI are now stored within the appropriate DB fields so they can be pulled directly from the applicable field(s) for forms and transmissions. These changes were only made for Plan 81 (LRP). This does not affect Plan 83 (DRP) where transmissions are sent through the PASS system.

101902

Mapping

DESCRIPTION ID #

The RMA released a new CLU Layer - April 2019. This has been implemented in the System.

103354

In select counties in Ohio, the CLU Processing and Township layers have been updated to reflect "flipped" or non-traditional township values (i.e., the Township/Range is flipped). When adding these legals to Land IDs on a premium line, the System will now correctly validate those as valid legal descriptions and will automatically look up the flipped legal based on the keyed farm/tract in one of those locations.

96979

MPCI

DESCRIPTION ID #

Companion Policy: It was found that additional logic was needed to account for scenarios when both System-generated and manually-generated child lines exist. Previously, the logic was only working when one or the other existed but not both. Scenario example showing the issue (links were established between the Source and the Companion policies and then acres were added to the Source policy):

• Source Policy—Corn unit 1-0101: 50.0 planted on the parent line, a System-generated SCO child line, and a manually-created PP child line with 30.0 acres
• Companion Policy—Corn unit 1-0101

After acres were added on the Source policy, only the 30.0 acre PP line came across. The System did create a child line, but it had zero acres. The Companion policy didn't have the SCO line but still expected the main line to be 50.0 planted and the child line that was created to have the 30.0 acres of PP.

With this ticket, Companion Policy functionality has been updated to correctly sync the acres when both System-generated and manually-generated child lines exist.

102090

Companion Policy: Some bugs were found during internal testing of the Companion Policy functionality when established companion links needed to be broken. With this ticket, the following issues have been corrected:

• Scenario 1: If the plan changes on the Source or Companion coverage to an unsupported plan, the System should automatically break the companion links on the applicable coverages.
• Issue: Previously, when a user changed the plan on the Source policy to an unsupported plan, they received the warning message about the link being broken as expected; however, the link was only removed from the Source policy and not the Companion policy.
• Fix: The logic was updated to now remove the links for the applicable coverages from both policies.
• Scenario 2: If a policy shareholder with established companion links is deleted from the Source policy, the System should automatically break all companion links between the applicable Source and Companion policies.
• Issue: Users were able to delete policy shareholders from the Companion policy but links were not breaking as expected on both policies.
• Fix: Due to the current logic in place, the System is unable to break the links at this time from a Companion policy to a Source policy in this scenario. In order to prevent shareholders with existing companion links from being deleted on the Companion policy, the System will now throw a hard stop error message telling the user that they must first break any associated companion links before they will be able to delete the shareholder with established companion links. Once the links are broken for that shareholder, the user will then be able to delete the shareholder from the Companion policy.
• Scenario 3: If an associated shareholder (with established companion links) is removed/unassociated from a detail line on the Source policy where the companion link exists, the System should automatically break the companion link for that detail line on both the Source and Companion policies.
• Issue: The user was able to remove/unassociate linked shareholders on the Companion policy, but the links were not being removed from the detail lines on both policies as expected.
• Fix: Due to the current logic in place, the System is unable to break the links at this time from a Companion policy to a Source policy in this scenario. In order to prevent shareholders with existing companion links from being unassociated on the Companion policy's detail line, the System will now throw a hard stop error message telling the user that they must first break any associated companion links. Once the links are broken for that shareholder, the user will then be able to remove/unassociate the shareholder from the Companion policy’s detail line.

102215

Companion Policy: Some bugs were found during internal testing of the Companion Policy functionality. With this ticket, the following issues have been corrected:

• The Crop Practice and UI checkboxes are now read-only on both the Maintain Detail Line page and the Fast Edit AR page on the Companion policy once companion links are established. Previously, they were not always read-only on both pages on the Companion policy.
• The companion link icon popup wording was not consistent across various pages in the System. For consistency, they all now read "Companion Link Exists" if you are within the Source policy or "Source Policy Exists" if you are within the Companion policy. Previously, the popup on some of these pages was displaying "1 or more Companion links Exist".

102209

Companion Policy: Users have the ability to create a new unit on the Companion policy when establishing companion links from the Source policy; however, an issue with the Create New Unit feature was found during internal testing when coverages were insured by type. If multiple coverages were established by type on both the Source and Companion policies, the System was not creating the new unit on the Companion policy under the appropriate type. The Create New Unit functionality has been updated to correctly build the new linked unit for the coverage using the applicable coverage by type.

102198

Perennials: In CA, AIPs are permitted by the Davis RO to establish a higher yield for Almonds that have not met minimum insurability requirements. When the "higher yield" calculations are applied to an APH, the YC option code is not applicable, by procedure. An APH bug was applying the YC option code to the P15 record when the higher yield APH exception was used for calculation AND when the detail lines reflected the same BU/OU but had different sub units. The System wasn't properly handling calculation of these lines as 2 separate units with the sub unit extension and was caught in a logic loop when the user tried to re-save the APH to remove the incorrect YC value. This has been corrected to now remove the YC option code when the "higher yield" Almond exception calculation is applied.

102229

Margin Protection: Standalone Margin Protection and standalone STAX coverages require the grower to report production annually for planted acres. Agents enter the production in the Fast Edit PR grid within the year the acres were insured rather than the following RY. A bug was reported through the help desk that resulted in a coverage and the associated detail lines with acres not displaying within the Fast Edit PR grid as expected. Following review by a developer, it was determined the NLF (No Longer Farming) flag was applied to one of the 0-acre lines for the coverage. The NLF flag prevented all detail lines of the coverage from loading to the grid which was not correct. An adjustment to the code was made to allow the grid and detail lines to be loaded for all lines of a coverage (lines with acres > 0) even if 0-acre lines reflect the NLF status.

102528

SCO: This is a testing-only ticket to verify premium calculations for SCO when added to Plan 55 crops. RMA extended SCO to the Hybrid Seed crops for the 2019 Spring SCD, and the detail line and premium calculations could not be fully tested at that time. This testing-only ticket confirmed the System was accurate.

101483

Suspensions: A suspension has been in place for several years to trigger if there is an excessive yield entered in the APH. Research confirmed that the suspension was initially designed to trigger when an AR sign date existed on the coverage. The logic has been updated to trigger when either a Production Report Sign date or an Acreage Report Sign date exists.

102487

MCEU: With the 7.110 release, for the 2019 and succeeding Reinsurance Years, users now have the ability to create Multi-County Enterprise Units within the System. The Multi-County Enterprise Unit, or MCEU, Endorsement allows a grower who farms across county lines to combine their acreage of a single crop in one county with their acreage of the same single crop in a contiguous county in the same state to create one larger enterprise unit. This endorsement also allows for combining separate enterprise units by practice across contiguous county lines. To support this functionality, the following changes have been made in the System.

• A new MC option is available on the Add New/Maintain Coverage pages to allow users to easily elect and identify Multi-County Enterprise Units.
• A new popup, Manage Unit Structure, has been added to the System. This new popup is available from the Additional Functions dropdown on the Detail Lines tab when the EU or EP unit structure has been elected on a line.
• An MC unit structure code displays on the Detail Lines tab for Multi-County Enterprise Unit detail lines. This code is not a valid Unit Structure code with the RMA, but rather, one created within the System to help users quickly identify MCEU detail lines.

For more information on MCEU functionality, see the online help site for a how-to video and other documentation.

102800

With TFS #101175, a new field was implemented on the BFR Certification page (Tools > BFR Certification) for WFRP Remaining Years of Eligibility. This field was added following new procedures issues from RMA around BFR benefits and WFRP policies. Per RMA, beginning in 2019, growers qualifying for BFR benefits are eligible for benefits for up to 10 years on WFRP rather than the standard 5 years of benefits available on other policy types. This field was designed to allow the user to select a value from 0-10 (rather than 0-5 like the other Remaining Year of Eligibility field).

During internal QA testing of TFS #101175, it was found that rather than displaying 0-5 in the Remaining Years of Eligibility field and 0-10 in the WFRP Remaining Years of Eligibility field, the System was displaying options for 0-5 as well as options for 0-10 in both dropdowns, causing 0-5 to display twice. With this ticket, these dropdowns were updated so that the standard Remaining Years of Eligibility field displays 0-5 values only and the WFRP Remaining Years of Eligibility field displays 0-10 values only.

102788

Private Products

DESCRIPTION ID #

The POTATO ALTERNATE PAYMENT ENDORSEMENT has been added to the System and will generate as a PDF for the user to print when the policy form code (Basic AP) is elected.

102897

A request was received to update the Effective Date on the Confirmation of Coverage form for Private Products when the policy has been canceled. The logic to display the date was updated on the Private Product Confirmation of Coverage form when the policy is canceled.

101184

Yield Stack: The AIP requested updates to their Yield Stack sales record and policy pages to assist with improved processing for 2019. The Practice for the Sales Record was added as a field for selection and the Rate field was removed from the Sales Record. On the policy page, the user will now see Weighted Average Rate Yield and Liability as additional columns. Updates will be made to the titles, calculations, and references calculations used in the Weighted Average Share, Rate, and Practice fields. For optimization, multiple county/crop combinations are allowed to be submitted at once at the time the user submits the coverage to create the Yield Stack quote. Also, only one rolled up detail line will display per each county/crop combination for the Enterprise Unit.

101556

A request was received to have the ability to submit more than one coverage at a time when setting up an Increased Coverage Election Policy. An enhancement was made to the Increased Coverage Election (ICE) policy to give the user the ability to submit more than one coverage at a time when setting up the ICE quote.

102058

System Infrastructure

DESCRIPTION ID #

A 2015 ICE update was made available by the RMA and has been implemented in the System. The following tables were updated for 2015:

• CCWS
• PASS
• ROE

103197

A 2016 ICE update was made available by the RMA and has been implemented in the System. The following tables were updated for 2016:

• CCWS
• PASS
• ROE

103198

A 2017 ICE update was made available by the RMA and has been implemented in the System. The following tables were updated for 2017:

• CCWS
• PASS
• ROE

103199

A 2018 ICE update was made available by the RMA and has been implemented in the System. The following tables were updated for 2018:

• CCWS
• PASS
• ROE

103200

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

• CCWS
• PASS
• ROE
• IcePriceElectionPercent
• IceGuaranteeAdjustmentTypeInsurancePlan
• IceProgramIndicatorCommodity

103201

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

• IcePriceElectionPercent
• IceGuaranteeAdjustmentTypeInsurancePlan
• IceProgramIndicatorCommodity

103416

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

• CCWS
• PASS
• ROE
• IcePriceElectionPercent
• IceInsurancePlanCommodityCoverageType
• IceNonPremiumAcreageInsurancePlanCommodity
• IceGuaranteeAdjustment
• IceGuaranteeAdjustmentTypeInsurancePlan
• IceContractPriceLimit
• IcePriceRounding
• IceInsuranceOptionCriteria
• IceProgramIndicatorCommodity
• IceCoverageLevel
• IceLrrFundCutoff

103202

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

• IceAip
• IcePic

103418

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

• ITS

103203

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

• AreaCoverageLevel
• AreaRate
• Commodity
• ContiguousCounty
• CoverageLevelDifferential
• CroppingPractice
• Date
• DocumentBuilder
• InsuranceOffer
• InsuranceOption
• InsurancePlan
• Interval
• Map
• OptionRate
• Practice
• Price
• Statement
• SubsidyPercent
• Type

103080

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

• Price
• UnitDiscount

103004