Release Notes 6.100.0

An issue was reported where a "C" was not printing on the 3rd APH database for the years that had a claim on the APH / AR page of the MPCI Perennial Combo Form. This was corrected.

Beginning in 2018 for crops with a contract change date of 11/30 or later and in 2019 for all crops, RMA has converted the Yield Cup procedures to a new "YC" option code. The grower has the ability to opt out of using the Yield Cup on an APH. This ticket implemented "Yield Cup Opt Out?" functionality on the Schedule of Insurance (SOI) / Production Report so the grower can indicate on the form that they are opting out of using the Yield Cup on this APH, which will then be keyed into the System by the agent. The updates for the SOI / Production Report are applicable for all years since the System will determine when YC can be elected on the coverage. New YC verbiage as well as a "YC Opt Out?" checkbox were added and will display at the bottom of the Total Production field if the "YC" option is elected on the coverage. The YC checkbox will always be unselected. The version date was updated to "04-2018".

An error was generated when a user attempted to print the Claim Folder or Notice of Loss when the insured intention was set to "Replant". This ticket has fixed this error.

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:

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

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

Many of the existing validations from the legacy Add New APH page were put in place as part of the original Add New APH Drawer ticket. However, during internal testing of the Add New APH Drawer, it was identified that a few validations that existed on the legacy Add New APH page were missing from the Add New APH Drawer. With this ticket, the following validations were added to the Add New APH Drawer:

APH: When a new APH is created and the user selects an override of Added Land – Simple Average or New Crop P/T, the System displays a series of popups asking about cropland acreage limitations. The user’s selections on these popups are then used to determine if either the simple average t-yield applies or the variable t-yields apply to the new APH.

Given that an APH can now be created through Fast Edit AR, this functionality also needed to be added to the preliminary save logic. This includes preliminary save of both the Legacy Add New APH and the Add New APH Drawer.

The preliminary save logic of the Legacy Add New APH page and the Add New APH Drawer has been updated to include the cropland acreage limitation popups for the Added Land – Simple Average and New Crop P/T overrides. In addition, a more user-friendly format will be implemented for the existing popups.

Contracts: In the Contracts Information grid on the Coverages tab, there is a column for Contracted Value. This field is tied to the Contracted Bushels/Contracted Pounds/Contracted Tons/Contract CWT (exact label depends on the crop) field on the actual contract.

During internal testing of some new Hybrid Sweet Corn Seed functionality, it was found that the current "Contracted Value" label could easily get confused with the Contract Value field on Hybrid Sweet Corn Seed contracts. These labels were so closely worded that it was causing confusion on which value should be displaying on the Contracts grid.

Given this, it was decided to update the "Contracted Value" label in the Contracts grid on the coverages tab to "Contracted UOM", short for unit of measure. This label allows the field to still account for the various values (bushels, pounds, ton or CWT) that could exist in the field while eliminating confusion with the "Contract Value" on Hybrid Sweet Corn Seed contracts.

Coverage: The procedures for the new Yield Cup (YC) option state that the YC option should not be applied to Cotton Seed (SE) child lines. During internal testing of the YC functionality, it was found that the System was applying the YC option to SE child lines. The YC logic has been updated to no longer apply the YC option to SE child lines.

Fast Edit AR: In the 6.090 release with TFS #66994, functionality was added to allow users to create a new APH from within Fast Edit AR. During internal QA testing of this functionality, a gap was found in the logic when a child line was created for a detail line and an APH was subsequently created. In this scenario, the System was not correctly associating the new APH with the child line. The Add New APH logic in Fast Edit AR has been updated so that the newly created APH gets associated with both the parent and child lines.

Quote: By design, lockout logic does not apply to MPCI quotes. The one exception to this is when an agent user attempts to convert a quote to a policy and the lockout date for the Sales Closing Date has passed. A bug was reported where agent users were not able to edit the APH of MPCI quotes if the production/acreage reporting lockout date had passed. The APH lockout logic has been updated to no longer apply to MPCI Quotes.

Grower: A request was received for a new field to allow users to enter the state of incorporation for growers with an Entity Type of "Corporation" or "LLC". With this ticket, a new field, "State of Incorporation", was added to the Grower pages. This field will only display when the grower’s Entity Type is "Corporation" or "LLC". This field has been added to the Grower page accessed by searching for a grower as well as the grower pages accessed from within a policy.

NOTE: TFS #86855 has been set up to map this new field to forms.

Grower: A request was received to add a flag for Limited English Proficiency on the Grower page. In addition, users wanted the ability to manually key a language if this flag was set.

With this ticket, a new flag for Limited English Proficiency was added to the Grower page. In addition, a text field for Preferred Language was added that allows users to manually key in the language spoken by the grower. This new field will display on the Grower page accessed by searching for a grower as well as on the grower pages accessed from within a policy.

Fast Edit: When a user was using Fast Edit for an Annual Hail policy, the Fast Edit page was not accepting the application 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 it.

An enhancement was made to be able to convert a stand-alone policy to be a continuous policy or vice versa.

NOTE: TFS #88176 has been set up to address an issue where the plan of insurance is not being updated on the Confirmation of Coverage.

An update was made to the Insured Intention field to add "Destroy" and "Other" as Insured Intentions for the Private Product Notice of Loss in addition to the existing choices for Replant and Harvest.

ICE: Increased Coverage Election policies currently have 5 policy options available—4 of which use the Liability Factor (BR, CR, CY, and BY). Users were receiving an invalid error on the AY option stating the Liability Factor is required, though this is the one ICE option that does not account for this factor. This issue has been fixed. Now, when the user keys an ICE policy with the AY option, they will no longer receive the validation error message, "Liability Factor is required", upon submitting coverage, as that is not a valid field for this option.

NOTE: This does not occur upon initial creation of the first ICE AY coverage. This occurs if you have left the Coverage page, return to it (or the policy/quote), and try to add a second coverage to the ICE AY option policy.

When adding a supplemental replant policy, the System was allowing users to add coverages for crops that were not available for the Supplemental Replant product. An update was made to look at the crop first to make sure it is available for the product. Originally, it was looking at a coverage detail on the MPCI policy and if the detail line did not contain any detail line information; now, it looks at the crop first to determine coverage.

Coverage: An update has been made to ensure that NLF lines on the MPCI coverage do not stop the remainder of the lines from being submitted to the Private Products side via mark complete or submit of acres processing. Testers had noticed if one or more lines were marked as "No Longer Farming", they were not bringing over any lines for that coverage. This has been corrected.

When a user was converting a quote to the next step, either a binder/policy, it was not taking into account the liability on the line, so once converted, the policy was over the liability max. When the user was converting a quote to a binder or policy, the System was not looking at the Total Liability for the County, Township, and Range and including lines on the quote with the same location to determine if it will go over the liability limit. With the enhancement, once the user tries to take the quote to the next step, they will receive a popup stating that they cannot continue.