Release Notes 6.050.0

NLF: It was identified that No Longer Farming (NLF) units were not printing at the end of the coverage on the Production Report like they do on other forms. The NLF print option was updated to only display for the pre-filled report styles. The sort order for the Crop Summary and Detail Line was also updated to match the Fast Edit PR pages, which prints NLF units at the end of the coverage. If NLF units are elected to be printed, the units are listed after all non-NLF units for the coverage in the same unit # / type / practice sort order for the coverage.

This ticket added the NLF print option to the base Production Report / Acreage Report and updated the form with the following base form standards. These changes are for all years:

eSign: The 765PR Production Report by Unit form has been modified and enabled for use within the eSign Wizard. For this form, the eSign Wizard will:

eSign: The 765QPR Production Report Worksheet by Unit form has been modified and enabled for use within the eSign Wizard. For this form, the eSign Wizard will:

eSign: Previously, the grower Electronic Consent Form attachment was being attached as a policy-Level attachment within the policy being signed. This has been fixed. The grower Electronic Consent Form is now being attached at the grower level and is therefore visible from all of a grower's policies. The System was also checked to migrate any grower Electronic Consent Forms previously attached at the policy level so they could be re-attached at the grower level.

eSign: The following updates were made to the eSign Wizard:

An issue was found on the Potential Loss Estimator Worksheet where a red Telerik error was printing in the Assignment of Indemnity field if an Assignment of Indemnity (AOI) had an ampersand (&) in the Creditor's name. This issue has been resolved.

The Potential Loss Estimator Worksheet is available for Plan Codes RP (02) and RPHPE (03) only. Agents can use this form to estimate what the final Harvest Price will be when the form is printed in order to give the grower an idea of what a potential revenue loss could be.

NOTE: TFS #80837 (also in this release) updated the Trigger Loss and Harvest Price fields for units with RPHPE plans.

It was found that the Potential Loss Estimator Worksheet was not printing the Harvest Price and calculating the Trigger Yield for units with the RPHPE Plan. The following updates have been made to the form:

The Potential Loss Estimator Worksheet is available for Plan Codes RP (02) and RPHPE (03) only. Agents can use this form to estimate what the final Harvest Price will be when the form is printed in order to give the grower an idea of what a potential revenue loss could be.

NOTE: TFS #80837 (also in this release) updated the AOI field to accept an ampersand in the AOI name instead of printing a red Telerik error in the AOI field.

Livestock: Additional Attachment Types were added for Livestock as required. With this ticket, the following additional Attachment Types were added under the Livestock heading:

Livestock: An issue was identified in the 6.045 release on the LGM Dairy Cattle Application where, if no detail lines existed, the "Hundredweight of Milk" Type was being displayed on all three lines instead of Hundredweight of Milk, Tons of Corn, Tons of Protein Meal. With this ticket, the LGM Dairy Cattle Application was updated as follows:

NOTE: The Detail Line page displays "Tons of Soybean Meal" instead of "Tons of Protein Meal" as the System is matching the Livestock Handbook for the LGM Dairy Cattle Application.

Livestock: The following issues were identified on LGM Applications:

The LGM Applications were updated to print the correct SBI Share and to print the Policy State.

NOTE: The Detail Line page displays "Tons of Soybean Meal" instead of "Tons of Protein Meal" so that the LGM Dairy Cattle Application matches the Livestock Handbook.

Livestock: The following updates were made to the LGM Dairy Cattle Schedule of Insurance (SOI) form for all years:

Livestock: The following updates were made to the LRP Schedule of Insurance (SOI) form:

Livestock: Users now have the ability to print the Schedule of Insurance (SOI) for Livestock Gross Margin (LGM) for Cattle insurance policies. With this ticket, the new form, Livestock Gross Margin (LGM) for Cattle Schedule of Insurance, was added to the Livestock Print tab in an individual Livestock policy and displays in the System as "Livestock Gross Margin (LGM) Schedule of Insurance – Cattle".

