Lime CRM 2020.2 - Keb

🖖 Trusted, yet brand new

This releases of Lime CRM is one of the biggest we ever have done, and it it really feels like both the underlying platform and the Web Client has started to come to their own. Paired with just released Lime BI and the upcoming Lime eSign we are taking our offering to new places.

Getting a release like this together is a massive effort, and every single part of our organisation has help out in different ways. We are especially glad to have a lot direct contributions to Lime CRM from the expert service organisations! With this release we are changing the version scheme of Lime CRM and this release will be called Lime CRM 2020.2.

The scheme is really simple [year-of-release].[release-number-that-year]. We think the scheme will be simpler, yet more functional then our previous scheme

Versions numbers in all honour, but with this release we will give our on-premise release a name too! As mentioned, releasing great software is a massive effort, but it is also a processes where you need to adapt, overcome and change. It requires dedication and very little room for error. Finally it is a team effort. One could almost compare it to an expedition to climb a mountain, so with this our on-premise releases will be given a name of peaks worthy summiting, but also has a relation to us as an organisation and the people who work here. We think the first name is pretty given – Kebnekaise, or for short Keb. Situated in the very, very north Kebnekaise is the highest mountain in Sweden, rising 2106 m over the sea.

Thank you Kristoffer Cedeberg for pitching the idea of naming our releases.

⚠️ Breaking changes!

With this release of Lime CRM the add-ons Infotiles, Newsletter, GDPR and Lime Event are no longer included in the base installer. To (keep) use(ing) these add-ons they should be added to you solution as requirements.

✨ Highlighted Features

📁 File based document storage

Lime CRM can be configured to store documents on disk instead of in the database. Shout out to Tommy Lindh for implementing this feature!

🔐 Login in using AzureAD for the Web Client

Support for AzureAD while logging into the Web Client. This will enabled customer to use security and convenience features such as, single sign on, multi factor sign on, enforce password policies. We are looking into brining the same functionality to the Desktop Client in the fall. The feature will also arrive in the cloud during the fall. Thank you Martin Berg for being the catalyst of creating this feature

✏️ A brand new Lime Admin

A brand new version of Lime Admin, providing a visual UI for configuring the web client and add-ons. When creating add-ons to Lime CRM, you can automagically get a custom UI for the add-on to simplify configuration. It is no secret that we see Lime Admin as the coming replacement for LISA.

💄 Improved UI in the Web Client

Many minor UI improvements in the Web Client; to provide a simpler and easier to use interface:

• Related view is now wider and pops out to make it easier to know where you are in the web client.

• The table view is now adjusting to screen size in a much better way, making it easier to grasp the information shown. The rows are also tighter to get a better overview of the data shown in the table.

• The activity feed has been redesigned to include soft borders, more highlighted headings and improved relation pickers.

• The start page can now be customized to be able to show custom widgets (this was previously behind a feature switch). ### 🛠️ Application Configuration When configuring Lime CRM we have so far had to pick between either lime-config or lime-data based config. lime-config is file based and server instance unique; perfect for server configuration such as ports, timeouts etc. lime-data powers Lime Admin and is stored in the database. Albeit convenient it comes with some trade offs; secrets such as API-keys or passwords are best kept out of the database and URLs for integrations can become problematic when for example restoring a production database to a test environment. With Lime 2020.2 we are expanding lime-config to include application level configuration. One can now configure unique configurations for each app running on a Lime Server. This is perfect for API-keys, Passwords or URLs. Full documentation can be found here. ### 👩‍🔬 EXPERIMENTAL: A comply re-designed object card

A completely new layout of the object card in the Web Client behind a feature switch. The new design includes the following:

• Related information is now presented in tabs
• The tabs have counters indicating the number of items in them
• You now have the possibility to create custom tabs to meet specific customer needs (on-premise only until we have isolated apps)
• There are now three different slots where customized widget/actions can be reached (on-premise only until we have isolated apps)
• The visual design is more minimalistic and cleaner and
• The overall usability is improved

👨‍🔬 EXPERIMENTAL: Speed improvements for the Desktop Client on-premise

****A Redis caching backend can now be configured and The Lime CRM data structure is cached. We have seen speed improvements between 3x-10x for common read operations in the Desktop Client. Read more here

🔨 Highlighted Improvements and Bug fixes

Lime Core

• Improvements to Object Access. Several bugs where to few objects where returned has been fixed
• Makes the task-handler debuggable in VSCode
• The API documentation now supports having a colon in a fields local name. Thank you Richard Westberg!
• The API documentation can now be used while developing, served over http
• The search indexer no longer crashes while indexing fields with over 10000 characters, instead these fields are ignored
• BeginsWithOperator now works with Lime Objects, great contribution Niklas Olsson!
• You can use much larger DSL while writing tests. Nice fix David Hurtig!

Lime Web Client

• Search in option queries now handle capital letters
• The table view is now updated when updating an object not part of the current filter
• Editing a already existing history note will no longer update the date for when the history note originally was created
• User is now returned to previous page after login in again