Release Notes 9.055.0

Perennial Combo Form: MCT was made aware that the Record Type for the most recent year was not printing on the Perennial Combo form's Production / Acreage Reporting page. For all years, the Record Type field on the Perennial Combo form's Production / Acreage Reporting page has been updated to print the Record Type for the most recent year, if present, in the APH database.

An enhancement request was received asking to add a new Livestock Policy Management Dashboard (Livestock > Policy Management Dashboard) to the System. The purpose of the dashboard is to allow the user to view, sort, and filter all of their Livestock policies. This also provides users with enhanced navigation through their Livestock policies to view, add, and print forms for the respective policies. TFS #118882 added the new Livestock Policy Management Dashboard for the DRP Plan, and TFS #119528 added the LRP Plan to the Policy Management Dashboard. With this ticket, the LGM Plan has been added to the Policy Management Dashboard.

An enhancement request was received regarding the Claim icon popup on the new Livestock Policy Management Dashboard (Livestock > Policy Management Dashboard). Previously, if a Claim icon appeared, the popup only displayed the word "Claim". The request received was to build out that popup to include claim details like the Claim icon popup on MPCI policies currently displays. This information includes:

List of MPCI Claims

Claim Number (Date Paid) - Claim Status - $ Amount Paid

With this ticket, the wording in the Claim icon popup was updated to display information similar to the MPCI display with the only exception being the wording on the top line:

Livestock Claims Details

Claim Number (Date Paid) - Claim Status - $ Amount Paid

This change is applicable for all three plans on the Policy Management Dashboard.

NOTE: Only claim details for the applicable premium line will be displayed in the popup.

For MPCI and WFRP policies, there are two places an agent is stored. The first is the agent that is stored in the policy table and the second is the agent of record that is stored in the coverage table. The agent can be changed on the Grower tab of the policy. The agent of record, on the other hand, can only be changed via the Signature Maintenance page or via the signature maintenance functionality of the Fast Edit pages (for MPCI) or on the Income & Expense record (for WFRP). However, Livestock does not currently use a Signature Maintenance page, so there was previously no place to update the agent of record on Livestock policies.

With this ticket, a field for the selection of an Agent of Record has been added for DRP premium lines for the 2021+ RYs. The agent selected on the DRP premium line UI will be stored in the new AgentofRecordOID field in the LivestockPremiumLine table upon save of the DRP detail line. This field will be placed to the left of the signature dates. The label will be "Agent of Record", and the selection list will be populated with names of agents associated with the agency, defaulting to the agent assigned with the policy. Only active agents for the current RY and agents associated with the policy's agency will display in this dropdown. Users will be able to change the agent selection as necessary. A script will also be run to set the Agent of Record for any previously established premium lines prior to this ticket. The script will set the Agent of Record on those premium lines to match the agent on the policy.

TFS #119528 added the LRP Plan to the new Policy Management Dashboard (Livestock > Policy Management Dashboard). During the UAT process, an enhancement request was received to change the navigation for when a user clicks on the + icon for the premium lines displayed. Previously, the System would take the user to the Add New Detail Line page; however, the end date for the new premium line the user is wanting to add may not always be under the same Practice. A decision was made to update the navigation for the + icon to take the user to the Coverages tab of the applicable policy rather than the Add New Detail Line page. With this new navigation, the user can determine if a coverage with the applicable practice already exists for the new premium line or if they must first add the new coverage prior to adding the premium line.

A Delete (trash can) icon was added to the buttons below the unit group grid. When selected, if the highlighted unit is a temporary unit group, the System will disassociate fields, delete PORs associated with the unit group, and remove the unit group from the Unit Group grid. When selected, if the highlighted unit group is a server/AR Unit Group, the System will display a message indicating that the unit group will only be deleted from Mapping, and premium lines will need to be deleted from the AR separately (with the OK option to continue or the Cancel option to stop the process), disassociate fields, delete PORs associated with the unit group, and remove the unit group from the Unit Group grid.

NOTE: If a user selects the Reload icon to refresh the Unit Group grid without deleting the premium lines from the AR, the unit group will be reloaded to the Unit Group selection list.

Users reported that after syncing (when updating intervals that included a different first interval), fields would no longer be linked and duplicate planting records would be created on the next use of the PRF Wizard. Since Unit Groups are associated with the first interval premium line, changing the OIDs was orphaning the fields. This ticket updated the logic to ensure those fields do not get orphaned.

Users reported various issues with newly created unit groups and the "Haying" type option getting a "No Intervals Available" message. These issues have been corrected.

With the additional access allowed by mobile applications and grower portals, additional security was needed around the Tools > CIMS Results menu in order to limit access. This has been implemented.

Annual Forage: During testing of TFS #12151, inconsistencies were identified in the validation of insurable and insured acres between Annual Forage and PRF. The logic on save of a PRF detail line verifies insured acres are = or < the insurable acres or a hard stop error is returned, requiring a user to make a correction. Although Annual Forage is also a Plan 13 crop, the System was not performing a similar validation of acres entered at save. There was also a small UI display error around formatting of the acres field in the Acreage Details section of the page. The acres should have been formatted with a comma to be consistent with other formatting for acre fields.

The System was updated to incorporate a hard stop validation IF the sum of the Acreage Details section's Insured Acres is greater than the Insurable acres entered on the detail line. The hard stop validation will display the following error message: "The Insured Acres cannot be greater than the Insurable Acres". The formatting of the acre field has also been corrected.

Forage Seeding: For the 2021+ RYs, Forage Seeding (0032) will now have a Fall and Spring SCD. With TFS #118790, the System was updated to allow the following functionality for this crop:

According to the ADMs, the Practice is what distinguishes a Fall or Spring planting season for this crop, so it was initially thought that only a Spring practice code needed to be captured instead of the type code which is captured for most crops when this functionality is applied. However, after the changes in TFS #118790 were deployed, the RMA confirmed that both the Type and Practice are needed (see info from the 09-03-2020 PASS Status Report).

With this ticket, the System was updated to capture a Type in addition to the Spring Practice whenever a new application is received after the initial Fall SCD or coverage is changed for Spring which requires a Late Processed Flag of "06".

Perennials: While some internal testing was done for Perennial crops, a gap was identified where additional edits were needed for the PAW. Certain data elements within the PAW are needed and required in order for the System to calculate density and the percent of stand. These values being left blank or entered as 0 impacts the System correctly calculating these values. The System was updated with the needed PAW validations and will now require block #, plant/set out date, spacing (only first 2 fields of spacing), and # of trees/plants at save of a PAW grid.

WFRP: For the 2021+ RYs, the RMA has issued a new Commodity Code of "0606" for WFRP policies. This commodity will be used to report "Other Combined Direct Marketing" commodities. When this commodity is applied to a policy, the calculation of Total Qualifying Commodities is impacted. RMA has updated this calculation so that Other Combined Direct Marketing Commodities are not included when determining total commodities or total expected revenue for purposes of the Qualifying Revenue Threshold (also referred to as the Minimum Qualifying Amount) calculation only. This Qualifying Revenue Threshold represents an interim step in the Total Qualifying Commodities calculation. In addition, the RMA added a new step to the Total Qualifying Commodities calculation where 2 additional commodities are added at the end of the calculation if Other Combined Direct Marketing Commodities are on the policy. Finally, the calculation of expected revenue for Other Combined Direct Marketing Commodities works a bit different than other commodities. Since this commodity will include two or more direct marketing commodities, a yield is not required and is therefore not included in the calculation of expected revenue.

To account for the new Other Combined Direct Marketing Commodity, the following System Changes have been made: