Related
Release Notes 6.075.0
These release notes provide brief descriptions of changes included in AgWorks 6.075.0.
System Updates
Estimator
DESCRIPTION | ID # |
---|---|
Policy Estimates: This ticket added copy down arrows to the following fields on the Detail Lines page of the Policy Estimator: Type, Practice, Acres, Share, Buy-Up Price, Volatility, Rate Yield, App'd Yeld, Adjusted Yield, TA Adjusted, YE Adjusted, YE + TA Adjusted, and YC Adjusted. When a user clicks the copy down arrow on a given field, the value for that field on the first row of the coverage will be copied to all remaining rows within the coverage. |
83818 |
Forms & Reports
DESCRIPTION | ID # | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Production Report / Acreage Report: Beginning in 2018, for crops with a contract change date of 11/30 or later and in 2019 for all crops, RMA is converting the Yield Cup procedures to a new "YC" option code. The grower has the ability to opt out of using the Yield Cup on an APH. This ticket implemented "Yield Cup Opt Out?" functionality on the Production Report / Acreage Report so the grower can indicate on the form that they are opting out of using the Yield Cup on this APH, which will then be keyed into the System by the agent.
These updates are for all years since the System will determine when YC can be elected on the coverage and the Yield Cup (YC) Opt Out? field will only display when YC has been elected on the coverage. NOTE: TFS #84218 will update the Production Report / Acreage Report for when the Skip Row format page is printing so that it doesn't print the right border of the Land in Other County field; currently a right border is printing. |
83478 |
|||||||||||||||||||||||||||||||||||||||
The WFRP Schedule of Insurance (SOI) has been updated with a label update that came from the 2018 WFRP Handbook as well as with a request to print the Commodity Description. These updates are applicable to all years:
|
79926 |
|||||||||||||||||||||||||||||||||||||||
Previously, the Spouse's TIN was not printing unmasked when users selected the Unmask TIN print option. The MPCI Dec Page was updated to unmask the Spouse's TIN when users have selected the Unmask TIN print option. This change applies to all Crop Years. NOTE: The "Display Unmasked Tax IDs" print option is not available on the MPCI Dec Page for all AIPs per their request. |
82166 |
|||||||||||||||||||||||||||||||||||||||
RMA updated the Irrigated Practice Guidelines in the December 21st publication of the 2018 Document and Supplemental Standards Handbook (DSSH). The updates are effective for policies with a contract change date for the 2018 and succeeding Crop Years for crops with a contract change date of November 30, 2017 or later. The Irrigated Practice Guidelines can be printed with the Policy Declaration Page and for 2017+ as a stand-alone form. The Irrigated Practice Guidelines for the 2018 and succeeding Crop Years were updated in the following ways:
NOTE: Notes on the Irrigated Practice Guidelines functionality: (1) The Irrigated Practice Guidelines can be printed with the "Print Official Dec Page for this Policy" print option but will not attach with the "Auto Attach" print option; (2) The Irrigated Practice Guidelines has no QR code on the form; and (3) The Irrigated Practice Guidelines have their own page numbering and will not be included with the Dec Page or other forms.
|
83485 |
|||||||||||||||||||||||||||||||||||||||
Production Report: Beginning in 2018, for crops with a contract change date of 11/30 or later and in 2019 for all crops, RMA is converting the Yield Cup procedures to a new "YC" option code. The grower has the ability to opt out of using the Yield Cup on an APH. This ticket implemented "Yield Cup Opt Out?" functionality on the Production Report so the grower can indicate on the form that they are opting out of using the Yield Cup on this APH, which will then be keyed into the System by the agent. This new checkbox, Yield Cup (YC) Opt Out?, will display to the right of Unit field. The Production Report will only display the Yield Cup (YC) Opt Out? checkbox and the border separating the YC Opt Out and Unit if the "YC" option is elected on the coverage. When the Production Report is being printed in a blank or a pre-headed report style, the Yield Cup (YC) Opt Out? checkbox will not display. When the Production Report is being printed in a pre-filled report style, if the Yield Cup Opt Out? checkbox has been selected for a unit's APH database, then the Yield Cup (YC) Opt Out? checkbox is selected on the Production Report for the applicable unit. NOTE: The version date was not updated since the Production Report version date was updated with TFS #83060 in the 6.070 Release, which was also a January 2018 release. |
83381 |
|||||||||||||||||||||||||||||||||||||||
Production Reporting Worksheet: Beginning in 2018, for crops with a contract change date of 11/30 or later and in 2019 for all crops, RMA is converting the Yield Cup procedures to a new "YC" option code. The grower has the ability to opt out of using the Yield Cup on an APH. This ticket implemented :"Yield Cup (YC) Opt Out?" functionality on the Production Reporting Worksheet so the grower can indicate on the form that they are opting out of using the Yield Cup on this APH, which will then be keyed into the System by the agent. Along with this change, some other clean up was done:
These updates are for all years since the System will determine when YC can be elected on the coverage and the YC Opt Out? field will only display when YC has been elected on the coverage. NOTE: The version date will not be updated since the Production Reporting Worksheet version date was updated with TFS #83532 in the 6.070 Release, which was also a January 2018 release. TFS #84217 will update the Production Reporting Worksheet for when the Crop Summary continues on page 2 so that the Crop Summary's headers will print on page 2. Right now the Crop Summary's headers are not printing. |
83477 |
|||||||||||||||||||||||||||||||||||||||
Beginning in 2018, for crops with a contract change date of 11/30 or later and in 2019 for all crops, RMA is converting the Yield Cup procedures to a new "YC" option code. The grower has the ability to opt out of using the Yield Cup on an APH. This ticket implemented "Yield Cup (YC) Opt Out?" functionality on the APH Database Form so the grower can indicate on the form that they are opting out of using the Yield Cup on this APH, which will then be keyed into the System by the agent.
|
83479 |
|||||||||||||||||||||||||||||||||||||||
APH Database / Acreage Report: Beginning in 2018, for crops with a contract change date of 11/30 or later and in 2019 for all crops, RMA is converting the Yield Cup procedures to a new "YC" option code. The grower has the ability to opt out of using the Yield Cup on an APH. This ticket is implemented "Yield Cup (YC) Opt Out?" functionality on the APH Database / Acreage Report so the grower can indicate on the form that they are opting out of using the Yield Cup on this APH, which will then be keyed into the System by the agent.
NOTE: TFS #84219 will update the APH Database / Acreage Report for when the Crop Summary continues on page 2 so that the sub-header will print on page 2. Right now the sub-header is not printing. |
83480 |
|||||||||||||||||||||||||||||||||||||||
In December 2017, RMA released an updated DSSH for 2018. The Pre-Acceptance Inspection Report (PAIR) was updated with the newly-released 2018 DSSH requirements in the following ways for the 2018+ Crop Years:
|
83483 |
|||||||||||||||||||||||||||||||||||||||
In December 2017, RMA released an updated DSSH for 2018. The Hybrid Seed Yield Request form was updated with the newly-released 2018 DSSH requirements in the following ways:
NOTE: This notice is controlled by an AIP System Preference and will only display for AIPs who have elected to have this System Preference turned on.
|
83484 |
|||||||||||||||||||||||||||||||||||||||
It was reported that SE child lines were printing on Production Reporting forms: the Production Report, Production Reporting Worksheet, and Production Report / Acreage Report. The Production Reporting Worksheet, Production Report, and Production Report / Acreage Report were updated to no longer print SE child lines. On the Production Reporting Worksheet, if the include NLF print option is also selected, the NLF units will also print. These updates are for all years. NOTE: Not all AIPs have the Production Report / Acreage Report form turned on. Also, the include NLF print option does not include NLF units on the Production Reporting Worksheet pages when it is selected with the Production Report / Acreage Report. |
81512 |
|||||||||||||||||||||||||||||||||||||||
The following updates have been made to the Farm History Report page of the WFRP Combo Form for all Crop Years:
NOTE: Once the policy has been saved, any fields that have no data entered on the screen (i.e., have a NULL value) will be saved as "$0.00". Also, only header data will print on the Market Animal and Nursery Inventory Report page; this page will print blank when the WFRP Combo is printed in a blank report style; otherwise, it will print pre-headed with the pre-head and pre-filled report styles. |
84162 |
|||||||||||||||||||||||||||||||||||||||
This ticket cleaned up some items found during testing the 2018 DSSH changes with TFS #75468 in the 6.050 Release. These updates were made to the Production Reporting Worksheet for all years:
|
81728 |
|||||||||||||||||||||||||||||||||||||||
A request was made to modify certain fields on the Price Flex Prime Schedule of Insurance (SOI) form. This enhancement will be for the 2018 and succeeding Crop Years and for Price Flex Prime products only. This change will affect the Schedule of Insurance in all printing areas. The following updates were made to the Price Flex Prime Schedule of Insurance form:
|
82713 |
|||||||||||||||||||||||||||||||||||||||
An AIP requested to have the Private Product Policy Register (Reports > Private Product Reporting > Policy Register), when exported to Excel, split the insured name into two columns: First Name and then Last Name. This update was made. |
81393 |
|||||||||||||||||||||||||||||||||||||||
It was discovered that the Private Product Schedule of Insurance (SOI) form that prints for Watts products did not display the Power of Attorney (POA). Power of Attorney was added to the header of the Watts Private Product SOI form. If a POA exists, the name will print as displayed on the UI. If no POA exists, the form will print "Power of Attorney: NONE". |
83577 |
|||||||||||||||||||||||||||||||||||||||
A request was made to modify certain fields on the Price Flex Schedule of Insurance (SOI) form. This enhancement will be for the 2018 and succeeding Crop Years and for Price Flex products only. This change will affect the Schedule of Insurance in all printing areas. The following updates were made to the Price Flex Schedule of Insurance form:
|
82712 |
Global
DESCRIPTION | ID # |
---|---|
The Online Help Site was updated with topics as well as with current release notes. |
83336 |
Infrastructure
DESCRIPTION | ID # | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The 2018 Watts provisions in PDF format were loaded in the System as provided by the AIP. |
84176 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2014 update was made by RMA and has been implemented in the System. The following table has been updated for 2014:
|
84293 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2017 update was made by RMA and has been implemented in the System. The following table has been updated for 2017:
|
84294 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:
|
84295 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2016 update was made by RMA and has been implemented in the System. The following table has been updated for 2016:
|
84296 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2015 update was made by RMA and has been implemented in the System. The following table has been updated for 2015:
|
84297 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2018 ADM update was made by RMA and has been implemented in the System. The following table has been updated for 2018:
|
84158 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2014 update was made by RMA and has been implemented in the System. The following tables have been updated for 2014:
|
84428 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2015 update was made by RMA and has been implemented in the System. The following tables have been updated for 2015:
|
84429 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2016 update was made by RMA and has been implemented in the System. The following tables have been updated for 2016:
|
84430 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2017 update was made by RMA and has been implemented in the System. The following tables have been updated for 2017:
|
84431 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:
|
84432 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A 2018 ADM update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:
|
84525 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2014 update was made by RMA and has been implemented in the System. The following table has been updated for 2014:
|
84612 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2014 update was made by RMA and has been implemented in the System. The following tables have been updated for 2014:
|
84543 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2015 update was made by RMA and has been implemented in the System. The following table has been updated for 2015:
|
84613 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2015 update was made by RMA and has been implemented in the System. The following tables have been updated for 2015:
|
84547 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2016 update was made by RMA and has been implemented in the System. The following table has been updated for 2016:
|
84614 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2016 update was made by RMA and has been implemented in the System. The following tables have been updated for 2016:
|
84548 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2017 update was made by RMA and has been implemented in the System. The following table has been updated for 2017:
|
84615 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2017 update was made by RMA and has been implemented in the System. The following tables have been updated for 2017:
|
84544 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following table has been updated for 2018:
|
84616 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:
|
84550 |
MPCI
DESCRIPTION | ID # | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
RMA has modified the P11-8 premium calculations for Hybrid Sweet Corn Seed (0093), Plan 55, for the 2018 RY. The calculation logic for Hybrid Sweet Corn Seed (0093) has been updated to account for the recent changes outlined in the draft version of the P11-8. These changes affect Hybrid Sweet Corn Seed (0093) but not the other crops under Plan 55. |
79921 |
|||||||||||||||||||||
Contracts: For the 2018+ RYs, RMA has made some changes to the Hybrid Sweet Corn Seed premium calculation. The rating will now incorporate the Total Contract Value as well as the Minimum Payment Quantity from the Hybrid Sweet Corn Seed Contract. Both values will be a dollar amount rounded to the whole dollar. The System previously had a Minimum Payment Quantity field that displayed on the Contract pages for Plan 55 crops; however, it was a bushel/acre value that rounded to the tenth. In addition, the System did not have a field for Contract Value. The Contract pages were updated to allow users to input a whole dollar value for Minimum Payment Quantity and enter a Contract Value to be used in the rating of Hybrid Sweet Corn Seed. The following updates have been made to the Contract pages for Hybrid Sweet Corn Seed:
NOTE: This ticket is for the user interface changes only. Rating changes will be implemented with TFS #79921. |
78894 |
|||||||||||||||||||||
With this ticket, APH calculations were updated to accommodate changes made to Yield Cup procedures by RMA. All changes apply to 2018 crops with an 11/30 or later filing date and to all crops in 2019. For crops with a filing date prior to 11/30, old Yield Cup procedures will apply. These changes to calculations and logic apply to the legacy APH page, the APH Drawer, and the Fast Edit PR APH calculations. The APH calculation changes include:
|
||||||||||||||||||||||
The TA/YE Recalc utility logic was updated with TFS #82114 for crops with an 11/30 CCD+. This MCT-initiated utility calculates database values for the Average Yield and Rate Yield for APHs that do NOT have an Approved Yield greater than zero (0). For quoting purposes, the System calculates preliminary values for the following: Standard Procedure Approved Yield (Approved Yield without TA/YE/YC but with a Yield Floor), Adjusted Yield (non-TA/YE/YC Adjusted Yield), Approved TA Yield, Approved YE Yield, Approved TA + YE Yield, and Approved YC Yield. This utility is typically run immediately following the roll of policies to the new RY and is handled as a standard post-roll process. This utility has been part of the post-roll process for several years. Because the YC calculation was pending, this utility was delayed from being run post roll—with plans to run the standard utility following the 6.075 release to production. The database values calculated are then displayed in the TA/YE Comparison grid located at the bottom of the APH. This release added a field for the YC calculation to the grid. This utility will ONLY update the preliminary database values for APHs that have NOT been updated yet for the 2018 RY. If the Approved Yield is equal to zero (0) and year 10 in the APH has acres greater than zero (0) and no production, the utility will apply the database preliminary calculations for use in quoting. At the time the APH is updated with production for year 10 in the APH, the preliminary values are replaced with final values following the user invoking full APH calculations. NOTE: The only change to this recalc utility was adding the YC calculation to values already being set. For coverages and detail lines/APHs that have the YC option applied, the utility will now take YC into consideration when setting the DB values. |
82209 |
|||||||||||||||||||||
APH: TFS #82114 updated APH logic for crops with an 11/30+ Filing Date to account for the YC option procedures. As part of the scope of these changes, the CC/SF rules also required updating. When APHs exist for both a CC and SF practice in a state/county AND have separate T-Yields by practice, the System will apply the "higher of" logic for calculation of the SF Approved Yield as allowed by RMA procedure. This functionality has existed in the System for several years. The new YC option procedures state that the YC option must be first applied to both the CC and SF databases, if applicable, prior to determining the "higher of" yield to use for the SF APH. This latest change is similar to the procedure for CC/SF when YE is applicable (YE is applied before determining the higher of yield), which has also been present in the System for several years. |
82973 |
|||||||||||||||||||||
APH: With TFS #82114, also in the 6.075 release, APH logic was updated to account for RMA's conversion of the Yield Cup procedures to the new Yield Cup "YC" option in 2018 for crops with an 11/30 or later Filing Date and for all crops in 2019. See TFS #82114 in this release for more information regarding the Yield Cup changes for 2018 and 2019. As part of these Yield Cup changes, the Simple Average T-Yield (SAT-Yield) calculations have been impacted. The SAT-Yield is calculated as the average of all yields for APH databases for the same Crop/Practice/Type/T-Yield Map Area (TMA). For APH databases that are not utilizing a Trend Adjusted (TA option) Yield and do not have a year for which a yield has been excluded (YE option), the Approved Yield is used in this calculation. For APHs with a Trend Adjusted Yield and/or a year that has been excluded, the Adjusted Yield is used in the calculation. The new procedures for the Yield Cup (YC) option state the Simple Average calculation should treat YC the same as YE and TA and use the Adjusted Yield in the Simple Average calculation rather than the Approved Yield if the YC option is applied to the APH. With this ticket, the Simple Average T-Yield calculations were updated to mirror TA and YE by using the Adjusted Yield rather than the Approved Yield if the YC option is applied to the APH. |
82974 |
|||||||||||||||||||||
Fast Edit AR: A Kendo-related issue was identified within Fast Edit AR when trying to duplicate a grid line any time a "verified standard rating" or "map area" existed. This Kendo-related bug has been resolved. |
83573 |
|||||||||||||||||||||
Peanut APH: TFS #70661 (in the 6.000 release) and TFS #73296 (in the 6.010 Release) were implemented for 2017+ to address exception processing now allowed by RMA with regards to Peanut APHs. Prior to these changes, "F" Yield Types used to represent classification yields were forced into a Peanut APH in the 2002 and prior RYs by the System and there was no way to apply an exception except with the use of the Override Entire APH by an AIP user. The changes implemented earlier this year were intended to leave the current classification yield logic in place while allowing flexibility in the placement of the "F" Yield Types in more current years within the APH if there was a written agreement or an RO Determined Yield applied. This introduced a general bug with the classification yield logic and required placement of classification yields in 2002 and prior in the APH appears to have been broken. For 2017+, an APH Override option will be added to the APH dropdown if the crop is Peanuts. The APH Override of "Classification Yield" will allow AIPs to select an override coded specifically to account for classification yield placement along with yield types required by RMA within the APH. The System will apply an "F" Yield Type and force placement of the yield types within the APH base period in 2002 and prior years. The System will consider the years as years of reference for determination of the yield floor but will not consider them actual/assigned yields for determining the variable t-yield. The System also will not consider these years as eligible for YA, YE, or TA. The System will apply the standard Category B procedures to determine and display the reference years within the APH; however, the System will calculate the yield floor as 80% of the current t-yield. An APH Override of "RO Determined Yield" will be used when a Determined Yield is applicable (e.g., written agreements and actual RO determined yields scenarios). The System will apply an "F" Yield Type and allow placement of the yield types within the last 4 years of the APH. The System will not consider the years as reference years for calculation of the yield floor, etc. in accordance with RMA procedures. AIPs with policies identified as classification yields in 2017 must manually correct them using the new APH Override post release. |
83396 |
|||||||||||||||||||||
Quotes: Margin Protection functionality within the System requires selection of a related coverage or a stand alone status, by design. It was recently identified that a quote for a Margin Protection coverage was triggering validation to "Select a policy" if the quote was Plan 16 or 17. Because there are Private Product policies that are required to be attached to a quote (for unsupported MPCI coverages), it was necessary to lift the validation that unintentionally extended to a Policy Type of "quote". |
83522 |
|||||||||||||||||||||
Rating changes were applied to the System for Plans 16 and 17 per the P11-13 exhibit. QA and UAT testing was not possible, pending price releases; testing will be completed in the March-April time line under a separate TFS ticket when prices are available. |
82568 |
Private Products
DESCRIPTION | ID # | ||||||
---|---|---|---|---|---|---|---|
MPowerD: This is a spin-off of TFS #84009 to update the User Market Price column so it displays Opt-Out or Opt-In instead of yes or no. |
84009 |
||||||
The following Production Hail display issues were resolved with this ticket:
|
83755 |
||||||
CHPP: The CHPP Guarantee was not calculating the same amount on the parent line as what it was calculating on the child line. It was found that the mpciGuaranteeReductionFactor was not getting stored on endorsement lines during the initial submit acres, which was causing the CHPP Guarantee not to calculate the same as the parent line. This has been corrected. |
83553 |