Release Notes 7.000.0

A request was received that SC claims (Self Cert Replants and Simplified Finals) be highlighted in the Claims & Inspections Register to make them stand out more for users. This change has been implemented, and SC claims will now be highlighted in purple in the Results grid of the register when a search is run that includes an SC claim.

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

An issue was found where the Production Report was only printing the "MASTER UNIT" indicator for automatically-created Master Yield units (Code = MA); it was not printing the indicator for manually-created Master Yield units (Code = MM). This issue has been resolved. The "MASTER UNIT" indicator will now print for both automatically- and manually-created Master Yield units.

A Special Provisions update was made available from RMA on 4/11/2018 with updates for the below plans/crops. SPOI PDFs are dated 3/27/2018. The file was downloaded and implemented in the System.

A request was received to no longer display the New Breaking Acreage Insurability Request Form on the Print menus since the form is now obsolete with New Breaking being included with the Request for Actuarial Change Form. The New Breaking Acreage Insurability Request Form is no longer displayed on the Print menus for all years.

Previously, the Schedule of Insurance (SOI) and SOI / Production Report were receiving a red Telerik error message in the Signature Authorization field if the Grantee, Authorized Rep, or Power of Attorney (POA) had an ampersand in the name. This was corrected.

An issue was found on Hail Applications where the detail line was not printing the acres but instead leaving this area blank. The logic was updated to print the acres on the detail line.

The PARFlex Schedule of Insurance was printing a tail on the bottom of the grid; this has been corrected.

When printing PriceFlexPrime and PAR blank SOI forms (Tools > Print Private Product Blank Forms > Print Schedule of Insurance for PAR and PriceFlexPrime), they were printing with errors. A correction was made so that when printing the PriceFlexPrime and PAR Blank forms for SOI, an error no longer occurs.

When printing the Batch Reports for Private Products, even if the user wasn't selecting the "Print Premium Line with No Acres"option, it was still printing lines with no acres. A correction was made to the Batch Report for Private Products so that no acre lines only print when the option is selected.

A new dropdown, Product Type, has been added to the Outstanding Balance Report (Reports > Private Products Reporting > Private Products Outstanding Balance Report).

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

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:

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 2019 update was made by 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:

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 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 table has been updated for 2015:

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 table has been updated for 2016:

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 table has been updated for 2017:

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 2019 update was made by RMA and has been implemented in the System. The following tables have been updated for 2019:

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

An enhancement has been made to the Fast Plant panel to allow a user to indicate if a field is Prevented Plant (PP) and if the plant date falls within the Late Planting period. When this occurs, the panel will show the determined percent reduction.

NOTE: This ticket will allow the PP/LP changes to be saved in mapping, but the data will not sync to the AR. That functionality is being added in the 7.005 release with TFS #69417.

During testing of TFS #85589 in the 6.095.0 release, while testing a fix for a rating issue when a STAX WA existed, an AIP determined that the Variable T-Yields within the APH database on the related/base MPCI premium line were being wiped out on the unit if a written agreement was attached. This spin-off ticket was created to resolve this issue, which was caused by the code using the STAX premium line to calculate the APH rather than the related/base MPCI premium line. The System was updated to no longer use the STAX premium line to update the APH on the related/base MPCI premium line.

Attachments: Current System functionality for attaching documents to a policy includes batch scanning. Using the Attachments tab, users were only able to attach one document/file at a time. In an effort to provide a workflow improvement, this functionality was updated to allow users to attach multiple files at one time from the Attachments tab of a policy. This can be done by clicking Add Attachments on the Attachments tab of the policy, and then when the Select file(s) to attach popup opens, clicking Browse. Then, in the Open popup, selecting multiple files by pressing CTRL on your keyboard while selecting files with your mouse. Or, you can drag and drop files into the Select file(s) to attach popup. This new functionality will allow up to 10 files to be attached at one time. However, the total combined size of all files included in a single upload cannot exceed 50 MB. The grid within the attachments popup has been updated to allow users to assign Attachment Types and descriptions to all files selected.

Margin Protection: During internal testing of the new auto-creation of Margin Protection (MP) detail lines, an issue was found as it relates to Enterprise Units, both EU and EP. Per the Margin Protection white paper, MP detail lines must have the same unit structure as the base coverage detail lines. Given this, the auto-create MP detail lines functionality was designed to use the unit structure from the base coverage detail lines that existed at the time the MP detail lines were created. However, validation for EU/EP occurs at mark complete, which can result in the unit structure changing on the base coverage detail lines after the MP detail lines have already been created. Furthermore, there are overrides available to AIP users on the coverage that allow the AIP to override the System’s EU/EP determination which, again, can result in a change in the unit structure on the base coverage detail lines after the MP detail lines have already been created.

