Release Notes 8.090.0

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

System Updates

Forms & Reports

DESCRIPTION ID #

APH Database Form: An issue was found where System-generated child lines were printing on the APH Database form, and if AOI data had an ampersand, it was not printing on the form correctly.

AOI data was updated to print an ampersand instead of "&" when the name is entered into the System with an ampersand.
The APH Database forms was updated so that no System-generated child lines (MP, SE, SCO, STAX) or PP and LP child lines will print on the form.

109531

Nursery: RMA has created a new pilot program, Nursery Value Select (Commodity 1010). This new pilot requires a Monthly Unit Value Plan (MUVP) form for each basic unit and is included with each Nursery Value Report (NVR) the insured submits. The new MUVP form is available to print from the MPCI policy Print tab and the Batch Printing menus and displays with the title of "Monthly Unit Value Plan". The form is available in the blank, pre-headed with agency only, and pre-headed with insured and agency / agent report styles, and its format follows base form standards and the example in the handbook. This form will be available for all years, but the System will determine when the Nursery Value Select pilot policies can be entered into the System.

113479

Nursery: The Federal Crop Insurance Corporation (FCIC) released Nursery Value Select Pilot Crop Provisions. The changes are applicable for the 2020 Reinsurance Year / 2021 Crop Year.

113483

Nursery: A new form, Nursery Value Report (NVR), was implemented in the System for use with acreage reporting for the new pilot program, Nursery Value Select. With this ticket, the NVR form has been updated in the following ways:

A Practice field was added at the bottom of the Nursery Location(s) field (this is the same location that the Practice field is on the PIVR).
The following was added as a second sentence in #8 (in the "Also, I understand..." section): "At least 40 percent of my gross income derived from plant sales is from the wholesale marketing of plants."
The insured's email was excluded from printing with the pre-headed agency / agent only report style.
The revision date was updated to "03-2020".

114113

2020 Special Provisions were made available by the RMA and have been implemented in the System. The following Provisions have been updated for the 2020 RY / 2021 CY:

Nursery Value Select (NVS) (1010) - Plan DO (50) SCD 5/1: In these states: AL (01), FL (12), NJ (34), and TX (48) with each state having several counties.

114134

PAW: With this ticket, the Standard PAW questions have been added to the Florida (FL) Fruit Tree Producer's Pre-Acceptance Worksheet (PAW) form for all years. The questions will print after all of the PAW lines that are tied to the unit, and the answers will be blank. The revision date of the form was also updated to "03-2020".

114543

Livestock: The Last Target Marketing column was added to the Livestock Policy Register (Reports > MPCI Reporting > Livestock Register) Excel report after LGM Gross Margin Guarantee.

105587

Grove Identification Map: While reviewing the Grove Identification Map and the Continuation Page in preparation for the new Apple Trees pilot program, it was found it was missing a few base form standards to be consistent with other forms. This form was updated for all years to be consistent with other forms, and is now dated "03-2020".

113380

Perennials: For the 2020+ RYs, the RMA is now requiring that the acres for the years in a transitioning APH must be greater than zero to be associated with the "OF" Yield Type. RMA clarified that these transitioning acres should be entered with the "OF" Determined Yield Type applied. After confirmation was received from RMA that APHs transitioning from a conventional practice to an organic practice must have the Determined Yield Code of "OF" (TFS #79558 & #71710), a bug was reported. When attempting to apply the acres to the APH as directed by the RMA, an AIP identified what seemed to be a bug in the hard stop validation within the legacy APH. When the acres were greater than zero, the APH returned an error stating the "OF Yield Type cannot be preceded by an actual assigned yield". With this ticket, a change was made to adjust the "OF" Yield Type validations for the 2020+ RYs to no longer trigger the hard validation when acres greater than zero are keyed.

113685

Private Product SOI/COC: An enhancement was made to remove the official SOI and COC functionality from Private Products.

114298

Global

DESCRIPTION ID #

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

111921

Mapping

DESCRIPTION ID #

The display of the Point of Reference (POR) map was not working. This has been fixed.

114473

MPCI

DESCRIPTION ID #

Enterprise Units by Cropping Practice: Beginning in the 2020 RY, for Soybeans and Grain Sorghum in counties with an 11/30 or later Contract Change Date and both an FAC (following another crop) and NFAC (not following another crop) practices available, RMA will allow Enterprise Units by Cropping Practice (EC Unit Structure). Several changes are being made in the System to accommodate this new unit structure. Enterprise Units by Cropping Practice will work very similarly to Enterprise Units by Irrigation Practice.

Functionality to elect EC on the coverage was implemented in the 8.085 release with TFS #112455. This release includes additional changes for EC functionality:

NOTE: MCEU is not available with Enterprise Units by Cropping Practice (EC) for 2020.

Updated Validation

With TFS #111155, the Enterprise Unit validation logic that occurs at Mark Complete has been updated for Enterprise Units by Cropping Practice. This includes the following:

1. When EC is elected on both cropping practices on the coverage, once AR Sign Dates are keyed and the coverage marked complete, the System will first determine if both practices separately qualify for an Enterprise Unit.

If both practice qualify for an Enterprise Unit, the System will apply EC unit structure to the detail lines.

If one or both practices do not qualify for an Enterprise Unit, the System will then determine if both practices together qualify for a single Enterprise Unit (EU Unit Structure).
If both practices together qualify for a single Enterprise Unit, the System will apply the EU unit structure to all detail lines.
If both practice together still do not qualify for a single Enterprise Unit, the System will apply BU/OU to all detail lines.
2. When EC is elected on FAC practices only on the coverage, once AR Sign Dates are keyed and the coverage marked complete, the System will determine if FAC practice detail lines qualify for an Enterprise Unit.
If FAC practice detail lines qualify for an Enterprise Unit, the System will apply EC unit structure to all detail lines reflecting a FAC practice and BU/OU to all detail lines reflecting an NFAC practice.
If an FAC practice detail lines do not qualify for an Enterprise Unit, the System will apply BU/OU to all detail lines.
3. When EC is elected on NFAC practices only on the coverage, once AR Sign Dates are keyed and the coverage marked complete, the System will determine if NFAC practice detail lines qualify for an Enterprise Unit.
If NFAC practice detail lines qualify for an Enterprise Unit, the System will apply EC unit structure to all detail lines reflecting an NFAC practice and BU/OU to all detail lines reflecting an FAC practice.
If NFAC practice detail lines do not qualify for an Enterprise Unit, the System will apply BU/OU to all detail lines.
4. System logic that determines and stores the System Determined Unit Structure has been updated to store EC if the System determines the coverage and/or cropping practice qualifies for EC. The unit structure determined by the System will display in the Manage Unit Structure popup.

NOTE: See the Crop Insurance Handbook for more information on Enterprise Unit qualification rules.

Updated Manage Unit Structure Popup

With TFS #112460, the Manage Unit Structure popup has been updated to account for EC. This includes the following:

1. Separate rows for FAC and NFAC practices are displayed in the Manage Unit Structure Modal when EC is elected on the coverage.

NOTE: This mirrors functionality for Enterprise Units by Irrigation Practice that displays separate rows for IRR and NI

2. The System Determined Unit Structure was updated to include EC if the System determines EC applies to one or both practices, based on what is elected on the coverage:
When EC is elected on both practices, if the System determines EC applies, EC will display for both practices.
When EC is elected on FAC practices only, if the System determines EC applies to FAC detail lines, EC will display for the FAC line only and BU/OU will display for the NFAC line.
When EC is elected on NFAC practices only, if the System determines EC applies to NFAC detail lines, EC will display for the NFAC line only and BU/OU will display for the FAC line.
3. An override for "EC" was added for when EC is elected on the coverage and the System determines EC does not apply:
Users will have the ability to apply the EC override to both practices when EC is elected on both practices.
The EC override will only display for the FAC practice line when EC is elected on FAC practices only.
The EC override will only display for the NFAC practice line when EC is elected on NFAC practices only.

Rating Logic

With TFS #112462, the rating logic was updated to account for the new EC unit structure. When applied, EC rating will follow the M13 premium calculation exhibits.

Suspensions

With TFS #112459, new suspensions were added to trigger when some form of Enterprise Units by Cropping Practice is elected on the coverage but the System determines during Mark Complete that the coverage/cropping practice does not qualify for the EC election on the coverage. The new suspension messages are listed below:

EC elected on both cropping practices:
"System validation indicates coverage does not qualify for EC, but does for EU. EC unit structure has been removed from the detail lines and EU has been applied. Underwriter review required."
"System validation indicates coverage does not qualify for EC or EU unit structure. EC unit structure has been removed from the detail lines. Underwriter review required."
EC elected on FAC cropping practices only:
"System validation indicates the FAC practice detail lines for the coverage do not qualify for EC. EC unit structure has been removed from the detail lines. Underwriter review required."
EC elected on NFAC cropping practices only:
"System validation indicates the NFAC practice detail lines for the coverage do not qualify for EC. EC unit structure has been removed from the detail lines. Underwriter review required."

111155, 112460, 112459, 112462

Hybrid Vegetable Seed: TFS #112814 removed the "Seed Company code required" validation from the Hybrid Vegetable Seed detail line. The M13 confirmed that the P11 (field 61) for Hybrid Vegetable Seed (0066) must be empty, so a Seed Company code is not required. The presence of the Seed Company dropdown on the detail line has been causing confusion for users. With this ticket, the Seed Company dropdown was removed from the Maintain Detail Line page if the crop is "Hybrid Vegetable Seed". This field must be retained on all other Plan 55 crops.

114122

Perennials: During internal review of Caneberry functionality, a bug was identified with the APH Calculation for Caneberries. Caneberries are a lag year crop, so an 11th year displays in the APH for tracking purposes only and is not intended to be included in calculation of the APH. However, it was found that the System was incorrectly using the lag year when calculating the APH. This issue has been resolved.

NOTE: During testing of this functionality, an issue was identified with the record type validation logic where the System is displaying the hard error stating a record type is required when a record type is missing from an APH other than the one being saved. TFS #114362 has been set up to address this issue in a future release.

114212

Hemp: When Hemp procedures were originally implemented, the P14 record required a Type. However, RMA changed their procedures with CR 213216 so that the P14 records for Hemp will no longer require a Type Code or a Class Code.

With this ticket, the validation logic requiring a Type upon save was removed. The coverage functions similarly to other mandatory type crops where a type is entered only if electing a different coverage level. This change impacts the Add New Policy, Coverage (Add/Edit/Maintain), and Quote (Add/Edit/Maintain) pages. A new message will display on those pages to notify users that "Selection of Type only applies when different coverage levels are elected."

As part of this ticket, a post-production script was run to remove the Type from any Hemp coverages added prior to the 3/26/2020 release date unless there are multiple coverages by Type with different coverage levels elected.

114357

Perennials: Beginning in the 2020 RY/ 2021 CY, RMA has released a new pilot program for Apple Trees. Apple Trees (0184) will now be insured under the Tree Based Dollar Amount of Insurance Plan (Plan 40) and the pilot is modeled after the other tree based dollar crop programs like Florida Fruit Trees and Pecan Trees. With this ticket, detail line and rating updates were made to the System to support the Apple Trees pilot program.

112897

MCEU: An issue was reported where a suspension stating a primary/secondary county designation is required was not triggering when it should have been. A fix was done to have the suspension trigger upon Mark Complete when the primary/secondary county designation within the Manage Unit Structure popup has not been made on a policy for MCEU. The suspension message states "A Primary/Secondary County designation and an MCEU Related Coverage selection is required when MCEU is elected.

107882

WFRP: An AIP reported that the Revised Insured/Agent Signature Dates on a Revised Report for WFRP Commodities were being improperly removed after save of Fast Edit PR and subsequent Mark Complete. This was confirmed and a fix was put into place with this ticket. Now, when Saving Fast Edit PR on a WFRP policy, the Revised Insured Signature Date and Revised Agent Signature Date are retained correctly on the user interface as well as in the database.

114172

Raisins & WFRP: Premium is not supposed to push to the Policy Balance table until the following information exists for a coverage: 1) Premium greater than zero; 2) An AR Sign Date (or equivalent signature date depending on the coverage/commodity); and 3) A successful Mark Complete. This means that no suspension has occurred, and the coverage is set to an "Approved" status during the Mark Complete process.

