Release Notes 7.010.0

During internal testing, a spelling issue was found on the new popup that displays when the user doesn't select a detail line when filing a Notice of Loss. The word "detail" was displaying as "detaill". This issue has been resolved.

Users reported that an agent was able to create a quote by selecting it on the Add NOL page for a related policy. This issue has been resolved.

During internal discussions, it was found that the amount printing for Margin Protection (MP) Reduction on the Schedule of Insurance (SOI) with TFS #88386 in the 7.005 release was incorrect. The SOI needed to print the actual reduction (MpPreliminaryPremium – TotalPremium). The following updates were made to the SOI:

NOTE: TFS #91278 is adding the net Premium Reduction. This new field is not visible on any of the System pages; currently, the only way to see the value is to check the database.

A question was received on why, when a user selects to print the SOI with the "Print All Land ID's" print option selected, some of the details do not print the Fields IDs. Additionally, when the user deselects the "Print All Land ID's" print option, only 1 of the Field IDs prints, and, if multiple Field IDs exist, the asterisk prints as well. This issue was researched and it was determined that the Field IDs that were not printing was due to a space(s) at the end of the FSN and Tract that caused the land code in the form not to work properly as the form didn't recognize the code. This issue has been resolved for all years. The land code used by the SOI has been updated to remove any extra spaces from the FSN and Tract so that all Field IDs are recognized and printed.

It was reported that the Acreage Report was receiving a Telerik error on blank detail lines. The Acreage Report was updated so that a Telerik error no longer occurs when blank detail lines are printed.

NOTE: TFS #91825 was set up for a future release. During internal testing, it was found that the Shareholder bottom border is not growing when there are more Shareholders than will fit in default field size.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Quotes: An issue was reported where a user received a "Sorry..." error when converting a quote to a policy. Development research determined this error was triggering due to a missing address on the Grower record. While there is logic in place to require an address when creating a grower, the address could later be deleted and the System did not stop the Grower record from being re-saved without an address. A validation has been added to prevent users from deleting grower addresses.

Quotes: In the 6.000 release with TFS #70097, logic was added to the convert quote to policy functionality to check for duplicate growers. The System defines a duplicate grower as having the same tax ID number, grower entity type, and agency. During the convert quote to policy process, if a duplicate grower is found, the System will continue with converting the quote to a policy but will attach the newly-converted policy to the existing Grower record rather than the Grower record the quote was originally created through.

Following release of this functionality, AIPs began to report issues where, following conversion of a quote to a policy, the System was attaching the newly-converted policy to an entirely different Grower record. Additional research found the issue was due to the tax ID number value. For many of the policies in question, the user had not entered a tax ID number but had instead marked the grower as a "prospective grower" in order to bypass the edit requiring a tax ID number. Given this, the tax ID number was NULL in the database. Then when the quote was converted to a policy and the System ran the check for a duplicate grower, it was finding another Grower record with a NULL tax ID and the same entity type and agency and attaching the quote to that Grower record, which was for an entirely different grower. Furthermore, in a few circumstances, it was found that the user had actually been entering a random tax ID number and/or making one up rather than obtaining the grower's actual tax ID number. It also appeared they were re-using the same made up tax ID number. This was also resulting in the System determining a duplicate grower existed and attaching the newly-converted policy to an incorrect Grower record.

In order to prevent the issues described above, the System was updated in the following ways:

A new Attachment Type, "VIP Documents", was added to the MPCI attachment types. This will be considered a permanent document, making it visible in multiple RYs as policies roll forward annually.

Annual Forage: In 2017, RMA made a number of adjustments to the Annual Forage policy. As part of these adjustments, the number of growing seasons was expanded from two to four, with specific plant dates applying to each growing season.

As part of the System changes in 2017, a dropdown was added to the coverage page to allow the user to select a planting season. Part of the dropdown description includes the plant dates applicable to each growing season. At the time this functionality was deployed, RMA had not released any ADM or ICE table referencing the applicable plant dates. Given this, the dates were hard coded. Since then, RMA has added the plant dates applicable to each growing season to ICE D00162. The logic that displays the applicable plant dates in the Growing Season dropdown will now be updated to use this ICE table rather than hard-coded values.

With this ticket, the Growing Season dropdown on Annual Forage coverages was updated to use the plant dates from ICE D00162. The current growing seasons and the applicable plant dates from ICE D00162 are listed below for reference:

