Release Notes 6.095.0

A Special Provisions update was made available from RMA on 3/13/2018 with updates for Cotton (0021) with the YP (01) plan. The file was downloaded and implemented in the System.

A Special Provisions update was made available from RMA on 2/20/2018. The file was downloaded and implemented in the System.

Acreage Report: During the 6.080 release testing, it was found that non-premium Acreage Types were printing on the Acreage Report. When printing the Acreage Type field, the alpha code of the Acreage Type, or Uninsured Reason:

NOTE: The acreage types X and Z are related to non-premium acreage codes set by the System and have nothing to do with the dropdown on the detail line. These are set when a user processes a 0-acre acreage report for the unit/county.

This change is applicable to all Reinsurance Years.

Attachments: An Attachment Type of "MPCI Application Checklist" has been added as an MPCI Attachment Type. This attachment will have a status as a current year attachment type.

For Pre-Printed Applications (Reports > Private Product Reporting > Pre-Printed Applications), the "Include Acres and Practice with Detail Information" option should only be displayed after the Include Detail Line Information checkbox has been selected. This has been resolved.

Margin Protection: MCT was made aware that MP and MP-HPO plans were printing on Acreage Reports and Production Reports when the MP and MP-HPO plans were associated with Yield Protection (YP) or Revenue Protection (RP) coverages. For MP and MP-HPO related coverages, the Production Report and Acreage Report for the base coverage will be used as the Production Report and Acreage Report for the MP and MP-HPO coverage. These updates below apply to the forms listed below for all years (the System will control when MP [Plan 16] and MP-HPO [Plan 17] can be selected).

The following forms were updated to not print MP and MP-HPO data in the Crop Summary (if the form has a Crop Summary section) and Detail Line section when the Margin Protection coverage is associated with a YP or RP coverage; however, MP and MP-HPO standalone coverages will print on the forms.

Exceptions: 1) Schedule of Insurance (SOI) / Production Report – No changes were made to this form. This form is designed to not print Detail Lines for Nursery (FG&C) (0073) or for plans RI (13), VI (14), MP (16), MP-HPO (17), STAX RP companion policy (35), STAX RP-HPE companion policy (36), AD (43), and WFRP (76). 2) APH Database / Acreage Reporting Form – No changes were made to this form. Currently no Margin Protection coverages print on this form. The form was designed to print coverages with plans YP (01), RP (02), RPHPE (03), or APH (90) and, if the policy has a coverage(s) with plans TDO (40), DO (50), or YDO (55), then those coverages will also print on the form. The form prints pre-headed if printed for standalone Margin Protection coverages. 3) Production Report / Acreage Report (NOTE: This form is not turned on for all AIPs per their request.) – No changes were made to this form. Currently, Margin Protection coverages print on this form; this form is not conducive to be used for Margin Protection coverages.

A request was received to print the Hail data at 100% share when printing on the MPCI / Hail Combo Application with the pre-print for next year print option. The rule for printing data in the Hail Plan and $/Acre (For Approved States Only) field was updated as follows:

ELSE, if the associated Hail coverage has no endorsement(s) attached, THEN the associated Hail coverage will print.

These updates are applicable to all Crop Years. The Application / Change / Transfer / Cancel Form is available to print within an individual MPCI Policy on the Print tab and via the Tools > Batch Printing menu.

On the Pre-Printed Application page (Reports > Private Products Reporting > Pre-Printed Applications), the Private Products are now reloaded based on the year that is selected.

This ticket updated the ICE COC following the ICE changes implemented with TFS #84142 (which updated ICE Forms to display an ICE Option). If the ICE Option equals BY, BR, CY, or CR, then "N/A" is displayed under the % of Price field. These changes are applicable to 2018 ICE Policies going forward.

