Release Notes 8.000.0

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

System Updates

Forms & Reports

DESCRIPTION ID #

SOI: The format of the Schedule of Insurance (SOI) was updated to implement that same format for the eZ-Hail and Production Hail Detail Lines and Premium Summary Section(s) that print when those products are linked to an MPCI policy. As such, the vertical borders and bolding were removed, and the Product, Policy Form, Est. Acres, and Net Premium font was made larger to help those important items stand out on the SOI. Additionally, the borders and shading were removed from around the Premium Summary section title. These changes apply to all Reinsurance Years.

103818

RMA released updated Annual Forage crop provisions for the 2020 and succeeding Crop Years (CYs). These have been updated in the System. Provisions print with the MPCI Policy Declaration Page when the print option to print provisions with the form is selected. The MPCI Policy Declaration Page is available to print from the MPCI policy Print tab and from the Batch Printing menu.

103435

SOI: The Schedule of Insurance (SOI) has been updated with this ticket to make it easier on the eyes for scanning/reading and to have four important data items stand out for the Grower: Crop, Unit, Acres or Tree Count, and Insured's Premium. There are currently 11 different formats of the SOI (see below). Formats 1, 2, 3, and 11 were not updated. Formats 4, 7, 8, 9, and 10 will be using this new SOI format.

1. API / PRF
2. Annual Forage
3. WFRP
4. Nursery
5. Clams (crop is currently discontinued)
6. AGR (crop is currently discontinued)
7. Fruit & Trees
8. All other MPCI crops
9. Hudson Private Products continuous
10. SOI as an AR
11. SOI / Production Report

The following updates were made to the SOI for all years:

• Crop Summary Section
• The shading and borders were removed from around the Crop Summary title.
• The right and left borders on the Coverage lines were removed.
• Multi-County Enterprise Unit Endorsement Section
• The shading and borders were removed from around the Section title.
• The right and left borders on the Coverage lines were removed.
• County was added to the Related Coverage info.
• A Total MCEU Guarantee field was added to the MCEU table. The data for this field will be populated in a future release.
• Nursery Location Section
• The shading and borders were removed from around the Section title.
• Page 2+ Header
• Logo and AIP Contact info will no longer print.
• On the left of the form title, the Insured's Name and Agency's Name will display.
• On the right of the form title, the Crop Year and Policy # will display.
• Detail Lines Section
• Detail Line pages will now start on a new page.
• County was moved to print in the Detail Line title. The Detail Line title and column / field labels will now print above the first detail line and will then only print when there is a county change or if there is a change in a field label (e.g., with Fruit, Trees, Nursery, and Grapes).
• These data items will now display as bolded and in a larger font size: Crop, Unit, Acres, and Insured's Premium.
• Type and Practice were moved to print behind the Crop in parentheses; this data is not bolded and displays in a normal font size.
• Plan, Type, and Practice labels were removed. Plan data will only print if it is STAX with a related coverage on the policy.
• Acres and Plant Date were moved to no longer be stacked.
• The Yield Limit label and data were removed.
• Land labels will no longer be bolded.
• The Options field and data were moved to print above the Farm Name; title is also no longer bolded.
• The child line indicators were moved to print under the Crop and will display in bold and in the same font size as the Crop is so the child lines stand out.
• The No Land section will print with child lines.
• The Skip Row fields were removed; this data will now print under Acres when the data is available.
• The Crush District label and field were removed from printing with the Type; the label and data will now print under Unit when the data is available.
• Remarks Section
• The space before and after the Remarks section was increased.
• Premium Summary Section
• The shading and borders were removed from around the Crop Summary title.
• SCO acres no longer print since they are accounted for in the parent line.
• Plan, Type, and Practice were removed from the County / Crop label. Plan data will only print if it is STAX with a related coverage on the policy. The type will only print for Mandatory Type crops. Both will print in parentheses after the Crop.
• SBI Section
• The shading and borders were removed from around the Section title.
• The right and left borders on SBI lines were removed.
• Legend Section
• The legend no longer prints on each page.
• The legend will print at the end of the SOI out of the Footer area.
• UI Reason Codes were incorporated into the legend.
• The Acreage Type Legend was removed.
• The Revision Date was updated to 06-2019.
• The Nursery Land Location page that generates when a Nursery policy has more than 4 Land Locations was updated. This extra page prints at the end of the SOI. The right and left borders on the Land Location Detail Lines were removed.
• The colon (:) was removed from the Landlord Tenant Statement label on the Statement Pages when the SOI is printed as an AR.

