This Release Checklist applies only to clients who are upgrading from version Lucity 2019 or later.
Lucity stresses that no client should upgrade a test or production environment without reading and understanding this document. Clients must consider several important factors and plan accordingly before upgrading.
What To Know Before the Upgrade
IMPORTANT! Clients cannot upgrade directly to Lucity 2019r2 from Lucity 2015 or earlier. In certain cases, clients may not be able to upgrade directly from Lucity 2015r2.
The Upgrade Guide does not contain Release Notes or Checklist items for Lucity 2019 or earlier. Refer to the installation guide for Lucity 2019 for details on earlier versions.
The 20.3 release only allows the following special characters in the Client Name in Client Maintenance. & - / \ ( ) ‘ Literal space If your client name includes any other characters please remove them before upgrading.
The 20.2 release included changes to make the import and update more consistent when attaching documents and comments. These changes require that any import that includes document/comment attachment be split out as an update seperate from the intial import. Please contact support for information and assistance with making this change.
Lucity 20.1 supports Microsoft Edge but performance is sub-optimal. We do not recommend using Edge with the 20.1 release. We recommend Chrome as the best browser for Lucity users on a desktop computer. If Chrome is not an option Firefox provides a good user experience as well.
All Web applications are now 64 bit. If you are using custom app pools in IIS, they must have the Enable 32 bit flag unchecked.
The Esri JavaScript SDK included in Lucity expects that all data be sent over SSL if Lucity Web is using SSL. If you are using SSL with Lucity Web, review your GIS map services including the geometry and geocoding services and upgrade then to SSL with valid certificates.
The Lucity Web Map changed how it works with the ESRI World Geocoder to bring it in line with ESRI requirements. This means that the some operations in Lucity that use the ESRI World Geocoder will start using ArcGIS Online service credits. More information about preparing for this change.
These features were deprecated in the Lucity 2019 release
Lucity GIS Viewer (a desktop GIS Viewer, please contact Lucity support for a migration path if you are still using this viewer).
Lucity ASP.NET style forms in Lucity Web (these are still supported in the Lucity Admin Form designer for the Lucity Citizen Portal) Note that users should no longer use the Lucity Admin Form designed for editing non Citizen Portal forms.
Starting with Lucity 2019r3 there is a new installer called the Lucity API Gateway. This installer is required for the CentralSquare Finance Enterprise integration. It is not necessary to install this application unless you are a Finance Enterprise customer and are directed to do so by CentralSquare/Lucity.
Lucity 2019 has an additional required installer called Lucity Report Server. We recommend installing this on the same server and port you install Lucity Document Server. If Lucity Web is running SSL, Lucity Report Server should also be installed using SSL. All Lucity reporting for Lucity Web and Lucity Mobile Server will run within the context of this new web service.
Work Employee Setup - The SSN field is removed during the upgrade and any data stored in that field will be lost. If you are using this field to store data other than SSN, move it to another field prior to upgrading.
The following module's have had changes to the picklists. Please review these and fix the picklists prior to upgrading.
Purchase Orders - The Purchase Order module status list has been standardized. Starting with 2019r2, new purchase orders will default to 1 = New Purchase Order. Prior to upgrading, if you were using a status code of 1 to represent a state other than New Purchase Order, we recommend updating your data. More information about preparing for this change.
Facility Building Assessment Library, Facility Building Inventory - Prior to Lucity 2019r2, the User defined fields 1 – 15 in Facility Building Assessment Library were previously incorrectly shared to Facility Building Inventory. They should have been shared with Facility Building Assessments instead. We have corrected this. As a result, your picklists and button captions for these fields will be lost. Please make note of these values in both Facility Building Assessment Library as well as Facility Building Inventory prior to the upgrade and fix as needed after the upgrade.
Distribution Water, Raw Water, Recycled Water - Several fields in the various water modules should have shared picklists but did not. The fields now share picklists but the change will cause existing picklists to be lost. Review the Water release notes for more details.
Lucity 20.2 adds a new system related to the Import and Update. If you are running executables as part of a Import/Update Post Process you must add the executables, including the path to the new List of programs allowed to be run by Import and Update PostProcessing setting.
Included in this release is Early Adopter support for ESRI’s utility network. Refer to the release notes for information on this feature in this release and the limitations.
The Lucity Parts "Issued" functionality was overhauled in Lucity 2019. If you use this functionality, review your employee, building, and room views and, if needed, add the new Transactions and Returnable Parts Issued children to your view.
Facility Building Assessment Library, Facility Building Inventory - Prior to Lucity 2019r2, the User defined fields 1 – 15 in Facility Building Assessment Library were previously incorrectly shared to Facility Building Inventory. They should have been shared with Facility Building Assessments instead. The upgrade corrected this. As a result, your picklists and button captions for these fields are now lost. Please update the values in both Facility Building Assessment Library as well as Facility Building Inventory to the values you were previously using.
Lucity updated the SQL Server driver it uses to run reports in version 2019. All reports should continue to run as normal, however, you should consider updating your custom Crystal Reports to use the new driver. If TLS 1.0 and 1.1 are disabled on your servers any custom reports still using the old driver will fail to run.
The Document Server application pool may no longer be shared with multiple web applications. If you have custom configured applications using this app pool, you must create new application pools for each application.
The Lucity API Gateway application pool may not be shared with multiple web applications.
Recommended Steps for Every Lucity Release
Lucity recommends that administrators:
Run theValidation tool (found in the Geodatabase Configuration tool, located on the Lucity toolbar in ArcCatalog). The Validation tool checks the geodatabase configuration for any fields that have been deprecated. Learn more.
Review theRelease Notes to learn about new features.