Release Notes 7.025.0

The Claim Summary page has been updated to give users the option to add additional crop or detail lines to an existing Notice of Loss (NOL) if it's in a specific status. The Edit NOL button will only be visible if the claim is in one of the following statuses: "Open", "Open-Corrected", "Assigned to Adjuster", or "Assigned to Supervisor".

A Special Provisions update was made available from the RMA on 4/20/2018 with updates for Annual Forage (0332) with RI (13) plan. The file was downloaded and implemented into the System.

During the UAT testing for the 7.005 release, it was found that, when a user selected crops in the Filtering Options AND entered policies in the Policy to Batch field in the Batch Printing tool (Tools > Batch Printing), all crops on the policies were printing instead of just the crops selected in the Filtering Options. The Batch Printing tool has been updated in the following way to resolve this issue:

During internal testing of TFS #91986 in the 7.011.1 release, it was found that the Farm Name data, when it went to a second line, printed on top of the Legal Description label and data on the Acreage Report. The Acreage Report has been updated so the Farm Name will no longer print on top of the Legal Description when the Farm Name prints to a second line.

Previously, the premium and liability were not printing on the Schedule of Insurance (SOI) premium lines for standalone STAX coverages, but the premium and liability were printing in the Premium Summary for these coverages. The SOI and SOI / Production Report have been updated to print the premium and liability on the premium lines for standalone STAX coverages.

A new column, "Effective Date", has been added to the end of the Private Product Confirmation of Coverage (COC) form. This ticket did not update the COC for any Watts products.

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

A new release notes notification has been added to the Help button (?) in the header of the System. Now, whenever a new release that has accompanying release notes in the help site is released, the Help button in the header will turn red. When a user clicks on the button, the background of the button will revert to the default gray and the user will see a red option, "New Release Notes Available!", in the dropdown. Clicking this option will take the user to a new browser tab with the current release notes page in the help site. In the System, once the user navigates away from the page on which they clicked the red Help button, the Help button will remain gray, and the "New Release Notes Available!" option in the Help button dropdown will revert to "Release Notes" until the next release with accompanying release notes in the help site is released. If they do not click the red Help button at all, it will remain red.

When doing internal testing, it was found that users had the option to add a new Livestock policy for a prospective insured. Prospective insureds should only have the option to add quotes in that dropdown, not policies. With this ticket, the "Add Livestock Policy" option has been removed from the dropdown for prospective growers.

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

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

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

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

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

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

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

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

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

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

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

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

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

A 2019 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 the RMA and has been implemented in the System. The following table has been updated for 2019:

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

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

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

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

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

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

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

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

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

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

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

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

Land IDs: The original intention of the Land ID popup was to have the Land IDs sort first by FSN, then Tract, and finally S/T/R. A bug was recently reported with this sort order where the System was sorting by the first digit of the number only. For example, if there were three Land IDs with FSN 5287 and Tracts 1, 10, and 8, the System would sort them as:

These should have been sorted as:

With this ticket, the sort order of Land IDs in the Land ID popup was updated to sort in ascending order: first by FSN, then tract, and finally S/T/R. This sort order will now consider all digits of the number.

NOTE: Any leading zeros will be ignored. For example, "0476" will be sorted as "476".

Quotes: Agents often use a quote to establish data in the System for prospective insureds prior to a Sales Closing Date. Once the required paperwork is received to trigger a policy, an agency user may then convert a quote to a policy. During the conversion process, the System performs validations around data accuracy and completeness. Using the "Prospective" status for the grower and SBI allows an agent to pre-key policy and coverage information without the need to enter a TIN, which is often not secured until the finalized application.

The scope of this ticket was to add the Is Prospective SBI checkbox to an SBI record, allowing a user to postpone entry of a TIN until the convert to policy process is triggered. The Is Prospective SBI checkbox has been placed on the page near the TIN entry field so users can select this to bypass validations on save.

Guarantee Adjustment Factors: The RMA has two different ICE/ADM tables from which guarantee adjustment factors for prevented planting and late planting are pulled. ICE D00068 Guarantee Adjustment is currently used to look up guarantee adjustment factors for all late planting adjustments. In addition, ICE D00068 Guarantee Adjustment is also used to look up adjustment factors for prevented planting on Written Agreements only. When a Written Agreement does not apply, ADM A01220 is used to determine prevented planting guarantee adjustment factors.

In the July PASS production release, RMA made an update to replace ICE D00068 with ADM A01220 for prevented planting guarantee adjustment factors on Written Agreements for 2019+ RYs. This means all guarantee adjustment lookups for prevented planting will use ADM A01220, regardless of whether there is a Written Agreement, and all late planting guarantee adjustment lookups will use ICE D00068.

With this ticket, the guarantee adjustment lookup was updated to account for the RMA’s change in the July PASS release. ADM A01220 will now be used for all prevented planting guarantee adjustment lookups, regardless of whether a Written Agreement applies or not.

