Release Notes 6.025.0

QR Codes have been added to the bottom-right corner of Private Product Application forms. This change applies to forms printed from the Private Products policy Print Forms tab as well as Batch Reporting (Reports > Private Product Reporting > Batch Report). These codes will also enable the form to auto attach to the policy via the Batch Scanning tool (Tools > Batch Scanning).

NOTE: Page breaking may occur on some forms due to spacing issues with the code.

For Named Peril and Crop Hail policies, a request was received to enable the SOI Printed checkbox on policies once an official Schedule of Insurance (SOI) form is generated/printed for a policy so it can be flagged correctly. With this ticket, a new print option, "Generate Official SOI", was added to the SOI form on the Private Products policy Print Forms tab as well as Batch Reporting (Reports > Private Product Reporting > Batch Report) to allow users to generate/print an official Schedule of Insurance and automatically flag the SOI Printed checkbox on the policy page if it's not already selected (if the checkbox is already selected, the System will not allow you to generate/print another official Schedule of Insurance). These updates are applicable for all Crop Years.

NOTE: TFS #77828 will fix an issue where the SOI for a policy is being pulled into a batch (when using Batch Reporting) when the "SOI Printed" flag has been selected already for the policy.

This ticket updated the Potential Loss Estimator and Potential Loss Estimator Worksheet to meet 2018 DSSH requirements. In addition, this ticket updated the format of the Crop Information section so that County, Crop, Type, and Practice will now print on the detail line, and the format of the Legend was updated so that it meets MyCropTechnologies (MCT) base form standards.

