Release Notes 6.000.0

Unprocessed Reports: By default, the Export to Excel button will now be hidden for the Unprocessed Reports until the Display Results button is selected. These reports are accessed from Reports > MPCI Reporting > Unprocessed Reports.

Dec Page: The MPCI Declaration Page was updated to match base form standards and to remove the Spouse, Assignment of Indemnity, and Power of Attorney fields. These updates are applicable for all Crop Years.

SOI / Production Report: A stand-alone STAX coverage is required to report production. Previously, STAX RP (35) and STAX RP-HPE (36) coverage information printed on the Schedule of Insurance (SOI) / Production Report Crop Summary and Premium Summary sections but no detail lines were printing; STAX detail lines should have been printing on the SOI. This ticket updated the SOI / Production Report to print the stand-alone STAX coverage detail lines. Also, the note to users that displays on the Print page was updated to more specifically state that the companion policies for STAX RP and STAX RP-HPE will not print on the SOI / Production Report.

Currently, the Acres and Plant Date fields do not print for a unit when the Acreage Reporting (AR) for the current year has not been processed; however, Liability and Premium were printing with a "+" after them, which indicated they're estimated values. Now, if AR for the current year has not been processed for the coverage, the System will not print the Liability and Premium for a unit’s detail line. In the Premium Summary, if AR for the current year has not been processed for the coverage, the System will not print Liability, Gross Premium, Subsidy Amount, A & O, Insured’s Premium, and Amount Due. The Admin Fee will also still print a $0.00. These changes apply to all coverages and all Crop Years.

SOI: Previously, the Schedule of Insurance (SOI) was rounding the Price to 2 decimal places for MPCI coverages with the Margin Protection (MP) plan instead of printing 4 decimal places. The SOI was updated to print the Price to 4 decimal places instead of rounding to 2 for MP detail lines.

SOI: The Schedule of Insurance (SOI) / Production Report was cleaned up regarding some items found during testing of the changes that were rolled out in the 5.010 Release:

NOTE: The SOI / Production Report will print for WFRP and Nursery policies. The only sections that print are the Headers, Crop Summary, and Premium Summary.

Private Products COC: An issue was reporting while printing Private Product Confirmation of Coverage (COC) forms where, when the policy was in a Binder status, "Binder" was not printing in the Status column. This ticket updated the COC form to display "Binder" in the status column when the policy is in a Binder status. Updates are applicable to all Private Product binders for all Crop Years. This update applies to the base Private Product Confirmation of Coverage form printed from the Print Forms tab and within the Batch Reporting Tool (Tools > Batch Printing).

The ICE 2018 update is now complete. The following tables have been updated for 2018:

The ICE 2018 update is now complete. The following table has been updated for 2018:

The ICE 2017 update is now complete. The following tables have been updated for 2017:

The ICE 2016 update is now complete. The following table has been updated for 2016:

The ICE 2015 update is now complete. The following table has been updated for 2015:

The ICE 2014 update is now complete. The following table has been updated for 2014:

The ICE 2013 update is now complete. The following table has been updated for 2013:

The ADM 2017 update is now complete. The following table has been updated for 2017:

The ICE 2013 update is now complete. The following table has been updated for 2013:

The ICE 2014 update is now complete. The following table has been updated for 2014:

The ICE 2015 update is now complete. The following table has been updated for 2015:

The ICE 2016 update is now complete. The following table has been updated for 2016:

The 2014 ADM update is now complete. The following table has been updated for 2014:

The ICE 2018 update is now complete. The following tables have been updated for 2018:

The ICE 2018 update is now complete. The following table has been updated for 2018:

The ICE 2017 update is now complete. The following table has been updated for 2017:

The ICE 2016 update is now complete. The following table has been updated for 2016:

The ICE 2015 update is now complete. The following table has been updated for 2015:

The ICE 2014 update is now complete. The following table has been updated for 2014:

The ICE 2013 update is now complete. The following table has been updated for 2013:

The ICE 2014 update is now complete. The following tables have been updated for 2014:

The ICE 2017 update is now complete. The following tables have been updated for 2017:

The ICE 2016 update is now complete. The following tables have been updated for 2016:

2018 Roll: The 6/30 CCD crops are typically rolled in early July to the next RY. For crops that have a single CCD but a dual ARD, MCT was prevented from rolling detail lines and APHs for these crops until after the 7/15 ARD was processed. In state/counties where the next RY's SCD is 8/31 or 9/30, this delay to allow processing to be completed often resulted in compressed processing time for renewals. A change was implemented to allow the roll to occur by Type in dual ARD areas:

With this change, when MCT rolls the crops in early July, only fall detail lines for impacted 8/31 and 9/30 SCDs will roll. When processing is complete, the AIP is responsible for notifying MCT that the spring lines can be rolled, joined with the initially rolled policy by the DB OID values.

NOTE: Roll logic has been modified for WA, ID, and OR. Only fall lines that reflect the WO option will roll with fall line types. Fall detail lines without the WO option fall under a 7/15 ARD, regardless of the 011 or 012 Type code on the detail line. For all other states/crops, detail lines and APHs will roll based on the fall Type code on the detail line. MCT will roll the coverage + fall lines initially and then a secondary roll will pick up the spring crop lines and add to the rolled policy in the new RY.

Claims: Several updates have been made to the View MPCI Claims page (on the Claims tab of MPCI policies). These updates include:

APH: The Short Rate collapsible banner from the Legacy Maintain APH page has been updated and implemented within the APH Drawer. Various changes were made to the Short Rate collapsible banner from within the Legacy Add New, View, and Maintain APH pages. These updates and the Short Rate reporting functionality were also added to the APH Drawer.