101550

VFR Application: The Veteran Farmer Rancher Application (VFR App) was added as a new form with TFS #101657 in the 7.110 release. With this ticket, a new MPCI Policy Attachment Type, "VFR Application", has been added. This Attachment Type should be used when the VFR App is attached via an individual MPCI policy as well as when the form is Batch Scanned.

103522

SOI: MCT was notified that STAX related coverage acres were being included in acre totals in the Crop Summary and Premium Summary on the Schedule of Insurance (SOI). The following changes have been made to this form for all Crop Years:

• WHEN the coverage has a STAX plan, AND the policy has another coverage with the same State / County / Crop, THEN do not print the acres for the STAX plan in the Coverage's Crop Summary's Total Acres Planted.
• WHEN the coverage has a STAX plan, AND the policy has another coverage with the same State / County / Crop, THEN do not print the acres for the STAX plan in the Coverage's Premium Summary's Acres and do not include the acres in the Total Acres for the policy.

No version date was updated with this ticket, as this was only a data update.

90742

Global

DESCRIPTION ID #

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

103896

Livestock

DESCRIPTION ID #

An issue was found internally while testing the 2020 RY changes for LRP (Plan 81). One of the changes introduced for the 2020 RY is to now include all 50 states for the LRP coverage. During testing it was found that the Entity State dropdown was not populating with all 50 states, but the Policy State dropdown was. Due to the layout of the fields on the Add New Livestock Policy page, the user was not selecting the RY until after they had selected the Entity State. As the RY had not been selected, the System did not know how to populate that dropdown. Since the Policy State field was after the RY selection, the System was populating that dropdown correctly with all 50 states.

With this ticket, the field layout on the Add New Livestock Policy and Add New Livestock Quote pages has been updated so that the user must first select the RY. This will ensure the state dropdowns are populating as they should be. This change will only affect the Add New Livestock Policy and Add New Livestock Quote pages but not the Add Livestock Coverage page as the RY is already set on that page based off of the RY of the policy. The state list dropdown logic was also updated to now only call the db once to populate both the Entity State and the Policy State fields to increase System performance when loading the page.

104208

DRP: Regulatory changes were announced on 4/22/2019 for the 2020 Reinsurance Year for Plan 83 – Dairy Revenue Protection (DRP) with PM-19-022. The following items have changed for DRP for the 2020+ RYs:

• Coverage levels have been adjusted to remove the 70 and 75 percent levels.
• The minimum declared butterfat was modified from 3.50 to 3.25, making the new range 3.25-5.00 pounds.
• The minimum declared protein was modified from 3.00 to 2.75, making the new range 2.75-4.00 pounds.
• The declared butterfat test to declared protein test ratio was removed.

NOTE: Changes called out in this ticket are specific to Plan 83 – Dairy Revenue Protection (DRP) only.

102857

LGM: Regulatory changes were announced on 4/22/2019 for the 2020 Reinsurance Year for Plan 82 – Livestock Gross Margin (LGM) with PM-19-023.

For 2019 and prior RYs, regulations were in place on the amounts of insurance insureds could have on the various LGM commodities. For the 2020+ RYs, the following limitations have been removed:

• LGM Cattle – Annual Head Limit of 5,000 per endorsement and 10,000 annually
• LGM Dairy – Annual limit of 240,000 hundredweight of milk
• LGM Swine – Annual Head Limit of 15,000 per endorsement and 30,000 annually

With this ticket, limitations have also been added to the monthly Target Marketing fields as follows to prevent "Sorry..." errors from being thrown now that limitations by RMA have been removed:

• LGM Cattle – 50,000 per month
• LGM Dairy – 1,000,000 per month
• LGM Swine – 50,000 per month

NOTE: Changes called out in this ticket are specific to Plan 82 – Livestock Gross Margin (LGM) only.

102856

LRP: Regulatory changes were announced on 4/22/2019 for the 2020 Reinsurance Year for Plan 81 – Livestock Risk Protection (LRP) with PM-19-024. The following changes have been made to system logic for the 2020+ RYs for Plan 81 – Livestock Risk Protection (LRP):

