Release Notes 6.115.0

The AFA Annual Forage App/Cancel/Trans form was modified for use within the eSign Wizard process. For this document, the eSign Wizard will:

a) Conditions of Acceptance section

The AFAR Acreage Report - Annual Forage form was modified for use within the eSign Wizard process. For this document, the eSign Wizard will:

a) Native Sod section in states where applicable

b) Measurement Service Requested

NOTE: Measurement Service Comment Entry is OPTIONAL

a) Remarks section

Raisin Acreage & Tonnage Report: MCT received a request to include acres when a user has selected the "Pre-print for next year" Print Option. When the "Pre-print for next year" Print Option is selected if the detail line has been processed (meaning an AR Sign Date as been entered), then acres will print if available from the current year.

For example: 23.30 acres were reported and an AR Sign Date has been entered for CY 2018 / RY 2018. Then, 23.30 acres will print on the form when the “Pre-print for next year” print option is selected with the other pre-print data.

NOTE: If the "Print Acres" or "Print Tons" Print Options are selected with the "Pre-print for next year" Print Option, the form will ignore the "Print Acres" and "Print Tons" Print Options. Those Print Options are intended to print tons and/or acres when that data has been entered without an AR Sign Date for the current year.

The Annual Forage Application has been updated in the following ways for all Crop Years:

When toggling between reports from within an Unprocessed Report (Reports > MPCI Reporting > Unprocessed Reports > APHs, Area Plan Production, CLU, Coverages, Detail Lines, or Final Tonnage), the filter options below the report selection list were not being updated to the correct Unprocessed Report selected. This has been resolved.

An issue was reported where the Policy Type dropdown on the Pre-Printed Applications page (Reports > Private Products Reporting > Pre-Printed Applications) was only displaying the "All" option. This issue has been corrected and all applicable policy types are displayed as options in this dropdown now.

An issue was found where the Acreage Report - CLU Form was not printing the correct Coverage Level when the coverage had different Coverage Levels based on Practice. The Acreage Report - CLU Form has been updated to print the correct Coverage Level when the coverage has different Coverage Levels based on Practice.

NOTE: This form is not intended to be used for Annual Forage, Pasture, Rangeland, Forage (PRF), Apiculture (API), Category C Crops, Perennial Crops, Plan Code MP (16) associated with a YP or RP coverage, Plan Code MP-HPO (17) associated with a YP or RP coverage, Plan Code STAX-RP (35) associated with a YP or RP coverage, Plan Code STAX-RPHPE (36) associated with a YP or RP coverage, Nursery, or WFRP.

Yield Stack was implemented as a new product that will be available for the 2018 Crop Year. Following the initial production of Yield Stack, the AIP requested updates to the forms and UI associated with Yield Stack to better comply with the product. This ticket encompasses the changes for the Schedule of Insurance forms. The Yield Stack Schedule of Insurance (SOI) is available in all areas where the SOI is available to print. These changes apply to the 2018 and succeeding Crop Years. All of the form data is populated from the associated fields on the UI:

Yield Stack was implemented as a new product that will be available for the 2018 Crop Year. Following the initial production of Yield Stack, the AIP requested updates to the forms and UI associated with Yield Stack to better comply with the product. This ticket encompasses the changes for the Confirmation of Coverage (COC) forms for the Yield Stack Private Product. The Yield Stack COC is available in all areas where the COC is available to print. These changes apply to the 2018 and succeeding Crop Years. All of the form data is populated from the associated fields on the UI:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The Iowa Department of Agriculture and Land Stewardship (IDALS) has offered an additional State Subsidy program for the 2018 RY. The program is targeted at select producers who use proper cover crop practices and is offered to producers who certify eligible land. The eligible land will be identified by the IDALS at a CLU and/or Legal level, and a listing will be provided to the RMA. The producer enrollment deadline for this program will be January 15th of each RY in which the program is offered. Applicants will be reviewed/accepted by the IDALS.

AIPs can elect to participate in this program by signing the Memorandum of Understanding (MOU) on file with the IDALS.

Funding will be provided to the RMA by the IDALS, and the RMA will determine the appropriate subsidy reduction for each P11 record (i.e., premium/detail line) that is submitted through PASS containing related P27 record(s) with CLU and/or Land ID information that is included on the eligible land listing. RMA determined values will be returned to the AIP as part of their error file. The value(s) will be provided in P11 output field 101 (State Private Subsidy Amount). AIPs are required to include the reduced subsidy on their Billing Statements with the description: “IDALS – Cover Crop Program”.

To implement this change, during the standard Error file import process, the RMA determined subsidy values will be imported and stored on the relevant detail lines. A new Mark Complete Process will then sum these values for the coverage. The summed value(s) for the coverage(s) will be included on the Billing Statement with the required description from the MOU.

The necessary changes to Billing Statements are slated for the 7.000 release.

NOTE: The new functionality going out with 6.115 could not be tested in the System because the RMA does not have the necessary pieces in place on their end to allow for testing at this time. It appears they have their changes slated for their June production release. This functionality will be tested when possible.