Given all this, users needed a way to update the unit structure on the MP detail lines following their creation and after the base coverage unit structure has changed. To accomplish this, a process was added to the mark complete functionality. This process will occur after MP detail lines have been created and after EU/EP validation logic has been applied to the base coverage detail lines. Then, the unit structure on the base coverage detail lines will be compared to the unit structure on the MP detail lines. If the unit structure does not match, then the System will update the unit structure on the MP detail lines to match the base coverage detail line unit structure. This will account for scenarios where the System changes the base coverage unit structure during mark complete, as well as when a user applies an override that changes the unit structure. Users will simply need to ensure mark complete is processed following application of any overrides. In addition, logic was added that will mark the MP coverage complete when the user selects to mark the base coverage complete on the Fast Edit AR Signature Maintenance page.

NOTE: During internal testing, a small bug with the application of the AR sign dates to the Margin Protection detail lines was identified. If the Margin Protection and base coverages are on separate policies, the System correctly creates the MP detail lines but does not apply the sign dates. A TFS ticket will be set up to address this issue. In the meantime, as a workaround, users can manually apply signature dates to the Margin Protection detail lines on the Signature Maintenance page.

Peanuts: The new weighted average price (WAP) calculations for 2018+ Peanuts that were added with the 6.115 release under TFS #88808/88809 did not include the capping of the WAP at the maximum contract price published in the ADM for the RY/State/County/Crop/Plan/Type. For the 2018+ RYs, if the WAP exceeds the maximum contract price published in the ADM, it will cap the contract price as the maximum contract price allowed for the RY/State/County/Crop/Plan/Type. Additional adjustments to the WAP calculations are expected with TFS #90115 in a later release.

Annual Forage: During internal testing of the Annual Forage functionality, it was found that there was not a validation in place to limit the percent of value to the minimum/maximum values contained in the special provisions.

A warning message has been added to the coverage pages for Annual Forage. If the user keys a value less than the minimum or greater than the maximum percent of value allowed for the state/county/interval, a warning message will display. The System will use the maximum acreage percent and minimum acreage percent values from the Price ADM table to determine the min/max values.

Coverages: In the 6.110 release with TFS #84498, a new database field and coverage indicator was added to flag coverages with more than one SCD. As part of this functionality a "^" will display next to the crop name on the Coverages tab for any coverages with more than one SCD. In addition, this symbol and a description of "Multiple SCDs" were added to the legend that displays below the coverages grid. These changes were implemented for the 2017+ RYs. While testing did confirm setting of the flag as implemented for the 2017+ RYs, the new "^" symbol and description were found to be displaying in the legend in prior years. With this ticket, the legend was updated to only display the multiple SCD indicator ("^") and description in the legend for the 2017+ RYs.

Fast Edit AR: During internal Fast Edit AR testing, a bug was identified where the System was not saving duplicated lines for Cotton with a Skip Row practice. The duplicate line functionality in Fast Edit AR has been updated, and duplicated child lines are now saved for Cotton with a Skip Row practice.

Peanuts: It was determined that the updated 2018 Peanut contract calculations that were deployed in the 6.115 release with TFS #88808 were not completely accurate. The necessary changes to fix the issue required additional RMA clarification, which resulted in an overhaul of the original calculations.

For the 2018+ RYs, the System will now determine the correct Peanut contract price to use at a Policy/Type level in the following scenarios:

When Non-Contracted pounds exist, the ADM price must be included with the Weighted Average Price (WAP calc). Non-Contracted pounds are determined by subtracting the Total Contracted Pounds from each Contract Record on the Policy for the same Type from the sum of the Total Guarantee for each unit with the same Type for all coverages on a policy. If the value is greater than zero, that value is considered to be the Non-Contracted pounds value.

NOTE: Some RMA calculations are based on a Grower and Type level. This means that information on all Peanut coverages for the Grower and Type must be considered. Due to the complexity of crossing policies to determine the correct peanut contract price along with the expected low volume of this specific scenario, System functionality will only use values at a Policy and Type level.

SA T-Yields: While researching Added Land and New Crop/P/T functionality, MCT identified that some actual yield types were not being included in the SA T-yield calculation logic. In determining whether an APH should be included in the SA T-yield calculation, the System identifies whether the APH has at least 1 actual/assigned yield in the base period. If it does, its approved yield (or adjusted yield if TA, YE, or YC apply) is used in the calculation. The System was only considering yield descriptors of "A" and "BF" to be actual yields. The CIH identifies several yield descriptors to be considered as "actual yields". This ticket simply considers these additional yield descriptors as "actual yields" in the determination of whether they should be used in the SA T-yield calculation.

