Fixed Issues for Version 21.3 Critical Patch 1
This section describes the issues that have been fixed in this release.
Why we fixed these issues: These issues were fixed to improve usability and to help ensure the Encompass Product & Pricing Service is operating as expected. The issues that are chosen to be fixed are based on the severity of their impact to clients and client feedback.
Issues with EPPS Zip Code Database and County Table Resolved
As part of the Encompass 21.3 Major release, the zip code database and county table were updated. To maintain consistency between Encompass and EPPS, the same updates made in Encompass were made in EPPS.
-
For new zip codes, the associated county was added to the county table.
-
For deleted zip codes, the associated county was removed from the county table.
-
For county names that did not match between Encompass and EPPS, the Encompass version was added to the county table.
As a result of the updates to the zip codes and counties, several issues occurred:
-
A system error was generated when certain zip codes were entered on the Property tab (e.g., 18301 or 29576).
-
Counties were missing (e.g., Morgan county in Alabama or Olmsted county in Minnesota).
-
Counties were displayed for the wrong state (e.g., Noxubee county for Alabama instead of for Mississippi).
These issues have been resolved and now the system error is no longer generated, the missing counties have been added, and the correct counties/states are displayed.
System Error No Longer Generated for Zip Codes with Multiple Counties
An issue occurred where a system error was generated when a zip code with multiple counties (e.g., 18302) was entered on the Property tab, a county was selected from the pop-up window, and then OK was selected. This issue has been resolved and the system error is no longer generated when a county is selected for a zip code with multiple counties on the Property tab.
|
Previous Section: Introduction |