Release Notes 17.115.0

This enhancement was to add a new form from the 2025 Nursery Value Select Handbook to the MPCI Print Menus, Peak Selected Value Report.

Changes that were made:

Updated for 2026+CY...

Requests were received to add full quote/preliminary application (pre-app) functionality for Livestock so that users can key quotes/pre-apps for producers (both prospective and existing/new full producers) to keep pending/prospective business separate from existing business and allow for users to pre-print applications for signatures and attach them to the quote/pre-app.

Changes that were made:

With this ticket, Livestock Pre-Apps/Quotes were implemented in the System. Livestock Pre-Apps/Quotes work like MPCI Quotes in that they allow for a user to key prospective business—whether new, transfer in, etc.—for the current RY or the next RY without having to key live policies or even live growers. These also allowed users to print applications for the current RY or pre-print apps for the next RY.

The Livestock Pre-Apps/Quotes interfaces will mostly mirror those of Livestock Policies (e.g., Livestock policy tabs like Coverages, Detail Lines, Attachments, Print are available).

Livestock Pre-Apps/Quotes were added from the same location as Livestock Policies but by selecting the new ""Add Livestock Pre-App/Quote"" option from the dropdown in the top-right corner of the Policies tab (when in a Livestock policy record or a Grower record) and clicking Go; this new option was available when a user had the existing Policy > Livestock Policy > ""Create"" System Function attached to a role on their user profile. Clicking Go with ""Add Livestock Pre-App/Quote"" selected opened the new Add New Livestock Pre-App/Quote page.

The Add New Livestock Pre-App/Quote page functioned/looked mostly like the Livestock Add New Livestock Policy page. When it first loaded, the user would choose a plan from the Program Type dropdown (just like they would when creating a policy). A user must have had the following existing System Functions attached to a role on their user profile in order to see/be able to select the indicated plan types: For "DRP", Policy > Livestock DRP Policy > "Create"; For "LGM", Policy > Livestock LGM Policy > "Create"; For "LRP", Policy > Livestock LRP Policy > "Create".

Once a plan was selected, additional fields for the pre-app/quote would display. Livestock Pre-Apps/Quotes are available for all Livestock years available in the System. To the right of the Year dropdown, a new field, Preliminary App for Next RY, was available. This field was specific to Livestock Pre-Apps/Quotes, and it should only be selected if the Livestock Pre-App/Quote needed to be rolled to the next RY as a Pre-App/Quote so that it could be converted to a policy in the new RY. Once rolled, the selection in this checkbox was cleared in the new RY, but the Coverage Status selected and the Previous Company and Previous Policy # keyed (if applicable) on the Pre App/Quote in the previous RY was rolled as is to the new RY.

NOTE: Validations that exist for the policy such as agent training requirements, COI sign dates, etc. also existed for Livestock Pre-Apps/Quotes.

Once the Pre-App/Quote was saved/created, the user was taken to the Coverages tab for the record. The user can add additional coverages, delete coverages, edit coverages, add endorsements, add attachments, print forms (including pre-printing applications), add notes, update the grower, etc.

NOTE: The ability to mark coverages complete was not available for Livestock Pre-Apps/Quotes. Additionally, users could add endorsements/detail lines to a Pre-App/Quote, but it's important to note that they might not have been eligible for transmittal to/approval by RMA if their Effective Date's sales window had passed when the Pre-App/Quote was converted to a Policy.

Once a Pre-App/Quote was ready to be converted to a policy, the user could click the Convert to Policy button. The System would check the details in the Pre-App/Quote against validations (see list below) that would result in a policy being created with errors. Some are warnings, but some are hard stops that must be addressed before the Pre-App/Quote could be converted to a policy.

Current validations when converted a Pre-App/Quote to a policy:

Errors (Pre-App/Quote cannot be converted with these):

"This policy's status is '{PolicyStatus}' and it cannot be converted from a Quote to a Policy."

This error was returned if the pre-app/quote was already converted to a policy but the page wasn't updated. It's to make sure a policy can't be converted to a quote. Links to the Policy details for the Quote.

"A valid tax ID number for the grower is required."