• LRP for Feeder Cattle, Fed Cattle, and Swine will be expanded to all remaining states. No changes were needed, but regression testing was performed to verify that all states are loading when creating a new LRP policy or adding a new LRP coverage for those commodities.
• The subsidy was increased from the previous 13% for all coverage levels to a range of 20%-35% based on the coverage level selected. No changes were needed, but regression testing was performed to ensure premium calculations are matching RMA's Cost Estimator.
• Limitation modifications have been made for both Number of Head per Endorsement and Number of Head Annually insured.
• Fed Cattle:
• Number of Head per endorsement has increased from 2,000 to 3,000
• Number of Head annually has increased from 4,000 to 6,000
• Feeder Cattle:
• Number of Head per endorsement has increased from 1,000 to 3,000
• Number of Head annually has increased from 2,000 to 6,000
• Swine:
• Number of Head per endorsement has increased from 10,000 to 20,000
• Number of Head annually has increased from 32,000 to 75,000

NOTE: Changes called out in this ticket are specific to Plan 81 – Livestock Risk Protection (LRP) only.

102855

MPCI

DESCRIPTION ID #

Annual Forage: Beginning in the 2020 Reinsurance Year (RY), RMA has made a number of changes to the Annual Forage (0332) policy. These changes include:

• A new Dual Use (DU) option that allows growers to insure their small grain crop under the Annual Forage policy for grazing as well as under an MPCI Small Grains Policy for Grain.
• DU will be available in select counties in Colorado, Kansas, Nebraska, New Mexico, Oklahoma, and Texas.
• The Productivity Factors available in Colorado and New Mexico were updated from 100% to 150%.

NOTE: No System changes were needed for this change. Once RMA updates the IcePriceElectionPercent table with these new values, they will be available in the System.

• The policy was updated to state grazing is a valid intended use under CAT coverage.

With this ticket, the coverage pages for Annual Forage have been updated to allow selection of the DU option on Growing Season 1 coverages only, if it is available for the RY/State/County/Crop. In addition, the Annual Forage detail lines pages have been updated to allow selection of the DU option if it is elected on the coverage. Finally, the detail line page has been updated to allow an intended use of Grazing when the coverage level is CAT.

NOTE: When the DU option is elected and applied to a detail line, a reduced County Base Value (CBV) applies to the premium calculation. TFS #103939 will address the necessary rating changes in a future release.

102178

Enterprise Units: In December 2018, RMA issued a Q&A that included a question around prevented planting (PP) acres and how the acres are counted in relation to the 20/20% rule for Enterprise Units. The 20/20% rule requires the lesser of 20 acres or 20% of total acres exist in two or more unique land IDs or multiple land IDs that can be aggregated together to meet this 20/20% rule. Previously, Enterprise Unit procedures required only planted acres could be used to determine if the 20/20% rule was met and to determine the EU discount factor. Through the December 2018 Q&A, RMA clarified that total planted acres for purposes of the 20/20% rule should be determined using all acres, planted and PP. Previously, the System was using planted acres only to determine total acres for purposes for the 20/20% rule.

With this ticket, the Enterprise Unit validation logic was updated to include both planted and prevented planting acres when determining total acres for the coverage for the purposes of the 20/20% rule. The System will continue to use planted acres only when determining the number of acres in each unique land ID for the purposes of the 20/20% rule as well as when determining the Unit Discount Factor. This change has been implemented for the 2019+ RYs.

NOTE: A query was provided to each AIP with a list of policies where EU/EP is elected on the coverage and one or more detail lines reflect a prevented planting status. These policies will need to be marked complete following the 8.000 release.

104237

RMA announced a change to the premium calculation for Plans 01, 02, 03, and 90 for the 2018+ RYs in mid April. CR 16778 modified the premium calculation for both RYs when the prior year and current year yields had a CUP applied. RMA deployed this change to production in their May production release.

This change has been discussed in detail on the All AIP calls as well as in the PASS Status Report from RMA. For the 2018 RY, recalculation of premium will be required (and possibly corrected claims) to refund overpaid premium. For the 2019 RY, the recalculation of premium will occur prior to any billing or claim processing.

103366

