Release Notes 11.055.0

1/31 CCD SPOIs were updated and made available from RMA on Jan 25, 2022. The Special Provisions for 2022 have been implemented in the System.

Batch Printing: Batch Printing functionality creates multiple PDF documents by design. When a user triggers a batch printing job, the System scoops up the first 300 policies in the first PDF and then spins off subsequent PDF documents for the next 300 policies, the next 300 policies after that, etc. The larger the batch print scope is, the more PDF files are created. A report was recently received of an agent having a batch print job of APH databases stop working after several hours of it being processing. In review, it was found that the first 300 policies contained almost 4500 pages because of the form being printed and the number of coverages and detail lines on the policy. With some forms—like the APH database—printing 2 APHs per page, the number of pages included with the batch print jobs has increased.

The scope of the change made to the System with this ticket impacted the APH Database and the Production Report. These 2 forms display the APH history in a very similar manner. Rather than build individual PDF batches with 300 policies, this change will reduce that to 100 policies at a time. This will add some efficiency to batch printing, allowing the batch jobs to finish earlier, but it will also create more PDF documents at the end of the batch process.

For all CYs, the MPCI policy Print tab and Batch Printing tool (Tools > Batch Printing) have been updated in the following ways:

RMA released Pecan Tree Crop Provisions for the 2023 CY/2021 RY. The Pecan Tree Crop Provisions (Pecan Tree Crop Provisions, Pecan Tree Insurance Comprehensive Tree Value [CTV] Endorsement) that will be effective for the 2023 CY have been implemented.

SOI: The Schedule of Insurance (SOI) that prints for the WFRP format has been updated to include printing Micro Farm.

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

This ticket added Sync From AR logs similar to the Sync To AR logs that were previously added.

Users requested that the Print functionality be updated to not require users to scroll to the right to close the print window. This update was made to the print popup for the selected report/form, and user will be able to close and then select a different report to open for printing.

Annual Forage: An issue was reported where, on an Annual Forage policy, the System was correctly displaying the rounded acre value but was not saving that same rounded acre value to the database when a value of hundredths was originally keyed. In return, this was causing P11 errors on the policy with RMA. The System has been updated to fix the rounding issue that was occurring when creating a new detail line and an original acre value was keyed to the hundredths. Within the Add New Detail Line page, the Insured Acres field in the Acreage Details section is now correctly rounding the acres value as expected.

Companion Policy: An issue was found internally where users were able to delete Policy Shareholders from the "Manage Policy Shareholders" link on the Utilities tab of an MPCI policy when the Shareholder had companion links associated with at least one detail line. While the developer was researching, they found a few other places where similar logic needed to be put in place and/or updated. With this ticket, the following changes have been made to the pages/areas listed below:

Coverages: It was determined that the Coverage grid on the Coverage tab of MPCI policies wasn't always sorting coverage records based on System specs. This was happening when a related STAX coverage existed on the policy. In the prior RY, the STAX coverage displayed below the base MPCI coverage; however, after the policy rolled to 2022, the STAX coverage was displaying above the base MPCI coverage. The correct sort order for this grid should be:

It was determined that the incorrect sort order was due to the special characters that display after some coverages. For example, an asterisk (*) to depict fund designation or (#) to depict new producer. The System logic has been updated to ignore these special characters.

Grower Wizard: Internal testing found some instances where saving changes processed through the Grower Wizard returned a "Sorry..." error. This incorrect handling of a NULL reference has been resolved.

PACE: Beginning in the 2022 RY, for Non Irrigated Grain Corn with an 03/15 Sales Closing Date, the Post - Application Coverage Endorsement (PACE) will be available according to the actuarial documents for certain States/Counties. From a System perspective, PACE will be similar to current SCO functionality. This ticket implemented the following detail line changes necessary to support PACE:

NOTE: Since PACE coverage is based on a post application window (in the ADMs) by Plant Date, it's important that users create separate premium lines by the "Date Planting Completed" date on the PACE Acreage Reporting form.

PACE: For Post-Application Coverage Endorsement (PACE), the Coverage page was updated to now display the Pre-Nitrogen Application in a read-only format, and the Post Nitrogen Application will now display as a dropdown. This dropdown will display values from 25-80% in 5% increments. Once the Post Nitrogen Application election has been made, the System will persist the applicable Pre-Nitrogen Application percentage as a read-only display. The Pre and Post Nitrogen Application values will equal 100%.

NOTE: Due to this ticket being in the 11.055 release, which is set to deploy on 03/03/2022, and the fact that applications may have already been processed by Agent/AIPs, after deployment of this ticket, the System will remove any invalid percentages in the DB and update the dropdown on the page to "Select". The Agent/AIP will have to go back and manually correct these coverages.

PACE: The System was updated in order to implement the rating logic from the M13 PASS Calculation Exhibit P11_17 Plan 26 27 28 Premium Calculations for PACE child lines. Included with those changes, the admin fee logic was also implemented where a separate $30 admin fee will apply when PACE has been elected.

Perennials: An enhancement was requested to increase the display on the PAW page to accommodate the full display of a planting pattern that is carried out beyond the decimal point within the pattern fields. This has been implemented.

Perennials: In TFS #61532, functionality was introduced for a new pilot program for Pecan Trees for the 2017 RY/2018 CY. Under the scope of that ticket the Restoration Method field was added to the Coverage page; Stages I - V were applicable, and the Range Class was based on the Restoration Method on the Coverage and the Stage.

For the 2022 RY/2023 CY, RMA has removed the 2 Restoration Methods and replaced them with a single tree reference price for each stage. The System has been updated for the 2022+ RYs in order to account for changes to the current Pecan Tree (0284) functionality per the RMA White Paper. The following changes were implemented:

Perennials: The System has been updated for the 2022+ RYs for the FL Fruit Tree PAW logic and validations to fix a typographical error in the CIH that impacted the tree age calculation. The following Stage Validations will now apply for Florida Fruit Trees (Plan 40) (Avocado Trees [0212], Grapefruit Trees [0208], Lemon Trees [0209], Lime Trees [0210], Mango Trees [0214], Orange Trees [0207], and All Other Citrus Trees [0211]; however, not Carambola Trees, as they were not a part of the typo):

PRH: It was determined that the Liability calculation within the Production Revenue History (PRH) rating logic was not always rounding up to the correct whole number. Only 1 premium line was impacted by this in 2021, and a manual premium override was applied to fix the value. The fix in this ticket will prevent the need to use the premium override in the future.

With this ticket, the PRH rating logic was updated to round the Liability value to the correct whole number based on RMA P21, 22, 23 Premium Calculation specs.

PRH: The logic that determines and sums the Production and Acre values from APH records has been updated to populate the correct values in the upper and lower Production & Revenue grids for Buyer Type records that are accessible via the Revenue History tab on Production Revenue History (PRH) policies. These changes include adjustments to exclude Production and Acre values from NLF units.

The values that are summed are taken from each APH record that has the same Personal Projected Price Group Code (from ICE D00179). These codes are based on the Crop, Cropping Practice, and Organic Practice for each unit. (Cropping Practice and Organic Practice codes can be determined by the Type/Practice on RMA's Actuarial Browser site.) For example, a Type of NTS (997) with a Practice of Winter Planted IRR (211) has a Cropping Practice of 211 and an Organic Practice of 997. The 211 Cropping Practice and 997 Organic Practice has a Personal Projected Price Group Code of 003 in the ICE Table for Strawberries (0154).

Once summed at this level, the values are applied to all Buyer Type records reflecting the same Personal Projected Price Group Code.

NOTE: Different Buyer Type Records may or may not have the same Personal Projected Price Group Code.

WFRP (Plan 76): For Plan 76 Coverages only (WFRP and Micro Farm), when the RC Option is elected and a Prior Year Tax ID value has been keyed, the Prior Year Tax ID field will now display as a masked number on the Maintain Coverage page. The full Tax ID number will display upon hovering over or clicking on the field. The field will also still be editable should it ever need to be updated for any reason (as long as it's not past the standard SCD lockout).

WFRP Micro Farm (9110): An issue was discovered internally through QA testing that dealt with the "Beginning Date" and "Ending Date" fields for Early & Late Fiscal Year Filers for Plan 76 WFRP. If either of these were selected for the "Tax Year", then these date-picker fields persisted. A validation around the "Beginning Date" and auto-populate logic around the "Ending Date" were missed when implementing Micro Farm (9110). With this ticket, the following issues were addressed:

When a user selects a Tax Year of either Early Fiscal Year or Late Fiscal Year, the System will display date fields for Beginning Date and Ending Date and require the user to enter dates in them. At save, if no Ending Date is entered, the System will auto-populate with a Date that is 1 day prior to the Beginning Date + 1 year. For example, if the Beginning Date = 02-01-2021, the Ending Date will populate with 1-31-2022.

WFRP Micro Farm (9110): During UAT of TFS #133103, it was discovered that Indexing Procedures were being applied incorrectly. A Micro Farm Insured needs to have 5 years of Tax History in order to qualify. The Maintain Income page was using substituted values that make a 5 year history when < 5 years were submitted to qualify for Indexing. A change has been implemented so that 5 years of Tax History are required for Indexing Procedures to apply. Substituted values will now not count towards the 5 year requirement, as expected.

WFRP: A bug was reported where the System was not calculating the Historic Average Revenue correctly on certain policies. This bug was traced back to an issue with the calculation of Historic Average Revenue. Historic Average Revenue should be the higher of:

In reviewing the policy in question, it was found that indexing did not apply and the System was correctly displaying "N/A" in all the various indexed average fields on the page; however, the Historic Average Revenue was set equal to what the Indexed Average Revenue would have been had indexing applied. Given this, the Historic Average Revenue calculation needed to be updated to only consider Indexed Average Revenue in the determination if indexing actually applied. For reference, indexing will only apply if all the following criteria are met:

With this ticket, the Historic Average Revenue calculation was updated to only consider the Indexed Average Revenue in the determination if indexing actually applies.