This error was returned if the Grower record was missing TaxID. Links to Grower details.

"SBI {SbiName} had a Tax ID Type ({SbiTaxIDType}) and Entity Type ({SbiEntityType}) which was not allowed with the Grower's Tax ID Type ({GrowerTaxIdType}) and Entity Type ({GrowerEntityType})."

Links to SBI View.

(RY 2018 and greater) "Number of SBIs required for grower entity type: {minimumNumSbis}"

This error was returned based on the Grower Tax ID Type and Entity Type. A minimum number of a certain SBI, based on tax id type and entity type, was needed. The max number of minimum of necessary such SBIs was used as the number to check against. Links to Policy Details for Quote.

"Grower {GrowerName} has an Entity Type of ""{GrowerEntityType}"" and that is not allowed."

This error was returned if the Grower entity type code is L or F. Links to Grower details.

"Grower {GrowerName} with an Entity Type of "{GrowerEntityType}" is not allowed to have a Tax ID Type of "{GrowerTaxIDType}.""

Links to Grower Details.

"SBI {SbiName} with an Entity Type of "{SbiEntityType}" is not allowed to have a Tax ID Type of ""{SbiTaxIDType}.""

Links to SBI view.

"An Address is required for the grower {GrowerName}."

This error was returned if a primary address was not set on the grower record. Links to Grower Details.

"A valid City/State/Zip is required for the grower {GrowerName}."

This error was returned if the grower address was not flagged as international and any one of the grower address fields are null or empty. Links to Grower details.

"A valid City/Country is required for the grower {GrowerName}."

This error was returned if the grower address was flagged as international and either of the grower address fields are null or empty.

"An Address is required for the SBI {SBIName}."

This error was returned if a primary address was not set on an sbi record. Links to SBI view.

"A valid City/State/Zip is required for the SBI {SbiName}."

This error was returned if the SBI's address was not flagged as international and any one of the SBI address fields are null or empty. Links to SBI view.

"A valid City is required for the SBI {SbiName}."

This error was returned if the grower address was flagged as international and either of the grower address fields are null or empty. Links to SBI view.

"An issuing company must be selected for Quote # {PolicyNumber}."

This error was returned if the ReinsuranceCompanyCode was null or empty. Links to Policy Details for the Quote.

"An agent must be selected for Quote # {PolicyNumber}."

This error was returned if the AgentOID was 0 on the Policy. Links to Policy Details for the Quote.

""The selected agent no longer exists for Quote # {PolicyNumber}.""

This error was returned if no Agent record was found for the AgentOID. Links to Policy Details for the Quote.

"The selected agent is not active for Quote # {PolicyNumber}."

This error was returned if the Agent was not active. Links to Policy Details for the Quote.

"The Quote cannot be converted into a Policy without having at least one active Coverage. Please check the warnings and errors and make any necessary changes to allow this Quote to become a Policy."

This error was returned if no coverages with an ActiveStatus of "A" existed on the quote. Links to policy details for the quote.

"The Quote cannot be converted into a Policy due to a Policy for this Grower Tax ID (TIN), reinsurance year, state, and insurance plan already existing on another grower record with the same Grower TIN. Please contact your AIP."

This validation was added with DO #216747 to the policy side. This should be looking at all coverages on the existing policies (with the same RY, state, insurance plan) for the Grower records with that TIN to determine the plan type--even if all of the coverages on the policy were canceled. Links to the Policy Details for the Quote.

"The Quote cannot be converted into a Policy due to a Policy for this Grower Tax ID (TIN), reinsurance year, state, and insurance plan already existing for this Grower record. Please contact your AIP."

This error was returned if the grower record the converted Quote was being added when they already had an active policy in the same RY and State for the same plan. This looked at all coverages on the existing policies for the Grower record to determine the plan type—even if all of the coverages on the policy were canceled. Links to the Policy Details for the Quote.

"The Quote cannot be converted into a Policy due to a Policy for this Grower Tax ID (TIN), reinsurance year, state, and insurance plan already existing with an active coverage for this Grower TIN. DRP policies only allow for one coverage per RY/State. Please contact your AIP."