When the user was printing an application for a WATTS product from the Print Private Product Blank Forms page (Tools > Print Private Product Blank Forms), the System was giving the user the option to select to "include extra app page", but this option shouldn't have been visible. A correction was made to the Print Private Products Blank Forms page so that if the user selects to print the application for a WATTS product, the extra option to include an extra app page will not display since it's not applicable.

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 2014 update was made by RMA and has been implemented in the System. The following tables have been updated for 2014:

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

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

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

Fast Edit PR: It was determined that if a user updates production in Fast Edit PR for one or more but not all coverages that require production on a policy, the System was (upon Save or Save & Exit) not always displaying the correct coverage records on the Assigned Yield popup and/or incorrectly applying Approved Yields to unprocessed crops. The System was updated to properly handle Assigned Yield functionality when one or more but not all coverages that require production to be reported are updated during the same Fast Edit PR session. This includes adjustments to the current Assigned Yield popup to properly display the correct coverage records that qualify for Assigned Yields and allow the user to choose how they want each coverage to be updated. For each coverage that qualifies for Assigned Yields, the following options are available:

A change was made to optimize overall performance when loading policy pages as well as to limit the number of database calls being made. This was discussed on the 3/6/18 All AIP call, so MPCI leadership groups have received the background on the change. With this ticket, all of the banners that typically load under the View MPCI Coverages grid, if applicable, will load collapsed instead of expanded. These banners include Assignment of Indemnity, Contracts, Written Agreements, Inspections, etc. In addition to displaying collapsed, the buttons for Add/Delete and similar functions were moved from the shaded banner bar to the top of the section when that banner is expanded, so they now fall within the applicable section of the page.

Perennials: The standard procedure for determining the Production Reporting Date is the earlier of the Acreage Reporting Date or 45 days after the cancellation date. However, there is a Special Provisions statement for a number of Perennial crops that supersedes this standard procedure and states the Production Reporting Date will be equal to the Acreage Reporting Date. Prior to the 2018 RY, the Special Provisions for Almonds did not include the statement around the Production Reporting Date and, therefore, Almonds had never been included in this logic. Now, for the 2018+ RYs, the Special Provisions for Almonds do include the statement, "the production reporting date will be the acreage reporting date”. This logic is used in the System to determine which date to display as the Production Reporting Date on the Signature Maintenance page.

APH Drawer: During internal testing of the Add New APH Drawer implemented with TFS #66994, a gap in the validation logic was found around the t-yield map area. The System was defaulting the map area selection to the first available selection rather than defaulting to a value of "Select". In addition, there was no validation in place to require the user to make a map area selection. This issue was also affecting the standard APH drawer. The following changes have been made with this ticket:

APH: There is a validation in place on the Add New and Maintain APH pages that does not allow a year greater than the current RY-1 to be entered in the Production History grid. During some internal testing, a bug was found where the year became read only if a year equal to the current RY was entered. The validation error triggered due to the year being greater than the current RY-1; however, since the year displayed as read only, the user could not change the year. The APH logic has been updated to no longer make the year read only.

EU/EP: In the 6.085 release with TFS #82141, some enhancements to EU/EP functionality were implemented to account for changes in the 2018 procedures that allow growers to elect EP on a single practice (irrigated vs. non-irrigated). During internal testing of this functionality, a bug was found. When the unit structure was changed on the coverage prior to AR sign dates being applied, the System was not consistently updating the unit structure on the detail lines. The EU/EP logic was updated so the System is now correctly updating the unit structure on the detail lines when it is changed prior to AR Sign Dates being applied.

NOTE: Once AR Sign Dates are applied, EU/EP validation takes place at mark complete.

EU/EP: In the 6.085 release with TFS #82141, some enhancements to EU/EP functionality were implemented to account for changes in the 2018 procedures that allow growers to elect EP on a single practice (irrigated vs. non-irrigated). During internal testing of this functionality, a bug was found.