NOTE: TFS #81906 will fix an issue when there are multiple counties on the policy with the same insurance period, the form is printing them all on one SOI instead of separating them out. This ticket will implement a fix so separate SOIs print in that scenario.

Livestock: Users now have the ability to print the Schedule of Insurance (SOI) for Livestock Gross Margin (LGM) for Swine insurance policies. With this ticket, the new form, Livestock Gross Margin (LGM) for Swine Schedule of Insurance, was added to the Livestock Print tab in an individual Livestock policy and displays in the System as “Livestock Gross Margin (LGM) Schedule of Insurance – Swine”:

NOTE: TFS #81754 will fix an issue where, when there are coverages in different insurance periods, the Totals fields for Number of Head and Expected Gross Margin per Month for one of the coverages is populating on the SOI for the other Insurance Period. TFS #81906 will fix an issue where, when there are multiple counties on the policy with the same insurance period, the form is printing them all on one SOI instead of separating them out. This ticket will implement a fix so separate SOIs print in that scenario.

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

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

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

An update has been made to the Plant Date field on the Plant panel and the Fast Edit Planting panel to accept additional date formats. Prior to this change, the System only accepted a date that was formatted as DD/MM/YYYY. The System will now handle these additional date formats, which are the same patterns accepted on the Fast Edit AR/PR pages for MPCI policies:

Margin Protection: The Margin Protection Whitepaper issued by RMA in May 2017 established a requirement for a P26 record on stand-alone margin protection policies. The System has been updated to allow Production Reporting for MP coverages for the 2017+ RYs via Fast Edit PR. All functionality for Production Reporting for stand-alone MP (Plan 16) and 2018+ RYs stand-alone MP (Plan 17) will mirror existing functionality for Production Reporting of ARPI and stand-alone STAX in regards to access, navigation, lockouts, validations, save, and Signature Maintenance.

A request was received to add attachment types for WFRP Farm Operation Reports, one for Revised and one for Final. With this ticket, two new attachments types have been added:

Perennials: An update was made to the 2018 CIH to the definition of "qualify" for Yield Exclusion for Perennial crops and for how YE is applied when Yield Variance is triggered and the Approved Yield is adjusted for High Variability. Refer to the 2018 CIH: 1862 APH Database Test for High Variability of Actual Yields, A. Testing Requirements (pages 390-391): "Qualify means it is in the actuarial documents as a crop year that the producer could elect for YE (the producer does not have to elect YE, but the crop year must be YE eligible)."

The System logic has been updated as follows:

