6.110.0 Release Notes

TFS #44164 added print logic for the Production Report form on policies with 200+ detail lines when the printing is done within the Print tab of that policy where, when the print button was clicked, the job was sent to the Service Bus to generate, which required the user to go to the Print Queue to retrieve it. AIPs requested that the logic be updated so the user no longer has to go to the Print Queue to retrieve the generated form. With this ticket, the print logic was updated for the Production Report form so users no longer have to retrieve large Production Reports from the Print Queue (Tools > Dashboard > Print Queue). This change is only applicable to the Production Report form when the policy has 200+ detail lines.

With this ticket, Planting Pattern now prints on the Acreage Report. Additionally, these other updates were made:

These updates are for all years and all report styles.

With this ticket, Planting Pattern now prints on the APH Database / Acreage Reporting Form behind the Practice code when applicable to the selections on the premium line (e.g., NIRR-SR (063) (6x1)).

NOTE: The version date was not updated since this is not a new format, just additions to the data that prints on the form.

This ticket implemented the following updates to the Plant Inventory Value Report (PIVR) to assist the Grower in identifying when the "BL" option code has been elected.

Updates to the PIVR are applicable for all crop years. The PIVR is available to print from the MPCI Print tab and in Batch Printing.

A few items were reported to MCT on the Supplemental Land Page during the 6.105 UAT cycle. The updates made with this ticket are applicable to all years.

The Supplemental Land Worksheet / Page is currently available to print as a stand-alone form or with the following forms:

By request, a "Pre-print for next year" print option was added to the Raisin Acreage and Tonnage Form that will display when the Pre-Filled report style is selected. This new print option is listed in alphabetical order for all years. When the "Pre-print for next year" print option is selected, the data will be pre-printed on the form if available on the policy.

A bug was reported on the Acreage Report where the "Z" indicator in the Crop Summary section was not working correctly. This issue has been resolved and the update made is applicable to all years. Now, when printing the Acreage Report in a Pre-Filled report style with the “Omit Zero AR Line(s)” print option selected, the “(Z)” indicator will print behind the coverage’s Crop Code for the coverages where the zero AR line(s) did not print in the detail line section (e.g., "Corn (0021) (Z)").

NOTE: Detail lines are considered to be zero AR lines when there is an AR Sign Date; if an AR Sign Date is not entered, then the detail lines and Crop Summary will not consider those lines zero AR lines.

An enhancement was made to the Private Product Policy Register (Reports > Private Product Reporting > Policy Register) to print "Payment Type" followed by a dash and what was selected for that filter on the report page (e.g., "All", "Cash", "Other") in the Report limited to section at the beginning of the report.

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:

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

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

An 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:

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

Yield Cup: In the 6.075.0 release, APH logic was updated to account for RMA's conversion of the Yield Cup procedures to the new Yield Cup "YC" option in 2018 for crops with an 11/30 or later Filing Date and for all crops in 2019 (see TFS #82114 for more information regarding the Yield Cup changes for 2018 and 2019). As part of these Yield Cup changes, the calculations of the Yield Cup of Contract Seed Beans (CSB) and Contract Seed Peas (CSP) have been impacted.

When determining the cupped yield for CSB and CSP, the prior year yield must first be multiplied by the most recent year’s Reference Year Adjustment Factor (RYAF) and then by 90%. The value determined through this calculation is the cupped yield for CSB and CSP. If this value is greater than the yield calculated using other methods (YA, TA, YE) or greater than or equal to the yield floor, then the Yield Cup applies.

This is a testing-only ticket to confirm the changes in 6.075.0 accounted for the additional calculation for CSB and CSP. No code changes were made as part of this ticket. All APH calculation changes for YC were implemented with TFS #82114 in the 6.075 release.

With Informational Memorandum PM-18-013, RMA announced some APH changes for crops produced under organic practices in certain Texas counties. As part of the updated procedures, organic practices (both certified and transitional) have been removed for Corn (0041), Cotton (0021), Grain Sorghum (0051), and Soybeans (0081) in the following counties:

Aransas, Atascosa, Austin, Bastrop, Bee, Bexar, Brazoria, Brooks, Burleson, Calhoun, Caldwell, Cameron, Chambers, Colorado, Comal, DeWitt, Dimmit, Duval, Fayette, Fort Bend, Frio, Galveston, Goliad, Gonzales, Guadalupe, Harris, Hays, Hidalgo, Jackson, Jefferson, Jim Hogg, Jim Wells, Karnes, Kenedy, Kleberg, La Salle, Lavaca, Lee, Liberty, Live Oak, Matagorda, Maverick, McMullen, Medina, Nueces, Orange, Refugio, San Patricio, Starr, Travis, Victoria, Washington, Webb, Wharton, Willacy, Wilson, Zapata, and Zavala.