This ticket added the following Yield Descriptors to the logic of whether an APH qualifies to be included in the scope of the SA Tyield calculation: "AY", "FA", "NA", "PA", "PR", and "DA". For assigned yields, "P" only will be considered. (SA T-yields don’t apply to Perennial crops.)

NOTE: There is an additional ticket planned for the calculation of the SA T-yield for policies when area plans (plan codes 04, 05, 06) are converted to a CCIP plan code. This ticket will be in the 7.005 release. Those scenarios are NOT covered under the scope of this ticket—this ticket merely identified what yield descriptors are considered actual / assigned yields. This is not changed functionality but, rather, the correction of a gap in the Added Land and New Crop/P/T logic that has existed for several years.

STAX & Margin Protection: When STAX or Margin Protection coverages are written in conjunction with an underlying MPCI base coverage, the user must properly link the 2 coverages together through the user interface. The linkage is accomplished by selection of the Related Coverage checkbox and the selection of the related MPCI coverage from a dropdown. During testing, it was determined that a "Sorry..." error was returned if a user saved a coverage when the Related Coverage checkbox was set but no base coverage selection was made. This same error occurred if STAX/MP detail lines were recreated through the Additional Functions dropdown if the base and STAX or MP coverages were not linked as necessary.

The scope of this change was to add code that keeps the "Sorry..." error from being thrown to the user interface and to the database when related coverages were not properly linked together. A complete linkage is required; however, when the System auto-creates STAX and/or MP detail lines—or recreates them through the Additional Functions process—the incomplete linkage described in this ticket will prevent the System from creating/re-creating detail lines for STAX and MP, by design. No changes were made to the functionality that auto-creates the detail lines; this ticket merely suppressed an error. If lines are not created on the STAX or MP coverages as expected during acreage reporting, the user must confirm that the linkage is in place as required.

STAX: An issue was reported where the Area Loss Trigger dropdown on STAX coverages with a written agreement was not populating with all available values. The Area Loss Trigger dropdown on STAX coverages with written agreements has been updated to populate with the correct values of 70-90 in 5% increments.

Yield Cup: For 2018, the new Yield Cup procedures applied to crops with an 11/30 or later filing date only. Beginning in 2019, the new Yield Cup procedures apply to all crops for which the YC option is available in the ADMs. When this functionality was implemented in 2018, it was coded to only apply to the 11/30 or later filing date crops. Now, for 2019, all references to the 11/30 filing date needed to be removed. The YC logic has been updated for 2019 to no longer be applied to only 11/30+ filing date crops. YC functionality will now be available on any crop for which the option is available in the ADMs.

NOTE: Testing of this functionality was limited due to limited availability of ADMs. Clary Sage, Potatoes, Sugarbeets in certain state/counties, and cabbage are currently the only crops for which ADMs are available and the YC option is available. TFS #82981 has been set up as a testing only ticket to retest this functionality once 6/30 ADMs are available.

Margin Protection: A request was made to include Margin Protection as an eligible MPCI plan to link with eZ-Hail and Crop Hail private product policies beginning in 2018. This has been implemented.

A request was made for cash binders or policies with placeholders not to default the Fall Due Date for the premium due date. To enable the payment date to be determined based on the payment date rules, this ticket removed the check to select if the lines on the policy are in a placeholder status. The only lines to be excluded will be "cancelled" and "pending" lines.

When a grower elects the EP unit structure on an MPCI policy but only has one practice (IRR or NI) with planted acres at acreage reporting, a 9999-0000 unit is created for the practice that has no planted acres. For Hail and Production Hail, when the user was trying to import acres through mark complete/submit acreage process, this unit was causing the mark complete/submit acreage process to fail. With this ticket, upon using the Mark Complete/Submit Acreage on Continuous Hail and Hail, the System will now ignore the 9999-0000 unit and allow all other qualifying detail lines to import into the policies.

NOTE: A spinoff, TFS #90589, will address all other private products.

Changes needed to be done for the calculation of IPA for optional endorsements that have additional coverage on the Fast Edit page. The System was updated to include validation for IPA limits on optional endorsements and additional coverage endorsement lines on the Fast Edit page.

Additionally, the message received when the IPA is over the limit was updated to read "IPA Limit of 'XXXX' will be exceeded. This will put it at a total of 'XXXXX'. If you are an admin you can override." However, the IPA for an optional endorsement with a limit cannot be overridden past the max limit even if you are an admin (e.g., for Prevented Plant/Replant).