Companion Policy: Logic is needed at the premium line level with the Companion Policy functionality to account for claims processing. There will be times that the System will need to temporarily block the established link without breaking the permanent link, which rolls from Reinsurance Year to Reinsurance Year. The Claims Team will be updating the existing MPCI Claims functionality to account for the temporary companion link blocks when claims are processed on either the Source Policy or Companion Policy when acreage report revisions apply. They will set new database codes within the CompanionLink database field of the MpciPremiumLine DB table with TFS #102190. This ticket will be adding the two new CompanionLink database field codes for the MpciPremiumLine DB table as well as updating the current companion policy syncing logic to be used once the codes are set in the database tables by the claims logic.

NOTE: The changes listed below will only take place when the Source Unit and/or Companion Unit(s) have a claim processed during the applicable RY and acreage report revisions are applied. If the Source Unit and/or Companion Unit(s) have a claim but no acreage report revisions are applied, no changes will be made to the existing companion links. MPCI Claims logic will set these new values at a premium line level when claims with acreage report revisions are being processed.

Allow the following Companion Flags to be applied in the MpciPremiumLine.CompanionFlag field:

• BS: Blocked Source
• Will replace the existing CompanionLink db value of S (Source).
• This will be set by claims logic when a claim exists for the Source Unit and acreage report revisions are applied when the claim is processed. If no acreage report revisions apply but a claim exists, the S (Source) db value will remain in place.
• When CompanionLink code = BS (Blocked Source)
• All Companion Unit premium lines (CompanionLink = C and SourceOID = premium line OID) that have established Companion links with the Source Unit that has the BS code will be set to BC (Blocked Companion).
• Once the new BS code has been set on the MpciPremiumLine table by the claims logic, upon Save, the System will behave as if a Companion link was not established for the current RY and no data syncing from the Source Unit to the Companion Unit(s) will be done. However, the database linkages will remain in place in order to roll into the next year’s policy to avoid having to re-establish the links in a new RY.
• The Link icon will still display so that users know the permanent companion link exists and so that it can be manually broken if needed, but the two previously-linked premium lines will no longer be kept in sync during the applicable Reinsurance Year.
• In this scenario, the wording within the Link icon’s popup message will update to add the following note: "Companion Link has been blocked due to claim activity."
• BC: Blocked Companion
• Will replace the existing CompanionLink db value of C (Companion).
• This will be set by claims logic:
• When a claim exists for the Source Unit and acreage report revisions are applied when the claim is processed, or
• When a claim exists for this Companion Unit and acreage report revisions are applied when the claim is processed.
• When CompanionLink code = BC
• All previously read-only, synced UI fields on the applicable premium line will be converted to editable, allowing for revisions.
• No data syncs will be made from the Source Unit to the Companion Unit with the new BC value from that point forward during the applicable Reinsurance Year.
• The Link icon will still display so that users know the permanent companion link exists and so that it can be manually broken if needed, but the two previously linked premium lines will no longer be kept in sync during the applicable Reinsurance Year.
• In this scenario, the wording within the Link icon’s popup message will update to add the following note: "Companion Link has been blocked due to claim activity."

Before establishing any new companion links, the System should first determine if the Source Unit already has a BS value set in the MpciPremiumLine.CompanionFlag field.

• If Source Unit has "S" and Companion Unit has "C", the System will allow a new companion link to be established and allow data syncs.
• If Source Unit has "BS", the System will allow new companion links to be established but rather than setting the C (Companion) value for the linked Companion Unit(s), the System will set the BC (Blocked Companion) value in the MpciPremiumLine.CompanionFlag field. The System will not sync any of the data from the Source Unit to the Companion Unit for the remainder of the RY, unless the companion link has been removed.
• The Link icon will still display so that users know the permanent companion link exists and so that it can be manually broken if needed, but the two linked premium lines will not be kept in sync during the applicable Reinsurance Year.
• In this scenario, the wording within the Link icon’s popup message will update to add the following note: "Companion Link has been blocked due to claim activity."

NOTE: TFS #102741 has been created to update the MPCI Policy Roll logic to convert the temporary companion link blocks put in place with the new BS and BC database values so standard companion policy syncing will resume for the new Reinsurance Year.

102174

Enterprise Units: During internal testing of enterprise unit functionality, a bug was identified with the Malt Barley Endorsement (ME Option). Previously, when the ME option was applied to the detail line, the System didn't apply EU or EP unit structure. Per RMA, EU/EP are valid unit structure options under the ME option. Given this, the System should allow the EU or EP unit structure codes when the ME option applies. The System has been updated to allow EU or EP unit structure when the ME option applies.

101486