These crops may be eligible to be insured under the organic practices by a written agreement; however, if a written agreement is not requested or written agreement criteria are not met, the crop may be insured as conventional practices. RMA will still require separate APH databases for conventional, certified organic, and organic transitional practices; conventional and organic APHs will not be allowed to be combined. In order to track organic acreage being insured under a conventional practice, RMA has added two new APH Procedural Exception Codes.

Any APH databases for certified organic or transitional organic acreage being insured under a conventional practice must be identified by one of these APH Procedural Exception Codes; furthermore, if less than 4 years of actual history exists, standard variable T-Yield procedures apply. This includes the use of the T-Yield for the conventional type and practice. However, in the event an SA T-Yield applies, the SA T-Yield will be calculated using only APHs reflecting the same "O" or "T" APH procedural exception code.

In order to account for these changes, System updates were needed to allow selection of the "O" and "T" APH Procedural Exception Codes on the detail line. In addition, the Simple Average T-Yield calculation needed to be updated to consider these new APH Procedural Exception Codes. See PM-18-013 for more information on changes to organic practice procedures in Texas. With this ticket, the following changes were made:

Back in 2016 when Margin Protection (MP) functionality was originally implemented, the number of MP policies written by AIPs was limited. At the time, the small number of policies did not warrant the amount of resources required to implement automatic detail lines created for Margin Protection policies with related coverages. Instead, a manual process was stood up that required users to create the Margin Protection detail lines separately from the base coverage detail lines and associate the base coverage detail lines with the MP detail lines.

In 2018, grower interest in Margin Protection policies has increased substantially and requests have been received for functionality to automatically create the MP detail lines when acres are keyed to the base coverage detail lines. This functionality will mirror the existing functionality for STAX. With this ticket, functionality to automatically create Margin Protection detail lines when acres are keyed to the base coverage has been implemented. This includes when acres are added/updated from the Add New Detail Line page; Maintain Detail Line page; Fast Edit AR; Fast Edit CLU; and CLU grid of the Land ID popup.

NOTE: Detail lines will only be created on the Margin Protection coverage if the coverage is related to a base MPCI coverage.

The System will create a detail line on the Margin Protection coverage in read-only format for each detail line on the related coverage where the following criteria exist:

Margin Protection detail lines will be created for all MPCI coverage parent detail lines meeting the criteria above as well as child lines that are created by duplicating a parent line in Fast Edit AR so long as the above criteria is met.

There are a couple of exceptions: Acreage designated as prevented plant on the MPCI detail lines will be uninsurable on the Margin Protection detail line, and the System will set an uninsurable reason of "UI". Acreage designated as late plant on the MPCI detail lines will be insurable so long as the plant date is prior to the Final Plant Date in the ADMs for the Margin Protection coverage. If the plant date is after the final planting date in the actuarials for the Margin Protection coverage, the System will apply an uninsurable reason of "U".

Margin Protection detail lines will be added, updated, and/or removed in the following scenarios:

NOTE: At the time this ticket goes to production, the Final Plant Dates for Margin Protection will not have passed. Therefore, the late plant functionality was not tested. TFS #88957 has been set up as a testing-only ticket to test this functionality once the Final Planting Date has passed.

A request was received to add a new database field to flag coverages with more than one Sales Closing Date (SCD). With this ticket, the following changes were implemented:

APH: Per the CIH, when a High Risk T-Yield Map Area applies and less than four years of history exist in the APH, "F" Yield Types should be applied in place of the Variable T-Yield or New Producer T-Yield Yield Types. A bug was identified internally where removing the High Risk T-Yield Map Area was causing the System to add the Variable T-Yield Yield Types to the APH grid but also retain the "F" Yield Types.

The APH logic has been updated to remove the "F" Yield Types from the APH grid when the T-Yield Map Area is changed to a non-high risk map area. In this scenario, the System will replace the "F" Yield Types with the Variable T-Yield or New Producer T-Yield as applicable.

Detail Lines: The Copy Detail Line functionality allows detail lines to be copied between policies and coverages so long as the Copy To and Copy From coverages are for the same State and County. An issue was found with the Copy Detail Line functionality around the HB option. When users attempted to copy a detail line from one coverage to an HB option coverage, the System acted as if the line was being copied but it would not actually finish copying the line even though both coverages were for the same state/county. Development research determined this issue was being caused by a detail line validation that requires a high-risk map area to be applied to HB option detail lines. With this ticket, the Copy Detail Line functionality has been updated to bypass the validation requiring a high-risk map area. A suspension is already in place to catch HB option detail lines that do not have a map area applied. This will allow the System to finish copying detail lines for HB option coverages.

