Release Notes 7.100.0

A request was received to update the MPCI and Private Product verbiage on the Authorization of Offset Outstanding Balances form (available from the Print Claim Folder menu and from the MPCI policy Print tab). The Authorization of Offset Outstanding Balances form has been updated with the following changes:

During testing of TFS #97965 in the 7.095 release, some additional enhancements to the CLU Acreage Report Crop Summary's Total Acres to assist the grower with seeing how the acres were reported were identified.

NOTE: This form is not intended to be used for Annual Forage, Pasture, Rangeland, Forage (PRF), Apiculture (API), Category C Crops, Perennial Crops, Plan Code MP (16) associated with a YP or RP coverage, Plan Code MP-HPO (17) associated with a YP or RP coverage, Plan Code STAX-RP (35) associated with a YP or RP coverage, Plan Code STAX-RPHPE (36) associated with a YP or RP coverage, Nursery, or WFRP.

For the 2018+ RYs, the AR CLU form has been updated in the following ways:

It was found that the Policy Declaration page was not printing all of the Options for coverages. With this ticket, the width of the column was widened so there is more room for Options to print. These changes apply for all years.

There are five formats of the Policy Declaration Page (see below). The format that prints is based on the crop.

Beginning in the 2018 RY, RMA added a new procedure that allows growers to elect to exclude acreage damaged by an unavoidable uninsured fire (UUF) or a third party from their APH databases. To qualify for this procedure, the Acreage Report must be modified to indicate the UUF / Third Party Damage procedures apply for the acreage.

NOTE: The requirement to modify the Acreage Report was waived for 2017 acreage.

In the following RY, acreage previously reported as UUF / Third Party Damage is excluded from the APH database. If part of the acreage was damaged by UUF or a third party but additional undamaged production/acres exist, the undamaged production/acreage only will be included in the APH database identified by the new "FA" Yield Type.

For forms that display the APH database, requests were received that the TA yield be displayed when it was being used with the FA yield type. When FA is displayed in the Description column, the Annual TA Yield value will now print in parentheses after it (e.g., FA (181.0)).

When BFR functionality was originally implemented, the procedures indicated the "BF" Yield Type would be used to identify history transferred to a Beginning Farmer Rancher (BFR) and would need to be removed from the APH. Requests were received for forms that show the APH database to display the TA yield when it is being used with the BF Yield Type. When BF is displayed in the Description column, the Annual TA Yield value will now print in parentheses after it (e.g., BF (249.0)).

These changes apply to the following forms:

It was found during UAT for TFS #97611 in the 7.095 release that the four asterisks were not removed from the FSA Farm label on the Raisin and Acreage Report. This ticket removed the four asterisks.

The Livestock Gross Margin (LGM) Schedule of Insurance (SOI) has been updated in the following ways for all years:

NOTE: TFS #102521 has been set up to update the Livestock policy Print tab to no longer display the "Level of Detail" label as well as its associated dropdown for the LRP SOI. This form can only be printed pre-filled, so a selection dropdown is unnecessary. This will be handled in a future release.

The Private Product Confirmation of Coverage forms have been updated to display the Product Type in the title (e.g., Crop Hail Confirmation of Coverage) for all Crop Years.

The Private Product Schedule of Insurance forms have been updated to display the Product Type in the tile (e.g., Crop Hail Schedule of Insurance) for all Crop Years.

A new Underwriting support option is now available and can be accessed via the new Start Co-Browsing Session button found in the System footer. This Co-Browsing feature will send a request for support to a Hudson Crop representative. The 4-digit PIN displayed can be used to correctly identify the user's session for the Hudson Crop representative. Questions about this new feature should be directed to your Hudson Crop representative.

NOTE: This new support option is different and apart from the Help Desk support provided by MyCropTechnologies, LLC.

A 2019 Special Provisions Update was made available from RMA on 2/16/2019. The following Special Provisions for 2019 have been downloaded (2019_SPOI_0131.zip and 2019_SPOI_0228.zip):

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

MCT will begin importing ITS related ICE tables to the baseline ADM_ICE table structure. Once in place, MCT will be able to better leverage the table data within the System. The following ICE files were imported to this table structure:

