Important changes coming in 2019r2 when using the Esri® World Geocoding Service

Starting with version 2019r2, ArcGIS Online service credits will be required to perform certain tasks when Esri’s ArcGIS World Geocoding Service has been set as the system default geocoding service within Lucity.

There are many tools, services, and applications provided with Lucity that use a geocoding service.  Some of these tools will take the results of the geocoding service and store them in the Lucity database.  It is this action, saving the results of the ArcGIS World Geocoding Service to the Lucity database, that will start using your ArcGIS Online service credits.

More information on this change including what actions, if any, you should take when preparing for the version 2019r2 upgrade can be found in this knowledge base article.  Please contact a Lucity support representative if you have any questions or concerns related to this change.

Keeping Lucity Mobile Running Smoothly

Mobile technology is changing quickly. Announcements about new phones, new tablets, and new security updates are in the news almost daily. It’s our goal to keep our mobile applications running smoothly and securely. We also work hard to take advantage of the latest changes to the devices operating systems (OS).

We have often heard you ask, “When should we update our mobile devices?” Continue reading

A Seamless Integration for Wastewater and Beyond in San Clemente

Our friends (and partners) at WinCan posted an article that highlights the asset management efforts of the City of San Clemente. Lucity is proud to be part of their solution and we’re excited to celebrate their successes with them. Read more about their WinCan + Lucity solution and let us know if you’d like to discuss any opportunities for CCTV integration with Lucity.

 “There’s been a big increase in efficiency,” CMMS Coordinator Elmer Catapang notes. “Our mantra is citywide preventive maintenance.”

Read the full article at blog.wincan.com.

Lucity Mobile will soon require TLS for newer Android devices

Starting in 2020, the Lucity Android 2.0 mobile devices running Android 9 or higher will require an encrypted connection (TLS) to Lucity Mobile server and any GIS web services accessed from the mobile device.  Using encrypted connections for data security has become increasingly important in the current security climate.  Recently, Google announced it would require TLS by default in its latest operating system.

In this article, Dave Burke, the VP of Engineering, states:

“As part of a larger effort to move all network traffic away from cleartext (unencrypted HTTP) to TLS, we’re also changing the defaults for Network Security Configuration to block all cleartext traffic. You’ll now need to make connections over TLS unless you explicitly opt-in to cleartext for specific domains.”

We have temporarily enabled a workaround which will allow devices running Android 9+ to continue to use clear text connections to the server to allow enough time for clients to obtain and configure SSL certificates for the GIS web adapter server and the web server for Lucity Mobile.

After configuring the certificate in IIS, reinstall the  Lucity Mobile Server application to allow the Lucity installer to set the appropriate .config settings for TLS.  Follow Esri guidelines for configuring Esri ArcGIS web adaptor to use TLS for your specific ArcGIS version.

We recommend that all Lucity web applications use TLS, not just Lucity Mobile Server. If you have concerns or questions about this change, please do not hesitate to contact us.

Lucity and CentralSquare >> FAQs

Greetings!

As I am sure that you have heard by now, Lucity has been acquired by CentralSquare Technologies (www.centralsquare.com).  We (Lucity’s Management Team and staff) are very excited about this change.  However, we also realize that change can be concerning. We’ve received questions from our user community and I thought I’d address them here. You can continue reaching out to us as you have been as questions arise – I always love to talk with our users! Continue reading