By design, the System does not invoke EU/EP validation logic until acres/AR sign dates are applied and mark complete is processed. Prior to EU/EP validation, the System should apply the unit structure elected on the coverage. The bug identified was that the System was attempting to validate for EU/EP prior to acres/AR sign dates being applied. The EU/EP validation logic has been updated to only trigger once acres/AR sign dates are applied and mark complete is processed. Prior to this, the System will apply the unit structure elected on the coverage or BU/OU, as applicable, if nothing is elected on the coverage.

EU/EP: In the 6.085 release with TFS #82141, some enhancements to EU/EP functionality were implemented to account for changes in the 2018 procedures. As part of the 2018 procedural changes, growers now have the ability to elect enterprise units on a single irrigation practice (irrigated vs. non-irrigated) while electing either BU/OU on the other irrigation practice. If EP is elected on a single practice and, at acreage reporting, the EP qualification rules are not met for the single practice, BU/OU applies to both practices.

During internal testing of the EU/EP enhancements, a bug was found where the System was setting the unit structure to EU rather than BU/OU when it was determined that the practice did not qualify for EP. The EU/EP validation logic has been updated to no longer apply EU when EP is elected on a single irrigation practice and the System determines the practice does not qualify for EP. In this scenario, the System will apply the underlying BU/OU unit structure.

Fast Edit AR: During internal testing of the new Add New APH Drawer in Fast Edit AR, a refresh issue was identified. When the Add New APH Drawer was launched, the Detail Line Drawer tab would initially display. After a brief pause, the System would then display the Add New APH Drawer. During the time the Detail Line Drawer displays, it appears as if it has fully loaded and can be edited by the user. This was causing confusion and users thought they had selected to open the Detail Line Drawer rather than the Add New APH Drawer.

Development determined this was due to one of two database calls being slower than the other. Given this, the length and frequency of the delay were impacted by the environment, the amount of traffic, and the number of jobs in progress. To reduce confusion, the System has been updated to display the drawer as grayed out during the time it takes to fully load the Add New APH Drawer.

Fast Edit PR: During internal testing, an issue was found by a user who was unable to view the Detail Lines tab in the drawer within Fast Edit PR for a unit that was a winter type Barley with the WO option. The issue was determined to be the code trying to add a null object to a list in two places, which is not allowed. The code was updated to add a null check around the call so the System doesn't try to add extra null objects.

STAX: For the 2017+ RYs, changes were made to properly rate STAX detail lines for a STAX coverage that is related to a base coverage when a Written Agreement (WA) was issued for both the base and STAX plan codes. Going forward, when this scenario exists, a Written Agreement coverage record needs to be created for the base coverage AND the related STAX Coverage. The WA for the STAX coverage must also be properly associated with the applicable STAX detail lines. STAX Written Agreement associations will not be retained on STAX detail lines when STAX detail lines are recreated via the Additional Functions dropdown on the Detail Lines tab. Users will need to re-associate the STAX WA when this occurs.

A correction was done so that if a new unit is added to a Production Hail policy that already had the acres submitted and the batch endorse applied, then once the user restores the policy and submits acres again, the added detail line will now have the same endorsement that was batch added to the previous lines.

Additional logging was added for the Mark Complete process that updates private products. In some cases, a private product cannot be updated. In those cases, a message will be logged and can be viewed via the private product Refresh Log button.

Additional messages that may display are as follows:

Fast Edit: The Fast Edit page was rounding the insured share to the nearest tenth. This has been corrected.

Fast Edit: When the user was using Fast Edit for an Annual Hail policy, the Fast Edit page was not accepting the app date that was already entered, stating one still needed to be entered. A correction was made to Annual Hail policies so that, when using the Fast Edit page to input a detail line, the line will now accept that an application date has been entered once the user enters one.

Margin Protection: A request was made to include Margin Protection as an eligible MPCI plan to link with ARCH and CPP private product policies beginning in 2018. This has been implemented.

Price Flex: The second and third submit of acres on Price Flex policies were not pulling over changes from the MPCI side. This has been corrected.