A. Yield Variance Test - The System will run the standard Variability and RO Exception test (TFS #32967) on all applicable APH databases.

Cherries: In 2018, new Tart and Sweet Cherry Handbooks were released by RMA. Additional clarification was made surrounding paragraph 1503 (Types of Yields) from the CIH. It states that if an Annual Price was used to calculate a producer's individual year annual revenue for unsold or partially sold harvested production, and the revenue amount was not used for an indemnity claim, that the Temporary Yield Descriptor of "J" is used. For the 2018+ RYs, the "J" Temporary Yield Descriptor will be allowed for Cherries. For Processing Type Cherries (112 and 416), the "J" Yield Descriptor Type is valid for two years (CY = 9 and 10). For Fresh Type Cherries, the "J" Yield Descriptor Type is valid for one year only (CY = 10). (This is standard procedure for all other commodities.)

Fast Edit AR: A bug was identified internally during testing where the validation error that requires a SubCounty (Map Area) was not being triggered on an HR-ACE coverage. When the HR-ACE (HB) Option functionality was first implemented, logic was put in place to require the Dual Coverage flag to be selected on the HR-ACE coverage. A validation on the detail line was also implemented that requires a SubCounty Code (Map Area) to exist if:

The requirement to set the Dual Coverage flag was later removed as this flag is only applicable to CAT coverages - CAT level coverages for high-risk land excluded (HRLE) from an Additional Level Coverage. Because the Dual Coverage flag is not being set on HR-ACE (HB) coverages, the SubCounty validation is no longer triggering.

The System logic for the HR-ACE SubCounty validation has been updated as follows:

Fast Edit AR: In the Fast Edit AR grid, a warning message will be displayed if 2 detail lines within the same unit series (e.g., 0001-000 and 0001-00001) have different shares entered. This is a warning only and will allow users to Save and Save & Exit without making changes, but it is intended to alert a user to a possible entry error while still within the Fast Edit AR grid.

In a recent release, a change was made around how the message was displayed on the page. During the UAT cycle, the ticket was failed because the System didn't display the message and allowed a user to save a basic unit (created using the "Add New Unit" feature) within an optional unit number series. This spin-off ticket was created and the functionality went back to development. After additional research and testing, it was determined there is a difference between the validations when adding a detail line inside and outside of the Fast Edit AR grid.

When adding a detail line on a coverage, if a user keyed a detail line with a unit number of 0001-0000 in a 0100-series of optional unit numbers, the System would respond with up to 2 different warnings. The first error would be that basic and optional unit numbers could not exist within the same unit series. Also, depending upon the share percentage keyed on the new detail line, a warning may have been returned saying share percentages could not be different. Since these are warnings only, a user is able to save through and continue. RMA has validations in PASS that will reject a line with different unit structures within the same unit series, but it is possible for detail lines within a unit series to have different shares. The intent of the warnings is just to cause the user to take a second look at the data keyed.

In the Fast Edit AR grid, the only validation in place is around the share on the lines within a unit series. There is no validation today around a basic and optional unit being added within the same series. A spin-off enhancement has been created to add this validation to the grid in the future.

NOTE: TFS #80995 has been opened to address the validation that is in place on the Legacy APH but not on the Fast Edit AR Grid in reference to a basic and optional unit being added within the same series.

Perennials: A bug was identified internally where the "AY" Yield Type was not being set when applicable. Any time YA is elected on the coverage and a yield within the APH is less than 60% of the T-Yield but does not qualify for YA substitution, the Yield Type must be set to "AY". This functionality was not working for Perennial APH databases with an APH Override set, Commingled checkbox selected, or RO UG applied.

The System logic has been updated for the Perennial APH (Plans 90, 47, and 41) to remove the YA checkbox and set the Yield Type as "AY" if the Annual Yield qualifies for YA but is not allowed. This logic is applicable to situations listed in the 2018 CIH Section 3, Paragraph 1545 C. (2) YA is not applicable to Category C APH when:

NOTE: There is a known issue with the AY Yield Type not applying when the APH Override is "RO Perennial Exception". This issue will be addressed in a later release with TFS #81721.

If the Commingled checkbox is removed or APH Override is removed/changed, upon save, the "AY" will be removed and the YA checkbox will be selected if Yield(s) become eligible.

NOTE: There are known issues with the Commingled checkbox that will be fixed with TFS #81721. If the Commingled checkbox is selected, the YA is correctly being removed but if 1) the year has a claim indicator or 2) the APH CUP is applied, the "AY" Yield Type is not being applied.

Perennials: An issue was found internally while testing PAW functionality. When using the "Update All PAWs on Coverage" via the Additional Functions menu on the View Detail Lines page, the System was not displaying the secondary questions when applicable. The System has been updated so when the "Update All PAWs on Coverage" is selected:

SCO: A small issue with the premium calculation on SCO lines with a very small liability was reported. The issue was reported on a policy where the base policy had an 85% Coverage Level so the SCO coverage was just 1%. This resulted in $1 of liability on the SCO child lines. Given this, the System was calculating $0 in premium for these lines. However, RMA is expecting $1 in premium as well as $1 in liability. The SCO premium calculation has been updated to calculate a minimum of $1 in premium.

SCO: An issue was reported where the System was not calculating premium on SCO child lines for Hybrid Rice Seed policies. This issue has been resolved, and the System is now calculating premium on SCO child lines for Hybrid Rice Seed policies.

An update has been made to ensure that when rolling a policy from one year to the next, if the process determines that there is a need to cancel the new year policy, then the appropriate dates are set to allow for display of the "- Cancelled" indicator on the View Policies grid.