Enterprise Units: In the 6.105 release with TFS #88070, functionality was added to account for the RMA's new P11 requirement of an "X" non-premium AR code when EU with LP or EP applies and zero acres exist for one of the irrigation practices. This includes creating a phantom line numbered "9999-0000" (for transmission purposes) if no detail lines currently exist for one of the irrigation practices.

During internal testing, a bug was found where the System was creating multiple phantom lines, instead of just one, when no detail lines existed for the irrigation practice. The logic that creates phantom lines when EU with LP or EP applies and a detail line does not exist for one of the irrigation practices has been updated to no longer create multiple phantom lines. Only one phantom line will be created in this scenario.

Fast Edit AR: When a user entered Acres and a Plant Date on a premium line on the Fast Edit AR page and then went to the detail line drawer and changed the Practice, the System was removing the Acres and Plant Date. When this same process took place on the Fast Edit AR page through the CLU popup, the Acres and Plant Date were not being removed.

The Fast Edit AR page was updated to no longer remove the Acres and Plant Date once the user has updated the Practice from within the detail line drawer.

NOTE: TFS #91535 has been entered to correct a display issue with the Skip Row Pattern on the Fast Edit AR page.

Fast Edit AR: When changing the Practice from "SR (IRR or NIRR)" to just "IRR" or "NIRR" on the Fast Edit AR page, the Planting Pattern was not automatically being updated to "1.00 (solid)" upon save. Subsequently, the user received a hard stop error within the Fast Edit AR page as well as incorrect suspensions. This has been resolved.

If a user changes an SR practice to IRR or NIRR on the Fast Edit AR page, the Planting Pattern will now be updated to a 1.00.

Margin Protection: In the 6.110 release with TFS #76574, System functionality was added to auto-create Margin Protection detail lines when acres are keyed to the related base coverage. As part of this functionality, if the plant date on the base coverage is past the Final Planting Date in the ADMs for the Margin Protection coverage, the System will still create the detail line; however, an uninsurable reason of "U" will be applied.

At the time of the 6.110 release, this late plant functionality could not be tested because the Final Planting Dates for Margin Protection had not yet passed. This ticket was set up as a testing-only ticket to test this functionality; however, during internal testing, it was found to not be working correctly.

With this ticket, the auto-create Margin Protection detail lines were updated to account for the late planted acres. If the plant date is after the Final Planting Date for Margin Protection, the System will apply an uninsurable reason of “U” to the Margin Protection detail lines.

Policy/Quote: An issue was identified where users were receiving a "Sorry..." error when attempting to add a new policy. Development found this "Sorry..." error was triggering because there were no agents associated with the agency selected on the Grower record. In order to prevent this "Sorry..." error, a message was added to the page where new policies are created. If there are no agents associated with the agency record selected for the grower, the message will display notifying the user of the missing agent associations. In addition, the dropdown and button to add new policies will display as grayed out. This will prevent the user from attempting to add a policy before agents have been associated with the agency.

Additional logging was added during mark complete or submit acres. The refresh log was updated with more details as to the reason why a line did not import after mark complete or submit of acreage.

ICE: The Increased Coverage Election was using the rate based on the number of acres on the detail lines. This was an issue when selecting Enterprise Units as this should have rated by the total number of acres for the county/crop instead. An update was made to use the total number of acres for the county/crop selection in ICE if EU is the unit structure to find the proper rate for the detail lines.

High Risk acres were not importing correctly. When imported through the Private Product maintenance table, an Agency Extension was given for High Risk and it was only allowing those lines with a High Risk written agreement policy to import to the Replant policy.

An update was made so that if the High Risk Written Agreement Type is selected for the agency in the Agency Extension of the Private Product maintenance table, it will allow all High Risk Acres to import to the Replant Policy.

NOTE: TFS #91966 has been set up to make an addition to the Agency Extension for High Risk as its own selection in the future.

ICE: When a user was creating an Increased Coverage Election policy, once the policy option was selected, the columns were not updating based on the selection. A correction was made so that when creating an Increased Coverage Election policy, once the user selects a Policy Option in the dropdown, the columns will be updated.

MPowerD: MPowerD gross premium was not displaying on details lines once the acres were submitted. A correction was made to MPowerD policies so that once the acres have been submitted, the Gross Premium column displays a value.