Related
Release Notes 6.010.0
These release notes provide brief descriptions of changes included in AgWorks 6.010.0.
System Updates
Forms & Reports
DESCRIPTION | ID # |
---|---|
Production Reporting Worksheet: An enhancement was requested to add the County to the Crop Summary section of the Production Reporting Worksheet. This change was made to the Production Reporting Worksheet, and since the format of the Production Reporting Worksheet was already being updated, other form standards were implemented in the form's Header, Crop Summary section, Detail Line section, and sort order at the same time. |
71087 |
HR-ACE: An enhancement was requested to indicate if HR-ACE applies to a unit on the Production Report, Production Reporting Worksheet and APH Database Form. HR-ACE is indicated for units on Acreage Reporting forms where "HB" prints in the Option field. These forms were updated to print "(HB)" behind the Unit Number for the units that have HR-ACE indicated. The Unit Structure code prints behind the Unit Number on the APH Database Form when applicable, and "(HB)" prints behind the Unit Structure code |
71524 |
Revised and New Illinois Endorsements were added to the System. This includes the corrected Wind endorsement and the Canning Rejection Endorsement for Sweet Corn. |
73833 |
myHudson: As part of the load balance solution, this ticket created API functions for each of the Data Warehouse Report panels so that the data can more quickly be pulled from the main eHarvest application. |
74184 |
Infrastructure
DESCRIPTION | ID # | |||
---|---|---|---|---|
A Special Provisions update was made available by the RMA for 2018 and was implemented in the System. |
73559 |
|||
A 2013 ICE update was completed in the System. The following table has been updated for 2013:
|
74311 |
|||
A 2014 ICE update was completed in the System. The following table has been updated for 2014:
|
74312 |
|||
A 2015 ICE update was completed in the System. The following table has been updated for 2015:
|
74313 |
|||
A 2016 ICE update was completed in the System. The following table has been updated for 2016:
|
74314 |
|||
A 2017 ICE update was completed in the System. The following table has been updated for 2017:
|
74315 |
|||
A 2018 ICE update was completed in the System. The following table has been updated for 2018:
|
74316 |
MPCI
DESCRIPTION | ID # | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Land IDs: In select counties in Ohio, the survey system has a reversed order of the direction on the Township/Range values. Normally, N/S direction is the Township and E/W is the Range, but in some counties, those are flipped. So instead of displaying as (005) 012N 001E, it is displaying as (005) 001E 012N. The System has a System Preference to note counties where these flipped values should be accepted. If the county is listed in the System Preference, the System will allow a user to key a "flipped" Township/Range value without trying to reformat it to the standard survey. The following counties in Ohio have been added to the System Preference: Butler, Champaign, Clark, Greene, Hamilton, Miami, Montgomery, Shelby, and Warren. NOTE: The System will store it correctly now and find planted CLUs for the listed Farm/Tract, but it won't show as a valid land ID for the entered Farm / Tract. A spin-off ticket has been created to update the Land ID validation logic to account for flipped townships in these counties (TFS #74479). |
74172 |
|||||||||||||||
Onions: Currently, Acreage Limitation warnings exist on the Signature Maintenance page when an original AR Sign Date is entered for Onions; however, the Acreage Limitations are not necessarily applicable to every State/County/Type/Practice for this crop. For 2017+ RYs, an update was made to the logic that triggers the Acreage Limitation warning on the Signature Maintenance page. The System will only display the warning if the Crop is "Onions (0013)", ADM A01200 contains a record with the same Plan/State/County as the selected coverage, and the Acreage Limitation Statement Code is "00303" or "01018". NOTE: The scope of this ticket is for the Signature Maintenance page only. TFS #72542 has been added as a placeholder to review the implementation of this edit on the Fast Edit grid at a later date. |
69502 |
|||||||||||||||
APH: An issue was identified where changes made to the APH within the drawer in the Fast Edit AR were not sticking and persisting to the actual APH grid outside of the Fast Edit AR. The Fast Edit AR was updated to calculate the APH that was updated through the drawer on Save and Save & Continue. |
71760 |
|||||||||||||||
Fast Edit AR: The Trend Adjustment & Yield Exclusion Comparison link/page accessed from within the Legacy Maintain APH page was not included with the original deployment of the APH Drawer that is accessible within the Fast Edit PR and Fast Edit AR pages. TFS #69067 added it for the Fast Edit PR page. However, it was not implemented on the Fast Edit AR page. The Blended Skip Row Calculator window was also not working correctly so that was fixed with this ticket as well. The TA/YE Comparison link/page accessed from the Legacy Maintain APH page has been implemented in the APH Drawer (which is accessible via the Fast Edit AR page). As with the link on the Legacy APH page, it will be available if "TA" or "YE" are available for the RY/State/County/Crop/Type/Practice (per the ADM) even if the option(s) are not elected for the coverage. The Blended Skip Row Calculator will now also be functional within the Fast Edit AR's APH Drawer. |
72984 |
|||||||||||||||
SBIs: During internal regression testing, a "Sorry..." error was being received when saving the Add SBI page if the City field was empty. Users should receive the Invalid City/State/Zip Combination error message in that scenario instead. The logic on the Add SBI page was updated so the "Sorry..." error is no longer thrown and the appropriate City/State/Zip Combination error message is displayed. |
73121 |
|||||||||||||||
Nursery: An issue was identified with the PIVR Signature Date within the Signature Maintenance page for Nursery coverages. The date, in and of itself, added through the Signature Maintenance page is not changing the "Approved" processing status to "Incomplete". However, if you enter the date through the View Detail Line grid, it does. The interim work around was to use the View Detail Line grid for entering the dates for PIVR Sign Dates. The Signature Maintenance logic was updated to have changes and/or additions to the PIVR Signature Date reset the processing status on the Nursery coverage to "Incomplete". |
73131 |
|||||||||||||||
APH: An update was made to the maximum character format of the Total Production and Reported Acres fields in the Production History grid of the Legacy Add New and Maintain APH pages for the 2017+ RYs. The following updates have been made: Total Production fields within the UI:
Reported Acres fields within the UI:
|
73175 |
|||||||||||||||
Peanuts: With the implementation of TFS #15954, the APH logic for Peanuts (0075) was updated to allow "F" Yield Types to exist in years after 2001 if a Determined Yield or Written Agreement is applied to the APH database. It was found during testing that the Reference Year logic for Peanut Classification Yields ("F" Yield Types in Yield Year 2001 and prior) was being applied to Determined Yields. This ticket implemented updates to the Reference Year logic for Peanuts (0075) for 2017+ RYs when a Determined Yield or Written Agreement is applied to the APH Database. The System will first identify the "F" Yield types within a Peanut (0075) database and then set the Reference Year value and calculate the Yield Floor using the applicable logic for the identified yield type. |
73296 |
|||||||||||||||
High Risk: The detail line contains a field for a Sub County Code to designate High Risk (HR) Map Areas that impact premium calculation. When there is a Partial High Risk Map Area, the agent is responsible for verifying whether the Section-Township-Range falls within the HR Map Area and designating it appropriately on the detail line. There are some areas of the country where a county may be partially HR and partially NOT HR. In these instances, there is a Verified Not High Risk checkbox that can be set to confirm that the HR status has been confirmed. However, a single Sect-Township-Range should not have both the HR Map Area and the Verified Not High Risk checkbox applied. Previously, the System was allowing both to be selected on a single detail line. A new Verified Standard Rating checkbox has been added to the database and the Legacy Maintain Detail Line page and the new Fast Edit AR Detail Line Drawer. This new checkbox replaces the Verified Not High Risk and Verified Not Unrated checkboxes. This checkbox will only display on these pages if a Sub County Code (Map Area) does NOT exist and the same "Partial Land ID" logic that exists today is applicable (i.e., P or C or NULL combo). The Verified Not High Risk and Verified Not Unrated checkboxes will no longer display on the Legacy Maintain Detail Line page and in the new Fast Edit AR Detail Line Drawer. |
59040 |
|||||||||||||||
Land IDs: When agents had multiple Land IDs to enter for a new premium line, an interim save was required after each line before the user was presented with the next blank line in the Land ID grid. This required excess clicks for the interim save. A change was made to present the user with a blank line at the top of the Land ID grid as soon as the first land ID is entered. This allows the user to key as many Land ID records as needed before performing a single save. By design, a save of the added Land ID records is required before the user will be presented with the CLU link to attach individual fields. |
73299 |
|||||||||||||||
Peanuts: A bug was identified with the Total Guarantee calculation for Peanuts with contracts if the "LP" option existed on the coverage. The System was not accounting for the different coverage levels by irrigated and non-irrigated practices and was always using the non-irrigated coverage level to calculate Total Guarantee. The Total Guarantee calculation for Peanuts has been updated to account for Coverage Levels by Practice. The System will now use the irrigated coverage level for detail lines with an irrigated practice and the non-irrigated coverage level for non-irrigated detail lines. Total Guarantee = round(round(round(Approved Yield * Coverage Level,0) * (Guarantee Adjustment Factor),0) * (Reported Acres),0) |
74135 |
Private Products
DESCRIPTION | ID # |
---|---|
A placeholder line was reading "ALL" when "Non-Irrigated" or "Irrigated" was selected. The logic was updated to pull in the correct Practice on placeholder line when a specific Practice was selected. |
70660 |
Production Hail: It was requested that agent users be able to edit detail lines on Production Hail quotes and binders as long as they have not been submitted. Then, once the policy has been submitted, the agent can edit the detail line for up to 24 hours after. An enhancement was done so that there will be no restriction on detail line edits on Production Hail for quotes and binders as long as they have not been submitted. For agent users, once in "Policy" status, they have 24 hours to correct anything incorrectly keyed. |
72270 |
Production Hail: A bug was found while testing some feedback from an AIP. If the user was setting up a Production Hail policy that had the Coverage by Practice option selected on the placeholder lines on the Create Policy page, it was showing the Practice as "All". As such, upon submit of acres, it was causing duplicate lines. A correction was made so that when the Coverage by Practice option is selected when setting up an Production Hail policy, on the View Production Hail page, when the user expands the record, it shows the selected Practice instead of "All". |
74260 |
Batch Reporting: A request was received to add the ability to print applicable provisions when printing from the Private Product Batch Reporting Tool (Reports > Private Product Reporting > Batch Report). A new option, "Include Provisions", is available to select in the Batch Report criteria. If this option is selected, then when printing the batch reports, the policy provisions and endorsements will print with the selected forms. The provisions will print once per policy in the batch (e.g., if 5 Crop Hail Applications are in the batch report, then 5 provisions will print following each application). This functionality is similar to the print option displayed on the Print Forms tab where the user can select the provisions to print. This update is applicable to all Crop Years. |
65482 |