Annual Forage: RMA has announced some changes to the Annual Forage policy for the 2018+ Reinsurance Years (RYs). The policy is being updated to include four growing seasons rather than the previous two, one Sales Closing Date (SCD) rather than the previous two, and four Acreage Reporting Dates (ARD) rather than the previous two. To account for these changes, a number of System changes are required. First, the System roll logic required some special logic for the 2017 to 2018 RY roll only. This logic will roll the growing season and interval (Practice) codes based on the new growing season and interval structure. These changes were implemented in the 5.120 release with TFS #70613.

In addition to updating the roll logic, the 2018 policy changes for Annual Forage also required changes to the coverage functionality as well as the validation logic. This ticket will address the changes needed to the coverage functionality. TFS #70760 and #70761 will address the changes and additions required to validation logic.

With this ticket, the Coverage page for Annual Forage were updated to account for the 2018 RY policy changes. These changes include:

Annual Forage: RMA has announced some changes to the Annual Forage policy for the 2018+ Reinsurance Years (RYs). The policy is being updated to include four growing seasons rather than the previous two, one Sales Closing Date (SCD) rather than the previous two, and four Acreage Reporting Dates (ARD) rather than the previous two. In addition, due to the new growing seasons, many practice codes (intervals) have changed.

To account for the change from two growing seasons to four, the existing validations around Annual Forage were updated, including warnings and errors on the coverage as well as mark complete suspensions. In addition, a new suspension that requires all coverages to be CAT or all coverages to be buy-up was added. The changes are as follows:

Annual Forage: RMA announced changes to the Annual Forage policy for the 2018 Reinsurance Year. One of these changes is that there are now 4 growing seasons rather than the previous 2 as well as there being new Practice codes based on the growing season/interval combination. To account for the new growing seasons and Practice codes, the sort order of the View Coverages grid for Annual Forage coverages was updated. Previously, this grid did not take growing season into account when sorting coverages. Now, the sort order for Annual Forage coverages in the View Coverage grid has been updated as follows:

Enterprise Units: Beginning in the 2017 Reinsurance Year, Enterprise Units (EU) are available under the HR-ACE endorsement (HB) option. However, EU or EP (Enterprise Unit by Practice) must also be elected on the base (higher coverage level) coverage and the base coverage must qualify for EU or EP. The functionality to account for this was implemented with TFS #48193 in the 5.030 release.

The determination of whether or not EU/EP applies to a coverage is done during the mark complete process. Since the HB option coverage can only qualify for EU if the base coverage qualifies for EU or EP, the System should have been determining if EU or EP applies to the base coverage before determining if EU applies to the HB option coverage.

During some internal testing, a bug was found with this functionality. If both the base coverage and the HB option coverage were marked complete at the same time and the System determined at that time that EU or EP needed to be removed or added back to the base coverage, it was not correctly updating the HB option coverage. The System was requiring the HB option coverage to be marked complete twice before properly adding or removing EU.

The mark complete logic that determines if EU or EP applies to a coverage has been updated to always determine if the base coverage qualifies for EU/EP first and then move on to determining if the HB option coverage qualifies. This will ensure that only one mark complete will be required to properly determine if EU/EP applies when both coverages are marked complete at the same time.

Fast Edit AR & PR: During internal testing of the Fast Edit PR and Fast Edit AR, an issue with the Previous Year Procedure Code field in the Detail Line Drawer was identified. When a user keyed a Procedure Code to a detail line in either the Fast Edit PR or Fast Edit AR grid, the System was persisting this value to the Previous Year Procedure Code field in the Detail Line Drawer. The issue was occurring when adding a Procedure Code to an existing detail line and when creating a new detail line in one of the Fast Edit pages.

A fix has been implemented for this issue. When a Procedure Code is keyed to a detail line on the Fast Edit PR or Fast Edit AR, it will no longer persist to the Previous Year Procedure Code field in the Detail Line Drawer.

Fast Edit AR: An issue was found internally where the logic for displaying the Verified Not High Risk checkbox in the Fast Edit AR Detail Line Drawer was not matching the logic for displaying that same checkbox on the Maintain Detail Line page. It was determined that in the Fast Edit AR Detail Line Drawer, the System was only displaying the Verified Not High Risk checkbox if a Primary Land ID was designated. An update has been made to the logic in the Fast Edit AR Detail Line to display the Verified Not High Risk checkbox regardless of whether the Land ID is the "Primary" Land ID on the line.

WFRP: In the 5.100 release with TFS #61452, functionality was implemented to have the System update the MPCI Liability field on a related WFRP policy when the MPCI policy Acreage Report was keyed and the coverages marked complete. A bug was reported with this functionality where the System determined MPCI Liability on the WFRP policy was not matching the liability on the MPCI detail lines or Schedule of Insurance form on select WFRP policies. The logic that determines and sets the MPCI Liability value on WFRP policies was updated to use the same logic that determines liability for MPCI detail lines and the Schedule of Insurance form.

Fast Edit: For the Fast Edit functionality, a request was made to add a Save & Next button when editing Private Product detail lines through the Edit Premium Line page that is accessed via the line number link in the Details tab of a policy.

With this ticket, a Save & Next option is now available when editing Private Product policies. This will allow the user to access the line # via link, make updates through the Edit Premium Line page, and then click Save & Next to go to the next detail line on the policy for editing/updating.

NOTE: Not all products are supported through the Fast Edit grid at this time. This new button will allow the users to move between detail lines without having to exit through the policy page for Hail, Production Hail, and Named Peril policies. This will not be available when creating a new policy (standalone).