This error was returned for DRP ONLY if an active coverage existed in a policy for the same ry/state/plan as the one that's on the quote when the coverage was DRP. Linked to the applicable coverage details.

"The Quote cannot be converted into a Policy due to a Policy for this Grower Tax ID (TIN), reinsurance year, state, and insurance plan already existing with an active coverage for the same county/commodity for this Grower TIN. Please contact your AIP."

This error was returned for LGM and LRP only if a coverage existed in a policy for the same ry/state/plan/county/commodity as one that's on the quote. Linked to the applicable coverage details.

"A Branch Office Code could not be determined and is required in order to convert a Quote to a Policy. Please notify your AIP contact for assistance."

This error was returned if the BranchOffice was null or empty. Linked to the policy details of the quote.

"The sales window for the below endorsements has passed. They may be ineligible for approval by RMA. Please notify your AIP contact for assistance.

This error was returned for users who did not have a lockout bypass permission on their user profile.

Hard Warnings (Pre-App/Quote can still be converted with these, but it may have resulted in errors or suspensions on policy):

"Warning - A grower record with the same tax ID, entity type and agency has been found for {0}. If you continue with converting this quote to a policy, the policy will be attached to the existing grower record for {1}."

This hard warning was triggered if the System found any other matching Grower record in the database that had non-quote Livestock Policies and uses that Grower record for the converted policy, if one existed. Links to the Grower details for the Grower of the Quote (not the found existing grower).

"The sales window for the below endorsements has passed. They may be ineligible for approval by RMA. Please notify your AIP contact for assistance.

Do you wish to continue with converting this quote to a policy and adding these endorsements to the new policy?"

This error was returned for users who had a bypass lockout permission on their user profile.

Warnings (Pre-App/Quote could still have been converted with these, but it may result in errors or suspensions on policy):

"A valid County must be selected for Coverage {CoverageDescription}"

This warning was returned if the CountyCode was null or empty. Linked to Coverage view.

"A valid Commodity/Crop Name must be selected for Coverage {CoverageDescription}"

This warning was returned if the Commodity abbreviation couldn't be found for the CommodityCode and reinsurance year (i.e., CommodityCode is null or empty). Linked to Coverage view.

"A valid Insurance Plan/Crop Plan must be selected for Coverage {CoverageDescription}"

This warning was returned if the InsurancePlanCode was null or empty. Linked to Coverage view.

"The Insured Signature Date must be after January 1, 1991, for Coverage {CoverageDescription}"

This warning was returned if the ApplicationSignedDate was prior to that date. Linked to Coverage view.

"The Insured Signature Date cannot be after today for Coverage {CoverageDescription}"

This warning was returned if the ApplicationSignedDate was a future date. Linked to Coverage view.

"The Agent Signature Date must be after January 1, 1991, for Coverage {CoverageDescription}"

This warning was returned if the AgentSignDate was prior to that date. Linked to Coverage view.

"The Agent Signature Date cannot be after today for Coverage {CoverageDescription}"

This warning was returned if the AgentSignDate was a future date. Linked to Coverage view.

"Coverage {CoverageDescription} flagged as suspended due to the preceding issues."

This warning was returned if any of the errors/warnings were resulting in a coverage suspension on the policy. Linked to Coverage view.

NOTE: DO #215675 will implement M13 imports for Livestock policies. These will be imported as Livestock Pre-Apps/Quotes.

The ability to Automap from Policy Land IDs was added.

Changes that were made:

This ticket ensured that Automapping by FSN/Tract functioned properly.

Request for System Function: Attachments Tab's New Drag & Drop Functionality.

Changes that were made:

This System Preference controlled the in-page drag-and-drop upload functionality. This was originally implemented as part of the Required Documents projects with 200086 but was split into its own preference so that it can be turned on regardless of whether the Required Documents functionality was turned on for Livestock and/or MPCI. When enabled (set to “True”), this feature replaced the legacy popup’s drag-and-drop upload that was included with the base functionality and instead allowed users to upload attachment via an in-page drag-and-drop. Once dragged-and-dropped into the provided space, the System prompted the user for attachment details similar to the legacy popup.