Fast Edit CLU: The Fast Edit CLU page was introduced for processing with the 2018 Spring ARD. When deployed, the page used the standard browser tabbing sequence, which essentially tabbed through each field on the grid line, including the checkbox, sub field, refresh icon, PP indicator, AR dropdown, and so on. The scope of this ticket was to introduce a more refined tabbing sequence to the page.

A user is required to click on the first field of the tabbing sequence to set the cursor. With tab, the sequence will be invoked to tab to crop, coverage, premium line, acres, plant date, and then the sequence begins again. Similar to the Fast Edit AR, when the tabbing sequence is broken by placement of the cursor on any other field on the page, the user may resume the sequence by tabbing to the next field that would be part of the sequence.

NOTE: The tabbing sequence does not include the Fast Plant fields at the top of the page.

Margin Protection: Beginning in the 2019 RY, RMA has updated the Margin Protection policy to state that the base coverage cannot be CAT. System functionality that allows users to associate a Margin Protection coverage with a base MPCI coverage has been updated to no longer allow a base coverage with a CAT coverage level to be associated with a Margin Protection coverage. In order to account for this change, the following System updates have been implemented:

Fast Edit CLU: The Fast Edit CLU page was introduced for processing for the 2018 Spring ARD. This page allows a user to duplicate a field line to process split planting (e.g., half of a field to one crop and half of a field to another crop). When using the duplicate icon on the Fast Edit CLU page, the System wasn't defaulting the duplicated line to a modified state. Although there are no known instances of issues or processing concerns resulting from this during the Spring ARD cycle, the intent for the duplicate feature was to place the line in a defaulted "modified" state since this state ensures the line is handled properly during Save, Save & Continue, or Save & Exit from the page.

Underwriting Report: TFS #31550 & #82108 added the ability to correctly update MPCI Detail Lines with Insurable Acres from the Underwriting Report page (Detail Lines tab > View/Add Underwriting Report from the Additional Functions dropdown) to avoid having to key acres twice. The updating of Uninsurable Acres was intentionally left out of the scope of that ticket due to the complexity of how those lines would need to be updated. This ticket provides the ability to include Uninsurable Acres when updating Acres on MPCI Detail Lines from the Underwriting Report page.

NOTE: The Underwriting Report page is applicable to the following crops: Alfalfa Seed (0107), Forage Production (0033), Grass Seed (0102), and Mint (0034)

The System was updated and will now allow a user to update detail lines with both Insurable and Uninsurable Acre values from the Underwriting Report. At save of the Underwriting Report page, an Apply Acreage popup will appear with a summary of Insurable and Uninsurable Acres for each unit keyed within the Underwriting Report. Users will be allowed to update standard detail lines with these values. If a unit within the summary grid reflects an Insurable and Uninsurable value, the existing detail line will be updated with the Insurable acre value and a child line will be created and updated with the Uninsurable acre value along with the following uninsurable reason code: "S - Uninsurable".

Although these changes are being stood up to support 2019+ RY processing, they will be applicable to all RYs. Also, due to the complexity of parent/child line relationships that can occur when a unit has an Insurable and Uninsurable acre value applied, updating acres from the Underwriting Report to the MPCI Detail Lines is intended to support the initial update of acres to MPCI Detail Line. Updating MPCI Detail Line acres from the Underwriting Report page for any subsequent changes is not recommended as it could cause unwanted child lines to be created. Should this happen, users will need to manually adjust the MPCI Detail Lines.

Known issues that will be considered with TFS #93797 in a future release:

Fresh Market Beans: During some internal testing, a bug related to SA T-Yields was identified. Per the CIH, SA T-Yields do not apply to Fresh Market Beans; however, the System was allowing SA T-Yields be applied on Fresh Market Beans.

The System has been updated to no longer allow SA T-Yields on Fresh Market Beans. This includes removing the APH Overrides of "Added Land – Simple Average" and "New Crop P/T" from the APH page when the crop is Fresh Market Beans as well as removing the "Apply Current Year SA T-Yields" option from the Additional Functions dropdown for Fresh Market Beans.

Prevented Planting: The prevented planting (PP) options of "PF" and "PT" are historically not applicable for Native Sod (NS) and New Breaking (NB) acreage. However, the RMA has recently added an exception that allows the "PF" or "PT" option to apply to NS and NB acreage but only if the NS/NB acreage is less than 5% of total acres. If the "PF" or "PT" option is transmitted on a P11 record, designated as NS/NB, and acres are 5% or more of total acres, then the RMA will reject the record.

When elected on the coverage, the System automatically sets the PF/PT options on the detail line in read-only format with the exception of detail lines designated as NS/NB. Currently, for NB/NS detail lines, the System does not apply the PP options, even if elected on the coverage. Given this new 5% exception, the System was updated to allow users to manually apply the PF/PT options to NS/NB detail lines. In addition, a warning message on the Legacy Maintain Detail Line page and a warning validation on the Fast Edit AR was added to notify users of the scenario when PF/PT can be applied to NB/NS detail lines.