Fast Edit AR: With TFS #98646 in the 7.100 release, logic was added to only allow a contract price to be selected in Fast Edit AR if the CP option was on the detail line. Since there are certain crops, including Contract Seed Peas and Contract Seed Beans that allow or require a contract price but the CP option is not available in the ADMs, this change resulted in users no longer being able to apply a contract price through Fast Edit AR for these crops that the CP option is not available on. Currently, there is a warning in place within Fast Edit AR for crops that require a contract, like Contract Seed Beans and Contract Seed Peas, but for which the CP option was not available. This warning helps to identify these crops but does not identify the crops that require the CP option.

Due to the CP option not being available for certain crops that require a contract price, the logic previously implemented with TFS #98646 that prevented the display of the contract price in the contract info dropdown if the CP option was not selected was removed. Now, a hard edit requires the CP option to be selected if it's elected on the coverage and the user has selected a contract price but not the CP option in Fast Edit AR.

102737

With TFS #69353, validations were implemented for the Maintain Detail Line page as well as Fast Edit AR to ensure that an NI Practice always reflected a Solid Pattern and an NI-SR Practice always reflected a Plant Pattern of something other than Solid if the reported acres value for the detail line was greater than zero and insurable.

An enhancement was requested on the Maintain Detail Line page so that when the crop practice equals Non-Irrigated, the Plant Pattern can ONLY equal Solid. Previously on this page, the user was able to pick a Planting Pattern other than Solid, and upon Save and Exit, the System did not throw an error that this was incorrect. It appeared as if the data was saved; however, when the user re-entered the Maintain Detail Line page, the System had correctly set the Planting Pattern to Solid and Skip Row Factor equal to 1.00. If a user within the Maintain Detail line selected Save, the System corrected the Plant Pattern to equal Solid. In Fast Edit AR, if the crop Practice was equal to Non-Irrigated, then the System had already set the Plant Pattern to equal 1.00 and this was read-only; the user was not able to change this information. Also, if the crop Practice was equal to Non-Irrigated Skip Row, if the user tried to select a Solid plant pattern, a hard edit was received and the user had to correct it before being able to continue.

With this ticket, a hard edit was implemented within the Maintain Detail Line page so that if the crop practice is Non-Irrigated, then the Plant Pattern can only be equal to Solid. If anything other than Solid is selected upon Save or Save and Exit, the user will receive a hard edit stating "A planting Pattern of Solid is required for Non-Irrigated Cotton".

103066

System Infrastructure

DESCRIPTION ID #

A 2020 Special Provisions Update that was made available from RMA on 4/23/2019. The following Special Provisions for 2020 have been downloaded (2020_SPOI_0430.zip):

• Strawberries (0154) - Plan ARH (47)
• CA (06) - multiple counties
• Forage Seeding (0032) - Plan DO (50)
• CA (06) - multiple counties
• MD (24) - multiple counties
• NV (32) - multiple counties
• NJ (34) - multiple counties
• NY (36) - multiple counties
• PA (42) - multiple counties
• UT (49) - multiple counties
• VT (50) - 1 county
• Fresh Market Sweet Corn (0044) - Plan DO (50)
• FL (12) - multiple counties
• GA (13) - multiple counties
• Peppers (0083) - Plan DO (50)
• FL (12) - multiple counties
• GA (13) - multiple counties
• SC (45) - multiple counties
• Fresh Market Tomatoes (0086) - Plan DO (50)
• FL (12) - multiple counties
• Sugar Beets (0039) - Plan APH (90)
• CA (06) - 1 county
• Cabbage (0072) - Plan APH (90)
• FL (12) - multiple counties
• GA (13) - multiple counties
• TX (48) - 1 county
• Clary Sage (0079) - Plan APH (90)
• NC (37) - multiple counties
• Potatoes (0084) - Plan APH (90)
• CA (06) - multiple counties

103881

A 2020 RY Special Provisions Update was made available from RMA on 4/29/2019. The following Special Provisions for 2020 have been downloaded (2020_SPOI_0430.zip):

• Annual Forage (0332) - Plan RI (13)
• CO (08) - multiple counties
• KS (20) - multiple counties
• NE (31) - multiple counties
• NM (35) - multiple counties
• ND (38) - multiple counties
• OK (40) - multiple counties
• SD (46) - multiple counties
• TX (48) - multiple counties

103146