Related
Release Notes 6.090.0
These release notes provide brief descriptions of changes included in AgWorks 6.090.0.
System Updates
Forms & Reports
DESCRIPTION | ID # | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
A Special Provisions update was made available from RMA on 1/31/2018. Two files were downloaded. The Special Provisions for 2018 have been downloaded into the System. |
84974 |
|||||||||||||||||||||
A Special Provisions update was made available from RMA on 2/7/2018. The Special Provisions for 2018 have been downloaded into the System. |
85646 |
|||||||||||||||||||||
Some feedback was received where the Total Acres field in the Annual Forage Schedule of Insurance (SOI) Premium Summary was causing some confusion as a Growing Season could have multiple coverages and the Growing Season’s Acres are listed for each Growing Season coverage. Previously, the Annual Forage SOI Total Acres field was adding all of the Acres listed for each coverage. With this ticket, the Annual Forage SOI's Premium Summary's Total Acres field was updated to always print "N/A". |
83936 |
|||||||||||||||||||||
Some clean-up items were identified while working on TFS #60557 in the 6.080 Release. These items were updated in the APH Database / Acreage Reporting (APH / AR) form:
|
84928 |
|||||||||||||||||||||
MCT was made aware that zeros are always printing in the 2nd ARH database Total fields on the ARH page in the MPCI Combo Form. The zeros printing in the Total fields in the 2nd ARH database on the ARH page in the MPCI Combo Form were corrected. |
86174 |
|||||||||||||||||||||
PDFs for provisions and endorsements have been loaded into the System. |
86278 |
|||||||||||||||||||||
eSign: The MBAR Map Based Acreage Report has been modified and enabled for use within the eSign Wizard. For this form, the eSign Wizard will:
NOTE: Measurement Service Comment Entry is OPTIONAL.
|
77687 |
|||||||||||||||||||||
A request was made for Underwriter and Field Representative fields to be added to the Private Products Policy Register (Reports > Private Product Reporting > Policy Register). These two fields have been added as dropdown filters for the policy register. |
84717 |
|||||||||||||||||||||
An enhancement was made to the Named Peril Product Type so that, when the user prints the Schedule of Insurance, if the Unsupported by MPCI checkbox was selected, then on the form, "N/A" will be displayed under the MPCI policy number. |
59589 |
|||||||||||||||||||||
While working on TFS #83480 in the 6.075 Release, it was found that the sub-header was not printing on page 2 when the Crop Summary section continued to print coverages on page 2 of the APH Database and Acreage Reporting Form. The APH Database and Acreage Reporting Form was updated to print a sub-header on page 2 when the Crop Summary section continues to print coverages on page 2. |
84219 |
|||||||||||||||||||||
MCT was notified that the A & O value printing in the A & O Note sentence, "FCIC has paid an Administrative and Operating expense subsidy on your behalf in the amount of $???.??.", did not match the Total A & O printing in the Premium Summary on the WFRP Schedule of Insurance (SOI). This value was updated to print the same A & O amount as the Premium Summary's Total A & O field on the WFRP SOI. |
85518 |
|||||||||||||||||||||
MPowerD: When a user was batch printing the Confirmation of Coverage for MPowerD and using the Auto-Attach, the form that was auto-attached to the policy was displaying a red error. A correction was made so that a user can auto-attach a Confirmation of Coverage for MPowerD and then open the auto-attached form and have it display without any error. |
85757 |
|||||||||||||||||||||
Previously, the Production Report only printed one blank APH Database section when the form was printed in the blank and pre-headed report styles. AIPs requested to print two APH Database sections like the pre-filled report style includes. The Production Report was updated for all years to print two APH Database sections when the Production Report is printed in the blank or pre-headed report styles. |
58015 |
|||||||||||||||||||||
RMA released a 2019 Nursery Handbook that has updates to the Plant Inventory Value Report (PIVR). The updates to the PIVR are applicable for 2019 and succeeding Crop Years. The PIVR is available to print from the MPCI Print tab and from Batch Printing. |
85898 |
Global
DESCRIPTION | ID # |
---|---|
The Online Help Site was updated with topics as well as with current release notes. |
85932 |
Infrastructure
DESCRIPTION | ID # | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
An ICE 2014 update was made by RMA and has been implemented in the System. The following table has been updated for 2014:
|
86185 |
|||||||||||||||||||||||||||
An ICE 2015 update was made by RMA and has been implemented in the System. The following table has been updated for 2015:
|
86186 |
|||||||||||||||||||||||||||
An ICE 2016 update was made by RMA and has been implemented in the System. The following table has been updated for 2016:
|
86187 |
|||||||||||||||||||||||||||
An ICE 2017 update was made by RMA and has been implemented in the System. The following table has been updated for 2017:
|
86188 |
|||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following table has been updated for 2018:
|
86190 |
|||||||||||||||||||||||||||
An ICE 2015 update was made by RMA and has been implemented in the System. The following table has been updated for 2015:
|
86570 |
|||||||||||||||||||||||||||
An ICE 2016 update was made by RMA and has been implemented in the System. The following table has been updated for 2016:
|
86571 |
|||||||||||||||||||||||||||
An ICE 2017 update was made by RMA and has been implemented in the System. The following table has been updated for 2017:
|
86573 |
|||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:
|
86574 |
|||||||||||||||||||||||||||
An ICE 2014 update was made by RMA and has been implemented in the System. The following table has been updated for 2014:
|
86567 |
|||||||||||||||||||||||||||
An ICE 2014 update was made by RMA and has been implemented in the System. The following table has been updated for 2014:
|
86962 |
|||||||||||||||||||||||||||
An ICE 2014 update was made by RMA and has been implemented in the System. The following tables have been updated for 2014:
|
87112 |
|||||||||||||||||||||||||||
An ICE 2015 update was made by RMA and has been implemented in the System. The following table has been updated for 2015:
|
86963 |
|||||||||||||||||||||||||||
An ICE 2015 update was made by RMA and has been implemented in the System. The following tables have been updated for 2015:
|
87113 |
|||||||||||||||||||||||||||
An ICE 2016 update was made by RMA and has been implemented in the System. The following table has been updated for 2016:
|
86964 |
|||||||||||||||||||||||||||
An ICE 2016 update was made by RMA and has been implemented in the System. The following tables have been updated for 2016:
|
87114 |
|||||||||||||||||||||||||||
An ICE 2017 update was made by RMA and has been implemented in the System. The following table has been updated for 2017:
|
86965 |
|||||||||||||||||||||||||||
An ICE 2017 update was made by RMA and has been implemented in the System. The following tables have been updated for 2017:
|
87115 |
|||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:
|
87116 |
|||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:
|
86966 |
|||||||||||||||||||||||||||
An ICE 2018 update was made by RMA and has been implemented in the System. The following tables have been updated for 2018:
|
87283 |
MPCI
DESCRIPTION | ID # | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Fast Edit AR: Users now have the ability to add an APH from within Fast Edit AR. Basic functionality was added with this release. Additional functionality will be added in future releases. |
66994 |
|||||||||
Fast Edit AR: A user interface enhancement was made to the Fast Edit AR page to assist users when processing an Acreage Report. The sum of the Total CLU Acres for each coverage will now display to the right of the Total Reported Acre value. The CLU Acre value will update in real time as CLU Acres are entered on detail lines associated with the coverage. The visual will help confirm that CLU Acres have been keyed for the coverage and are within a reasonable tolerance of the Reported Acre value. The Total CLU Acre value will be the sum of the total planted CLU Acres for the coverage. This includes:
|
85631 |
|||||||||
APH: An issue was reported with the Yield Cup logic and how the System is not allowing the Yield Cup to apply if any yields within the APH database had ever been identified as inconsistent or excessive. The Yield Cup procedures state an excessive or inconsistent yield only prevents the cup from being applied if an actual yield is reduced due to being excessive and/or the approved yield is reduced due to being inconsistent. The Yield Cup logic has been updated to allow a cup when years within the APH are identified as excessive or inconsistent except in the following scenarios:
|
86166 |
|||||||||
Almonds: An AIP found a few situations where the Almond Higher Yield calculation was being removed as the Approved Yield within the APH user interface and on the detail line. One minor change was made to the Almond APH calculation so, if the Higher Yield applied, it did not get removed during any additional processing to the APH. |
85954 |
|||||||||
APH: An APH bug was identified where the System was applying the "YE" option code to the APH when it was elected on the coverage but no years within the APH had actually been excluded. With this ticket, APH logic was updated to no longer apply the "YE" option code to the APH unless one or more years have been excluded from the APH. |
86087 |
|||||||||
APH: An APH bug was identified where the System was not correctly calculating and applying YA in the scenario where YC cannot apply due to the t-yield decreasing by more than 10% from the prior year. This issue was resulting in PASS error codes P15-4839 and P15-5880. APH logic has been updated and is now calculating and applying YA correctly. |
86408 |
|||||||||
Coverage: A typographical error displayed on the user interface when the on-page validation was returned for the LP option (Coverage Levels by Practice). This has been corrected. |
86476 |
|||||||||
Fast Edit PR: During internal testing, it was noticed that the Written Agreement Number that displays in the APH Drawer on the Fast Edit pages displayed in black text while the Written Agreement Number in the Detail Line Drawer displayed in red text. For consistency, the display of the Written Agreement Number in the APH Drawer was updated to also display in red text. |
69477 |
|||||||||
Rice: A report was received on 3/12 that users were unable to enter a stand-alone MP Rice coverage. There was some old code on the Add New Policy page that expected the crop to be Corn, Soybeans, or Wheat that was re-introduced when the PLASMA technology upgrade was made to this page in late 2017. The invalid restriction on the field was removed so the System is now allowing the selection of a stand-alone MP coverage on Rice. |
86970 |
Private Products
DESCRIPTION | ID # |
---|---|
A Township Limit was not working correctly if a quote had more than one detail line that, when added together, was over the limit. An update was made to calculate the Township Limit on a quote line by line and by total policy liability. |
86127 |
A user was receiving a JavaScript error when using the batch endorse on Production Hail policies. A correction was made so that, when the user is in a Production Hail policy and uses the Batch Endorse button, upon selecting Save & Exit, they will no longer receive a JavaScript error. |
86808 |
For mark complete in 2018, Private Product policies were not being updated nor were acres being submitted. A correction was made for 2018 Private Product policies so that once the acres are marked complete on the MPCI side, the linked Private Product policies will now be updated, acres will be brought across, and the policy status will be updated to "Acres Submitted". |
85595 |
Internally, an issue was found where a user could restore an optional endorsement that had the same Endorsement Code as one that had been re-added, resulting in a duplicate optional endorsement on the same line. A correction was made to optional endorsements that users are allowed to add. If the optional endorsement is added, then deleted, and then re-added to the line, the user will no longer be allowed to reinstate the originally-added optional endorsement which was allowing the same optional endorsement to be on one parent line. |
43110 |