With this ticket, the following changes have been made:

a. This applies only when a New Breaking (N) or Native Sod (D) procedure code has been applied to the detail line and PF/PT is elected on the coverage.

b. If an "N" or "D" procedure code has not been applied, the options will continue to be read-only options applied by the System.

a. This warning will display directly on the page on the Legacy Maintain Detail Line as soon as the user selects to apply PF/PT to the detail line.

b. On the Fast Edit AR, this will be a warning type validation that will display when validate or save is selected.

Fast Edit PR: By design, the Fast Edit PR grid for ARPI/STAX/Margin Protection only pulls a coverage into the grid if ALL detail lines for the coverage have AR sign dates applied. Also, by design, the System does not apply AR sign dates to units flagged as no longer farming (NLF). The combination of these two designs caused a bug where the System was not pulling coverages into the Fast Edit PR grid for ARPI/STAX/Margin Protection if one or more units was marked as NLF.

The Fast Edit PR grid for ARPI/STAX/Margin Protection has been updated to no longer consider NLF units when determining if all detail lines have AR sign dates applied. The System will now pull coverages into the grid so long as all lines have AR sign dates, excluding any NLF units.

Mark Complete: A bug was reported where the Mark Complete process was not completing on certain policies. Development research found that this issue was occurring when the PTY option was elected on the coverage AND one or more detail lines did not have an APH. The Mark Complete process was updated to allow the process to complete when the PTY option is elected on the coverage and one or more detail lines are missing an APH.

Rainfall Index: Under Rainfall Index plans of insurance—such as PRF, Apiculture, and Annual Forage—growers elect up to five intervals to insure during the year (e.g., Jan-Feb, Mar-Apr). During the course of the year, the number of insurable acres may change on these policies as land is sold, planted to another crop, etc. Claims on these types of policies are paid based on the insurable acres during the insured interval; however, the premium is still owed on the full acreage amount at the beginning of the policy year. For this reason, users need the ability to track both total original acres as well as reduced acres for claims purposes.

On the Plan 13 detail line page, the System previously provided the ability to key reduced acres for claims purposes; however, there can be up to five revisions in a given year, so a request was received to add additional fields to allow for multiple revisions. In addition, the effective date for each revision needed to be tracked.

With this ticket, an Add button was added next to the Reduced Acres and Effective Date fields for Plan 13 detail lines. When selected, the System will add an additional revision line. A total of up to 5 revision lines will be allowed. The System will require the reduced acres for each revision to be less than the previous revision with the exception of the first revision line, which can be equal to insured acres. In addition, the effective date must be later than the effective date on the previous line.

Fast Edit AR: Internal testing identified a bug with the Use BU checkbox on the Fast Edit AR grid. By design, the checkbox is read-only on the Fast Edit AR grid but editable within the APH drawer. The bug identified was that the checkbox in the grid was always displaying as un-selected, even if it was selected in the detail line drawer. The Use BU checkbox on the Fast Edit AR grid has been updated to display as selected if it was selected in the detail line drawer.

Conservation Compliance: When a grower, SBI, and/or Transfer of Right to an Indemnity (TOR) are out of compliance, a subsidy reduction applies. System functionality was designed to require an AIP Approval Date before applying the subsidy reduction. This date is applied on the Grower tab of the policy regardless of whether it is the grower or an SBI/TOR that is out of compliance. In addition, the applicable subsidy reduction displays on the Grower tab when the grower and/or an SBI are out of compliance. When a TOR is out of compliance, since the reduction applies to only detail lines the TOR is listed as a shareholder on, the subsidy reduction does not display on the Grower tab and instead displays directly on each applicable detail line.

An issue was reported where a TOR was out of compliance but the System was not applying a subsidy reduction. The issue was traced to a missing AIP Approval Date; however, the AIP Approval Date field was not displaying on the Grower tab so a date could not be entered. The field was designed to only display when either the grower and/or an SBI/TOR was out of compliance, but it was not displaying when an SBI/TOR only was marked as out of compliance.

With this ticket, the Conservation Compliance AIP Approval Date was updated to display when either the grower and/or an SBI/TOR is marked as out of compliance.

Margin Protection: A "Sorry..." error was being returned for a very specific policy scenario when the user selected "Recreate Margin Protection Lines" from the Additional Functions dropdown. When selected, the System first deletes all MP lines and then rebuilds them based on information on the related MPCI detail lines and RMA procedures. However, in the specific policy receiving the error, a TOR existed on one of the lines and resulted in an exception error as the delete process was being completed. This has been resolved.

When the user was setting up an linked Private Product policy and entered in the date as either 00/00/0000 or without slashes (for example, 00000000), the System created the linked Private Product policy without an application date.

A correction was made to the creation of linked Private Product policies from the MPCI side. The user must enter a valid application date when creating the linked Private Product policy. The System will no longer accept "00/00/0000" or a date without slashes as a date when creating the policy.