EP: When the EP Option is applied (for 2018 coverages with a CCD on or after 11-30), a "Selected Practice(s) for EP" designation is required to indicate whether the Insured elected EP by Irrigated Practice only, by Non-Irrigated Practice only, or Both. When "Both" was applied, the System was not applying the following EU Overrides correctly:

EP was being applied to both NI and IRR Practices when either of these overrides was applied and the "Selected Practice(s) for EP" designation indicated "Both". When these overrides are applied, EP should only be applied to the practice designated in the override description—even if the "Selected Practice(s) for EP" designation reflects "Both". The System has been modified to correctly apply the selected EP Override to the correct practice(s) based on the "Selected Practice(s) for EP" designation.

Fast Edit CLU: A bug was identified on the Fast Edit CLU page at the time of scheduled deployment in the 6.105 release. All of the information about the functionality of the Fast Edit CLU page was provided to AIPs during the UAT hand off on 4/11. Those completing UAT testing need to refer to that documentation for general information about the page and its use.

This change deals with the logic and navigation of the FSN/Tract dropdown selection to load field lines for a specific FSN/Tract. If a user selected an FSN/Tract, made changes to the field lines and then selected a different FSN/Tract, fields entered on the prior FSN/Tract were dropped unless an interim save was performed. The selection of FSN/Tract performed a refresh of the page rather than just retrieving the next set of field lines to display. This has been corrected so users are allowed to retain all entries when this navigation process is used and perform a single save at the end of the processing session.

Fast Edit CLU: During internal testing of Fast Edit CLU, a bug was identified with a Cotton suspension around Planting Pattern. The suspension in question requires a Planting Pattern selection of "solid" on non-irrigated Cotton. When acres were processed via Fast Edit CLU and AR sign dates were applied, this suspension message was triggering on non-irrigated (not skip row) detail lines because the System was not correctly setting the "solid" Planting Pattern. Fast Edit CLU has been updated to correctly apply the Planting Pattern of "solid" to non-irrigated Cotton lines which will prevent the suspension from triggering incorrectly.

Fast Edit CLU: During internal testing of the new Fast Edit CLU page, a bug was identified around creation of child lines for prevented plant and late planted acreage. While processing in Fast Edit CLU, if an error message was received, once the error was resolved and Fast Edit CLU saved, the System was not correctly creating the child lines for prevented plant or late planted acreage. If an error message was not received prior to saving Fast Edit CLU, the child lines were created correctly. With this ticket, Fast Edit CLU logic has been updated to create the necessary child lines at save of Fast Edit CLU, regardless of whether an error was previously received and resolved. So long as the error is resolved, the child lines will be created as needed.

STAX: During internal testing of Fast Edit CLU, a bug was identified with Cotton coverages with a related STAX coverage. By design, when acres are processed on the base Cotton coverage, the System automatically creates the detail lines on the STAX coverage. QA testing found that if the acres were added to the base coverage by processing through Fast Edit CLU, then the STAX detail lines were not being created. Fast Edit CLU has been updated so that STAX detail lines are created when acres are pushed to the base coverage from Fast Edit CLU.

ICE: Increased Coverage Election (ICE) introduced several new policy options in 2018. To accommodate these options, the System was allowing one ICE Plus policy option to be associated with an MPCI Policy. A request was made to allow for the ability to have multiple ICE Options associated with an MPCI policy due to varying coverage by county/crop. With this ticket, the System will now allow more than one active ICE policy to be associated with an MPCI Policy. This will allow for the user to vary the ICE option for the grower by county/crop when needed. The user will not be able to key more than one ICE Policy Option for the same county/crop.

It was reported that, when using the Fast Edit CH/NP page, users were unable to delete the Place Name. A correction was made to this page so that users can edit the Place Name field on this page for Private Products.

A prior request had set the minimum Effective Date on a detail line with Escalator or Stepladder to be 05/15 of the policy year. This ticket removed the prior implemented change to allow for the Effective Date to use the normal 2-hour rule so replants will be able to be addressed on claims. The Effective Date is used when indemnity is being determined on claims.

An issue was found where the 24 hour rule was unable to be removed due to it being hard coded in the System. The hard-coded 24 hour rule has been removed.

The Restore button was not available on all products associated with an MPCI policy. An update was done to have the Restore option available on all products that are associated with an MPCI policy.

NOTE: Users will need to have admin permission for the particular Product Type Policy Maintenance in order to view/select the Restore button (e.g., for CHPP policies, the user would need the following admin permission: Policy > CHPP Policy Maintenance > Custom, "Admin").