Once premium is pushed for the first time (based on the above criteria), any change in premium from that point forward will occur in real time. However, it was determined that the System has never required a AR signature date for WFRP or Raisins when determining when to push premium to the Policy Balance table for the first time.

With this ticket, the logic that updates the Policy Balance table was updated to require the AR Sign Date for Raisins and a Farm Report Sign Date for WFRP. Now, as expected, the AR Sign Date is needed in addition to the other requirements of a premium amount greater than zero and a successful Mark Complete.

NOTE: A spin-off ticket #114360 has been created to fix an issue found during testing. For WFRP, if premium is attached, when Farm Report Sign Dates exist and the coverage is Marked Complete but a suspension is thrown, clearing the suspension should push the premium to the Policy Balance table for the first time as long as the Coverage Status goes to an "Approved" status. This is not happening and will be fixed with TFS #114360. There is also a known issue where premium is pushing to the Policy Balance table too soon on carryover coverages. This issue is being resolved under TFS #114052.

114184

Private Products

DESCRIPTION ID #

An internal issue was reported where the yellow banner was not displaying when the user submitted acres or did a Mark Complete on a Private Product policy. This issue has been resolved.

113387

ICE: It was reported that the Increased Coverage Election forms for the Schedule of Insurance and the Confirmation of Coverage were printing blank for the user. A correction was made so that, when the user prints the Schedule of Insurance and the Confirmation of Coverage for the Increased Coverage Election policy, the information is now printing on the form.

114112

System Infrastructure

DESCRIPTION ID #

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

CCWS
PASS
ROE

114629

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

CCWS
PASS
ROE

114630

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

ITS

114633

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

CCWS
PASS
ROE

114634

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

CCWS
PASS
ROE
IcePriceElectionPercent
IceInsurancePlanCommodityCoverageType
IceNonPremiumAcreageInsurancePlanCommodity
IceGuaranteeAdjustment
IceGuaranteeAdjustmentTypeInsurancePlan
IceYieldTypeCommodity
IceContractPriceLimit
IceSpecialtyTypeCommodityPlan
IceStageCommodity
IcePriceRounding
IceInsuranceOptionCriteria
IceProgramIndicatorCommodity
IceCoverageLevel
IceLrrFundCutoff

114649

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

CCWS
PASS
ROE

114656