This functionality was implemented for the 2018 RY only. If the program is extended to future RYs, the System will need to be updated to accommodate those years.

The following exceptions apply to this functionality:

According to the RMA, the IDALS program is based on P27 records. In order to receive the additional subsidy, a P27 with information that matches the eligible acreage and land listing will need to be submitted to the RMA. The following crops/plans do not require a P27 record, so subsidy reductions may not be provided in all scenarios:

Fast Edit AR: During internal testing, a gap in the add new detail line validations on the Fast Edit AR was identified. The System was allowing users to add detail lines for any Type/Practice regardless of the Planting Season/ARD selected on the Fast Edit AR. For example, if a Spring planting season was selected, the System was allowing new detail lines to be created for all Types, including Fall/Winter.

A new validation has been added to the add new detail line section of the Fast Edit AR. When the Add New Unit button is selected, if the Type/Practice selected is outside of the Planting Season/ARD selected on the Fast Edit AR, an error will display.

NOTE: The Final Planting Date is used to determine if a Type/Practice is a Fall or Spring Planting Season.

Peanuts: The RMA expanded contract pricing for Peanuts to Plans 02 and 03 for the 2018+ RYs. Prior to this, contract pricing was only available for Plan 01. The RMA also changed their M13 submission requirements which allowed MCT to modify how Peanut Acreage Reports are processed in the System. A user will now be able to use Fast Edit AR where they weren't able to do so in the past, so processing should now be more simplified and efficient.

For the 2018+ RYs, the System was modified to allow Peanut Acreage Reports to be processed within Fast Edit AR. It will also now allow contract pricing to be applied to Peanut Plans 02 and 03. Rather than applying Contract information at a unit level, users will now apply it at a coverage level. This will be done by:

When selected, the System will use the contract records tied to the Peanut coverage to determine what contract price to apply to all Peanut lines with the same Type. This includes a Weighted Average Price (WAPP) if/when necessary. The "CP" option will also be applied to the coverage and applicable detail Lines during this process. This functionality will trigger any time one of the following actions occur:

Removing the checkbox within Fast Edit AR will remove contracts. An option will be available from the Additional Functions dropdown on the Detail Lines tab as well.

Because contract pricing is determined at a type level, the System will now require a Type to be keyed on each contract record tied to a Peanut coverage.

Also, the Apply Contracts checkbox has been removed from the Maintain Detail Line page. This will prevent the Apply Contract Information banner from displaying and allowing a user to apply a contract(s) at a unit level.

NOTE: TFS #78800 will implement Transmission changes.

Quotes: The functionality to designate a Primary County was added to quotes a few years ago. The intention of this was to allow users to set the designation so it would be in place if/when the quote was converted to a policy. During some internal testing, it was found the Add County button that allows users to create an actual added county coverage (intended to be utilized after the SCD) was displaying on quotes. However, this functionality is not applicable to quotes. The MPCI quote pages have been updated to no longer display the Add County button. This button will only display on policies when applicable.

Fast Edit AR: The Fast Edit AR functionality supports the creation of a new detail line and APH for added land from within the Fast Edit AR page. A bug was identified when a new detail line for added land was applied against an HR-ACE coverage. The System returned a "Sorry..." error and logged an Elmah error to the database. This has been corrected within the scope of this ticket.

Detail Lines: During internal Enterprise Unit testing, a bug was found where the System was setting the incorrect BU/OU unit structure on one Practice when EP was elected on the other practice. This scenario only occurred when the following conditions existed:

In this scenario, the System should set the unit structure to BU on the single line for which EP is not elected on; however, it was setting the unit structure to OU. The unit structure logic that determines the BU/OU unit structure on the practice EP is not elected on has been updated to apply the correct unit structure.

APH: During internal testing of the "F" High Risk Yield Type, a bug was found as it relates to New Producer. When a High Risk T-Yield area is applied to an APH with less than 4 years of history, "F" Yield Types are used to complete 4 years of history in the APH. If the grower was designated as New Producer and the High Risk T-yield area was removed from the APH, the System correctly updated the APH to "I" Yield Types instead of "F" Yield Types. However, if the High Risk T-Yield area was added back to the APH, the System left the "I" yield types and added "F" Yield Types to the APH. The APH Logic has been updated to remove the "I" Yield Types when a High Risk Y-Yield area is applied.

Hail and Production Hail: An update was made to ensure that, if the parent premium line has no premium on it, the System will not calculate premium on any attached endorsement lines. This pertains to Hail and Production Hail.

Crop Hail: Pro Ag currently uses a 24-hour lockout that allows agents to make update to their Crop Hail policies within 24 hours of the Convert to Policy functionality being initialized. There was an issue where, on rolled quotes/binders, the agent users were not able to see the Add hyperlink to add either an optional endorsement or additional coverage to the parent line. Within the 24 hours of Convert to Policy being initialized, the agent user will be able to use the Add hyperlink on the parent hail line to add either optional or additional coverage as a child line for the coverage. Once the policy has been converted for over 24 hours, the user will only be able to add additional coverage through the Add hyperlink on the parent line until the Crop Hail product's expiration date, if one has been implemented for the year.