Performance Hotfix Available for Lucity 2017

Today we released a hotfix for the Lucity Web application that improves performance for users on Internet Explorer 11 who are on Lucity 2017.  It also includes several bug fixes which affect users on all browsers.

This hotfix disables the ability to customize colors in Internet Explorer.  Color customization is still supported in other browsers such as Edge, Chrome, and Firefox. We currently have no plans to re-enable color customization for Internet Explorer in future releases.  The performance impact of allowing dynamic colors is too high for Internet Explorer.

The additional fixes included in this hotfix are: Continue reading

Windows Server 2016, SQL Server 2016, and Lucity 2016r2 SP1

This week we released Lucity 2016r2 SP1. The service pack includes a new dashboard import/export, a quick lookup for parts, and bug fixes. It also includes support for Windows Server 2016 and SQL Server 2016.  It can be downloaded from our support portal for users with access to software downloads.

Updated specifications for Lucity 2016r2 can be downloaded here. Older releases of Lucity will likely also work with SQL Server 2016 but will not be tested and we will not be making fixes to support SQL Server 2016 in those releases. The database unification process included in Lucity 2015r2 will not be tested by Lucity on SQL Server 2016. If you intend to move to SQL Server 2016, we suggest you consolidate your Lucity databases first.

The Lucity 2017 release is expected to be released mid February 2017 and will also include support for Windows Server 2016 and SQL Server 2016.

Lucity iOS clients will require Forward Secrecy with SSL beginning Dec 5, 2016

As previously announced, the Lucity Mobile 2.0 application for iOS will require SSL with TLS 1.2 starting next week.  In addition, SSL must be configured to support (perfect) forward secrecy using the Elliptic Curve Diffie-Hellman (ECDHE) key exchange.  This requires cipher suites installed on Windows Server to support this key exchange.  The order of the cipher suites will also affect whether perfect forward secrecy is supported.

These requirements are due to new Apple Security Requirements which require all submitted apps to adhere to Application Transport Security (ATS) before the end of 2016.

If you have any questions or need help figuring out whether your servers will support the new requirements, please contact Lucity Support.


Lucity iOS Clients will require SSL (TLS 1.2) beginning Dec 5, 2016

Users of Lucity Mobile for iPad or iPhone with Lucity 2016 or Lucity 2016r2 will receive an update next week which requires TLS 1.2.  These new requirements are necessary to meet new Apple requirements.  There is no backdoor or work around.  Lucity Mobile Server must be deployed with SSL and must support the TLS 1.2 protocol. We announced this in a previous blog post but want to put out another warning to make sure everyone is ready!

Microsoft Windows Server 2008r2 does not enable TLS 1.2 by default.  If you have Lucity Mobile Server deployed on a Windows Server 2008r2, you must take manual steps to enable TLS 1.2 on these servers.  This article contains some details about the steps to enable TLS 1.2 on Windows Server 2008r2.

Please see the post discussing the forward secrecy requirement as well.  This is also a critical requirement for iOS clients.

If you have questions or concerns, please contact Lucity support.