RI & VI Combo Form: This ticket updated the base Rainfall & Vegetation Index Application / Cancel / Transfer / Acreage Reporting Form to match base form standards, meet 2018 DSSH requirements, add Signature Authorization and Agency DBA sections, and remove the Acres option from the calculation options per the PRF handbook (see TFS #61575 in this release).

NOTE: TFS #68198 also updated the RI & VI Combo Form; these updates are from the removal of the VI plan for API per the RMA's July 27th publication (see TFS #68198 for a list of all of the changes).

RI & VI Combo Form: This ticket updated the RI & VI Combo Form with the removal of the VI plan for API with RMA's July 27th publication. For the 2018+ Crop Years, including pre-printing from 2017 for 2018, the Vegetation Index (VI) Disclaimer Statement has been removed from the form; the title on the form was updated to read "Apiculture (API) and Pasture, Rangeland, Forage (PRF) Application / Cancellation / Transfer / Acreage Report Combination Form"; "See Last Page…" in the footer was updated to "See Last Page of API & PRF Combination Form for Required Statements"; and for all years, the title on the Print tab and Batch Printing tool (Tools > Batch Printing) was updated to "Application / Cancellation / Transfer / Acreage Report Combination Form - Apiculture (API) and Pasture, Rangeland, Forage (PRF)".

NOTE: TFS #63893 in this release also updated the RI & VI Combo Form (see TFS #63893 for a list of all of the changes).

A Special Provisions update was made available from RMA. The following Special Provisions files for 2018 have been downloaded to E:\RMA Import\SPOI\2018: 2018_SPOI_0831.zip, 2018_SPOI_0930.zip, and 2018_SPOI_1031.zip.

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

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

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

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

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

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

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

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

PRF: The Percent of Value on PRF detail lines has been updated within the roll code to roll to the new RY at the AIP's request.

PRF: Per the PRF handbook, intervals must be calculated by percent. Previously, PRF detail lines included options to calculate intervals by percent or acres. With this ticket, the option to calculate intervals by acres was removed. In addition, the Acres column was removed from the intervals grid on the Maintain Detail Line page for PRF detail lines as well as from the grid on the Detail Lines tab.

Perennials Roll: Enhancements have been made to the roll of Perennial Category C (Plans 47 and 90) and Category D (Plans 40, 41, and 50) crops for the 2018+ RYs. An AIP Preference, "Perennial CLU/RLU Roll", has been added to the Roll Over Preference table. If selected, any CLU/RLU (Planted Fields) Land ID records that exist for the current RY will roll for the subsequent RY.

If the AIP Preference, "Perennial CLU/RLU Roll", is selected, the System will roll CLU/RLU records for Perennial crops. Fields to roll will include: CLU ID, RLU Flag (database table only, will not display in the UI), RLU ID, CLU/RLU Acres, Reported Acres, and Plant Date.

Coverage: AIPs have been receiving applications for fall coverages for growers that previously had spring-only policies. Previously, when a fall application was received, users had to either add the fall coverage to a new policy/policy number or roll the spring policy prior to ADMs being released, which caused many issues on the policy. Given this, AIPs requested the ability to add a new fall coverage to the same policy number as an existing spring-only policy that has not yet rolled to the current Reinsurance Year (RY) without being required to roll the spring coverages early.

With this ticket, functionality was added to allow users to select a prior-year spring policy/policy number that has not yet rolled to the current RY on which to create a new fall coverage.

To do this, users will select to add a new policy for the grower as if they are creating a brand new policy. Then, on the Add New Policy page, once the State/County/Crop have been entered, the System will run a check for prior-year policies for the grower that have not rolled in the same state as the state selected on the Add New Policy page. If one or more policies are found, a dropdown will display from which the user can select the applicable policy. The user will also have the option to create a brand new policy under a new policy number.

On save of the Add New Policy page, if a prior-year policy is selected, the System will roll the policy (without the spring coverages) to the new RY and attach the newly-created fall coverage to the policy rather than create a new policy. Once spring ADMs are available, the spring coverages will roll and attach to the policy.

Additional Information:

Contracts: An update was made to the logic for rounding Contract Price Election for CAT coverages of Plans 90 and 01 to accommodate the changes made by RMA with CR 100980. The System has been updated to round the Price Election amount "up" for any Contract Price where the fourth decimal value is greater than "0".

RMA released the 2018 Document and Supplemental Standards Handbook (DSSH), and one of the updates to the DSSH was for the Non-Discrimination Statement (NDS)'s "To File a Program Compliant" section. In addition to MPCI Forms, the NDS is also listed on the Non-Discrimination hyperlink that is in the bottom-left corner on the System's web pages. When reviewing this update, MCT decided to add more RMA Statements to this base hyperlink and add some efficiencies. With adding more statements to the hyperlink, the hyperlink label was updated to be more encompassing of all statements (i.e., the label for the "Non-Discrimination" hyperlink was updated to "RMA Statements"). To add some efficiency for future statement updates from RMA, all hyperlinks will now pull from the same location as the forms so updates will be needed in only one location. This is applicable to all Crop Years.

APH: Performance optimization opportunities were identified when Added Land is applied to a Master Yield crop. For the spring 2017 processing season, the Fast Edit AR grid supported the addition of Added Land lines within the grid but the user was still required to navigate to the legacy detail line to create an APH. If a Master Yield had been applied to the coverage, the creation of the new APH caused the System to launch all calculations and validations required when the Master Yield was initially created. When an APH is created at acreage reporting for Added Land, it isn't necessary for the System to perform all of the calculations that it was—an Added Land APH would come in without any history and would just be required to be assigned the approved Master Yield as the Approved Yield. The optimization change made eliminated all of the back-end calculation allowing the APH to be created and saved much quicker than previously.

APH: RMA has announced that the "F" Yield Type will now be allowed in all APH yield years for Tobacco crops. Previously, the "F" Yield Type was used to indicate a classification yield for Tobacco crops and was only allowed in 2004 and prior yield years. RMA has lifted this edit since the "F" Yield Type is now used for RO determined yields. The legacy APH and APH drawer have both been updated to allow the "F" Yield Type in all yield years within the APH.

Fast Edit PR: In Fast Edit PR, the Current Year Production Reporting grid includes an intended read-only display of the APH Drawer and Detail Line Drawer. By design, the Current Year Production Reporting grid allows pre-keying of production and acres for the year acres were insured in, versus having to wait until the APH rolls to the next RY where production and acres can be added directly into the APH or to the APH through the subsequent year Fast Edit PR grid.

Because the Detail Line and APH Drawers are tied back to the current RY's coverage, they should be read only for AIP users and agent users when accessed through the Fast Edit PR's Current Year Production Reporting grid. During internal testing, a way to make these drawer fields change from read only to editable was identified. It was found that the grid type was not set when opening the APH Drawer from the Detail Line Drawer. That was fixed so the System now looks up the grid type and applies the correct read-only format. This is applicable for Current Year Production Reporting within the Fast Edit PR grid only.

Land IDs: A bug was identified in the manner in which the Land ID grid refreshed when the data source for entry of acres was at the CLU level. Users accessing the CLU grid through the detail line Land ID link or the Fast Edit AR grid access the same Land ID modal. If acres were entered at a CLU level and saved and then the user attempted to enter acres on the next line (detail line or Fast Edit AR grid line), the prior CLU fields and data displayed for 3-7 seconds until a refresh occurred. At that time, the new line's CLU data was presented and the user could continue with entry. An adjustment was made to the logic around the refresh of the modal to make the entry more seamless and smooth for the end user.

SBIs: An issue was found during UAT of TFS #73044. When an SBI phone number was keyed in the XXX-XXXXXXX format, a "Sorry..." error was returned at save. It was found that multiple keying combinations would also throw this error. The logic for the phone number fields of SBIs on the Grower tab has been changed to automatically update the phone number to the correct formatting if the user enters 10 digits and has at least one of the two hyphens in the correct placement.

NOTE: The valid phone number formats are as follows: (234) 555-1212, 2345551212, or 234-555-1212.

PAW: An enhancement was made to new PAW questions for the 2018+ RYs. A second part has been added to the question, "Organic: has the acreage been affected by a Prohibited Substance (biological, chemical, or other agent) which results in a change in practice?" The following statement has been added:

Additionally, "cultural" was removed from the second question.

Perennials: Updates have been made to the existing PAW for the 2018+ RYs for Plans 41, 47, 50, and 90 Perennials based on the changes published in the 2018 CIH and DSSH. There will be two versions of the PAW: a base/standard PAW that will be applicable to Category C (Plans 47 and 90) and Category D (Plan 41) Pecan Perennials and a Category D (Plan 50) Florida Citrus PAW. Small differences for the base/standard PAW will be specified for each applicable crop.

Also for the 2018+ RYs, an enhancement has been made to the PAW for Category C and D Perennials (Plans 41, 47, 50, and 90) and to Category D Perennial Trees (Plans 40 & 50) to allow access to the Land ID popup via the PAW for CLU/RLU reporting.

The Stand Date on Cotton was not updating correctly on a child line; this has been corrected.

When marking complete/submitting acres on a linked Private Product policy that had both a parent line and an endorsement line on a coverage for a Crop/County, if that associated MPCI coverage did not have any qualifying acres, the endorsement line on the Private Product policy was causing the display to freeze and appear to not load any detail lines.

If there is a Private Product coverage that has a parent line and a corresponding endorsement (e.g., Basic Hail, Green Snap Endorsement), when marking complete/submitting acres, if the associated MPCI Coverage does not have any qualifying acres, the Private Product policy will leave the Placeholder (Sales Record) info on the policy and display a message that the policy has Non-Qualifying Premium Lines; it will no longer freeze the display during Mark Complete/Submit Acreage.

NOTE: The Non-Qualifying Premium Lines message is existing functionality; this ticket addressed the freezing of the UI in this situation.

Mark Complete: Previously, once an Acreage Report was finalized, Mark Complete on an associated MPCI policy with a Private Product policy would begin once the Processing Status in the Coverages tab showed as "Approved" for all the applicable crops on the policy. ProAg requested an update to this process so they can review the Processing Status at the Detail Line level instead of the Coverage level. This will alleviate suspensions on the MPCI policy from delaying the import of data to the Private Product policy.

Now, ProAg will initiate the import of the associated MPCI Acreage Report data into the Private Product Detail Lines through Mark Complete/Submit Acreage once all Premium Lines in the Acreage Report Detail lines tab show a Processing Status of "Complete".

NOTE: ALL premium lines must show as "Complete" for all crops associated with the Private Product policy.

When users were creating or editing placeholder lines on linked Private Product policies, they were receiving an error message that "Share is Required". The share was defaulting to 100% (as it shows on all placeholder lines) but was not allowing for it to be edited and was not being recognized upon save. Now, when a Private Product policy is in placeholder status, the Share field will not give the user a validation error. The Share is to only be validated once the policy is in finalized state with premium detail lines.