If using Lucity Mobile for the Android Tablet offline, update two system settings on the Mobile tab for an internally accessible url as well as an externally accessible url. The internally accessible url is accessed from the machine where the services are running. The externally accessible url will be accessed from the tablets. These will not be automatically set by the installer. See here.
Review network configuration to make sure that the services machine can make outgoing requests to the machine where Lucity Mobile is installed for the port where Lucity Mobile is configured. By default this is 443.
Clients with scripted imports for SCADA, fuelings, or other external data using Lucity.Import.exe are encouraged to configure and use Lucity.ImportAndUpdate.exe instead. Lucity.ImportAndUpdate.exe is a superior import because it populates default values, performs calculations, allows updating existing records, enforces business rules, as well as other advantages. See here for configuring the import.
Verify redlining service information in GIS>>Map Services is correct. More information
Verify editable map service information in GIS>>Map Services is correct. More information
A new option for keeping Lucity and ArcGIS data in synch is available which uses feature services, does not require an SOE, and supports work flows such as the Esri ArcGIS Data Collector for collecting data outside of an edit session. See here for configuration information. This is not a required change, the Lucity SOE will continue to be supported for this release.
To use new GIS editing functionality available in Lucity Web and Lucity Mobile, configure the above.
We recommend running the validation tool in Geodatabase Configuration tool in ArcCatalog on the Lucity toolbar. This will check for any fields that have been deprecated. See here
Starting with ArcGIS Server 10.1, ArcGIS Server urls are now case sensitive. Ensure that all urls have the proper case in Lucity Administration. (System>>Settings and GIS>>Map Services and GIS>>Map Setup)
Add Windows Users to Active Directory Group if Needed
During the server installation, you made a decision as to whether to use Windows Authentication as a method for users to connect to the databases. If you chose this method you also chose an Active Directory Group to use. Make sure that all users of the Lucity software are added to the Active Directory Group you specified to ensure your users can get into the software. See here (Database Connection Encryption Options, http://help.lucity.com/webhelp/v145/install/index.htm#25355.htm)
Logging configurations have changed. Clients with custom logging configurations should review the updated installed logging.config and adjust it as desired. Clients may also need to review the logging.config in the Config folder on their Lucity Server install if they have placed one there for distribution.
Subscribe User’s Dashboards to new Lucity Blog
If you feel it would be helpful to your users, you can add an RSS feed to our new Lucity blog to their dashboard. This blog will contain content covering how to use new enhancements in this release, future releases and service packs. The feed for the blog is http://blog.lucity.com/feed.