On 2/19/19, AIPs reported agents were locked out from processing Dairy Revenue premium following the President's Day holiday. Prices released on 2/15/19 should have allowed for processing through 9 a.m. on 2/19/19 because the President's Day holiday is in the ICE table. The only work around was applying the lockout bypass to a user role. This should not have been required because the ICE table reference of 2/19/19 as the business processing end time should have been accounted for. An issue was found with the date that was being used to check against the list of holidays in the ADMs. The date was not being updated correctly when the lockout was pushed due to the lockout date being a weekend day. Logic has been updated to fix this issue.

A new field, Effective Date, has been added to the Livestock Register (Reports > MPCI Reporting > Livestock Register). Users can enter a date range in this field.

It was found that the white Halo outline on printed map labels were very hard to read, especially when the labels were crowded together. A Print Halo checkbox was added to the Grower Information section of the Layers panel to allow the user to indicate if they want to have Halo Effects turned on or off for printing.

Map Books: Two new additional record keeping sheet options have been added for Map Book printing. These two new options were added:

Map Books: Users can now print Map Books from the Batch Printing tool (Tools > Batch Printing). In this tool, Map Books are titled as Map Booklets.

Fast Edit CLU: Users reported that the Select Land ID filter on the Fast Edit CLU page was no longer correctly filtering the view. This has been fixed.

Attachments: In Q4 2018, functionality was added that allows a user to choose to attach a document to other policies with the same grower OID/RY. To do this, when adding an attachment from within a policy, a checkbox is available at the bottom of the Attachment popup that, when selected, prompts the System to display other related policies for the grower to prevent re-work when an attachment is applicable to more than one policy.

In the last couple of releases, the Private Products team adopted the MPCI Attachment format, allowing users to attach multiple attachments at one time and leverage the "related policy" functionality. Code was also introduced to allow the related policies to pull in related Private Product policies to the list for selection. After implementation in the 7.090 release, the Help Desk received a report that a user could select a related MPCI policy on a Private Product policy Attachments tab but the user could NOT select the related Private Product policy on the MPCI policy Attachments tab. The scope of this ticket was to make the final adjustment so that all policies (MPCI and Private Products) display as related coverages regardless of what policy Attachments tab the Attachment popup is triggered from (MPCI or Private products).

A 2019 RY PASS error was reported through the Help Desk, and the bug was related to the unit structure discount factor that was calculated. When all acres of the unit = 0 (i.e., all acres are Prevented Plant), the factor applied should = 1.000. The adjustment was made in the calculation to comply with the PASS P11 exhibit. This change applies to unit structures under BU, EU, and EP unit structure.

Beginning in 2019, users will have the ability to create MP Plus linked Private Product quotes to convert to policies for applicable states/crops. Users will be able to see MP Plus as a selection in eligible states. A sales record will be filled out with the elections they wish to include on the policy, which will include Additional Price and Units Covered from the MP Plus tables. Once a user has created a sales record, upon submit coverage, an MP Plus quote will be created. The AIP will then review the quote to determine if it may be accepted: if accepted, an MP Plus policy will be created; if rejected, one will not be created. On the Policy tab, the user will be able to view the sales record information on the placeholder lines.

SRC: Two states, Mississippi and Arkansas, have a higher rate for the High Risk and FAC practice and should allow all HR and FAC acres to come over regardless of whether there is a Written Agreement attached to the coverage. All other states are to be handled as they were in prior years. The rate determination is to be as follows: Rate determined (either High Risk / FAC rate or normal rate if not HR/FAC on line) * (IPA/100) rounded to 2 decimal places. For example, 6.00 rate determined for Corn in AR at a $50 IPA—rate would be 6.00 * (50/100) = 3.00. The 3.00 rate would be used in the calculation of premium. All rate calculations are done in this way.

When an MPCI policy had a coverage canceled, it is was previously converting the associated Private Products policy to a policy status without any acreage reporting dates being entered. In some cases both crops were canceled; in other cases, only one. If there is still a coverage intact, the policy should still be in binder status. This issue has been resolved.

An enhancement has been made to Private Product policies so that when high risk acres are pulled to the Private Product side for those policies that allow them, an indicator will now display in the Info column for those acres to indicate they're high risk.

An enhancement was made to Increased Coverage Election (ICE) policies to allow for the liability factor to go up to 100%. Additionally, users now have the option of selecting EP or BU as the unit structure on all ICE policies.

An issue was found internally where a user was able to set a future date for the application date on Private Products when setting up a Private Product policy. A correction was made to linked Private Product policies on the application date to only allow the application date to be equal to or less than the current date.

An issue was found where users were not able to add a linked Private Product policy to an MPCI policy. An update was made to correct this issue.