Skip to content

Lime CRM Knowledge Base

In the knowledge base you can find information and security information regarding the Lime CRM Platform

Removal of Home Screen Web Apps (Progressive Web Apps) on iOS 17.4 or Newer

Lime CRM has been able to be installed as a Home Screen Web App based on the Progressive Web App (PWA) standard on iOS. As of iOS 17.4 Apple have removed the support for Home Screen Web Apps to comply with the Digital Market Act from the European Union. Any Home Screen Web App will continuo to function, but act as a bookmark, opening the website in the user's default browser.

Lime will investigate other methods to bring the best mobile experience to our users.

Lime CRM Desktop Client 11.1.3142

Product Lime CRM Desktop Client Version 11.1.3142 Date published 2024-02-14 Platform Windows Availability Manual installation and Automatic Updates.

This build primarily target general stability and problems with saving outgoing email.

Fixes

  • Worked around issue where unsaved emails without unique IDs caused mixup between Outlook Inspectors for subscribing to events.
  • Backported stability fix for events from background threads.
  • Backported stability improvements related to MFC and threading.
  • Prefer filters over pools of IDs for selections during async operations
  • Unified handling of default filter and view. Resolves issue where settings for initial filter and view are ignored.
  • Merge all settings from external config, resolved issues where CCC cannot be enabled for individual action pads.
  • Improved robustness for solutions with hidden required fields without default value.
  • Reverted mitigation for WebView2 120.0.2210.61 to avoid memory leak reports.
  • Stability: Avoid FinalReleaseComObject for shared COM objects.
  • Use unique timer ids for handling outgoing email to avoid mixup between different documents.
  • Avoid failure for Meeting items (accidentally) passed into integration with Outlook.
  • Added guard against self-destruction during event triggering.
  • Added guard against crash due to self-destruction of object during update.
  • Improved error handling and robustness for document mailer.
  • Workaround problems with legacy support for automatic login via saved password.
  • Ensure timestamps for files use correct timezone.
  • Fixed problem with sorting after searching.
  • Backported stability fix for rare crash during shutdown seen via Sentry.

Lime CRM Desktop Client 11.1.3139

Product Lime CRM Desktop Client Version 11.1.3139 Date published 2024-02-12 Platform Windows Availability Manual installation and Automatic Updates.

This build primarily target general stability and problems with saving outgoing email.

Fixes

  • Worked around issue where unsaved emails without unique IDs caused mixup between Outlook Inspectors for subscribing to events.
  • Backported stability fix for events from background threads.
  • Backported stability improvements related to MFC and threading.
  • Prefer filters over pools of IDs for selections during async operations
  • Unified handling of default filter and view. Resolves issue where settings for initial filter and view are ignored.
  • Merge all settings from external config, resolved issues where CCC cannot be enabled for individual action pads.
  • Improved robustness for solutions with hidden required fields without default value.
  • Reverted mitigation for WebView2 120.0.2210.61 to avoid memory leak reports.
  • Stability: Avoid FinalReleaseComObject for shared COM objects.
  • Use unique timer ids for handling outgoing email to avoid mixup between different documents.
  • Avoid failure for Meeting items (accidentally) passed into integration with Outlook.
  • Added guard against self-destruction during event triggering.
  • Added guard against crash due to self-destruction of object during update.
  • Improved error handling and robustness for document mailer.
  • Workaround problems with legacy support for automatic login via saved password.
  • Ensure timestamps for files use correct timezone.
  • Fixed problem with sorting after searching.
  • Backported stability fix for rare crash during shutdown seen via Sentry.

LDC 12.9.3137

Service Lundalogik Data Component (LDC) Version 12.9.3137 Date published 2024-02-10 Platform Windows Download LDC 12.9.2137 (due to technical limitations in build environment the installer have version -1000 compared to actual module) Included in n/a Manual update How to upgrade LDC

This version of LDC improves stability, resolves reported bugs and introduce support for LISA v2.

Technical Details

  • Unified session handling to enable JSON also for LDC.Attribute
  • Verify timestamp after generating datastructure and retry if changed.
  • Added validation and re-generation of options queries, primarily to support LISA v2
  • Workaround error in logging due to missing settings combined with insufficient privileges.
  • Switched to VS2022 v143 C++ compiler
  • Removed dependency for deprecated .Net Framework v4.0
  • Handle missing transaction for batched update.
  • Added handling of more problematic characters to file-level caching.
  • Worked around potential race-condition for accessing session-table.
  • Extended database level timeout for jobs (ie LISA) to 30 minutes (instead of 5 minutes) for LISA to better cope with slow databases in cloud.
  • Detect and recover from memory fragmentation.
  • Improved support for batch operations via COM interface with compatibility hack for stateless operation.
  • Worked around compatibility issue with LISA and assumptions about stateful batch updates.
  • Reduced risk for locking issues.
  • Worked around problems with trashcan optimization for nested queries.
  • Fixed problem related to mIxEd case and formatting of key names that broke generic support for loading LDC settings from environment variables.
  • Refactored internal mappings to avoid unnecessary usage of database ID.
  • Unified rules for filebased caching.
  • Ensure that large values read from Redis are cached locally to reduce network traffic.
  • Refactored session handling to avoid loading the complete session list.
  • Unified default ttl.
  • Unified mapping between database name and id.
  • Enforce 1h default TTL for all content to avoid problems with stale caches if Redis fails.
  • Improved error reporting for leaked C++ exceptions.
  • Added two-way mapping between database name and id.
  • General support for running LDC without any configuration.
  • Activated caching for XML datastructure for LISA.
  • Improved robustness for optimized trashcan queries.
  • Improved robustness for async updates.
  • Reset update-mode after successfull update.
  • Unified batched updates.
  • Ensure update-flag is only updated for actual updates.
  • Switched default connection strings to use MSOLEDBSQL19, deprecated SQL Server Native Client will now require explicit connection string.
  • Use direct accessor helpers.
  • Added logging for session timestamps.

GDPR Add-on Might be Affected by Security Improvement in Lime CRM

Older versions of the GDPR add-on might be affected by a security improvement in the Lime CRM platform.

Who Does This Concern?

This only concerns customers that fulfill all the below requirements:

  • Use the GDPR add-on in the desktop client.
  • Have not installed the add-on or upgraded its LBS apps since 2022-11-10. I.e., the LBS apps are from a lower version than 3.6.1.
  • Are running lime-crm v2.761.3 or later. This is the upcoming on-premise Lime CRM server release (planned to be named 2024.1).

Symptoms

The buttons in the GDPR add-on to download the personal information as an Excel file or a JSON file will no longer work.

Solution

  1. Upgrade the limepkg-gdpr package to the latest version. Check the GDPR add-on documentation for guidance.
  2. Make sure to remember to replace the LBS apps used by the add-on.

Please note that if you are running the predecessor package lime-crm-gdpr, the first action you must to do is to migrate over to limepkg-gdpr.

2023.2 – Vaalserberg – Patch 3

Lime CRM Server 2023.2.1883

  • lime-crm 2.677.16 -> 2.677.21

Bugfix

Lime CRM

  • lime_query: fix create join in aggregate property selector
  • lime_config.application: catch exception while fetching execution context
  • lime_execution_context: handle gracefully exceptions when fetching current context
  • lime_file: remove rowcount check on file save

Installation

Improve uninstallation process for RabbitMQ and Erlang

  • Continue uninstallation even if RabbitMQ or Erlang uninstall.exe file is missing.
  • Resolves Installer crashes and Erlang uninstallation issues.
  • Additional steps include removal of shortcuts and uninstall keys, enhancing overall stability.

Required: DMARC Email Authentication

Both Yahoo and Google recently announced new requirements for senders starting in February 2024. These new rules apply to all Lime Marketing customers.

How do these new requirements effect your team?

As a Lime Marketing customer, you automatically meet almost all the new sender rules! However, it will soon be required to have a DMARC policy set in your sending domains DNS. A DMARC policy is an instruction for receiving mail servers that tells them what to do when they get an email from your domain that is not authenticated (meaning failed SPF and/or DKIM).

Google's requirement is targeted towards those sending 5k or more emails to Gmail inboxes per day. However, this requirement will be enforced for all Lime Marketing customers.

As the new requirements take effect in February 2024, Lime Marketing will require DMARC for a sending domain to be valid.

What steps need to be taken?

If you're unsure whether your organization has implemented DMARC or not, you can check in your Lime Marketing account. Head to Sending Domains under Administration to see whether DMARC exists for your domains.

If no DMARC policy is found, you need to add one. We recommend setting a neutral policy (p=none) to get started as this won't affect any other emails if your domain is being used from other systems apart from Lime Marketing. For a general guide on adding DMARC at your DNS provider, take a look at this guide.

Your IT team will need to set up a DMARC policy by February 2024 to continue sending emails with valid sending domains from Lime Marketing.

Timeline

1st of February 2024 - Lime Marketing will enforce that all customers meet new sender requirements

Learn More:

Refer to Google and Yahoo guidelines for more detailed information.

BankID Secure start in Lime products

What is "BankID Secure start"?

The Swedish e-identification service “BankID” sharpens the requirements on starting an identification or signing process in their applications in order to increase the security and prevent risk of fraud. Details about the requirements, reasons behind and an FAQ is available on https://www.bankid.com/en/foretag/secure-start

What will be changed?

Lime Technologies will build a new version of Lime BankID API and JavaScript application that fully supports “Secure start”. It will no longer be possible to start a BankID identification/signing in someone's BankID app just by providing the personal identity number. Instead, the user can choose to autostart the BankID app on the same device, as where it is requested, or on another device by scanning the animated QR code. The identification/signing can still be locked to a specific personal identity number, for example in authentication or signature processes.

Timeline

1st of January 2024 - New version of Lime BankID API available that fully supports BankID “Secure start”. Documentation is now available at https://bankid.lime-technologies.com/api/v2/docs

10th of January 2024 - New version of Lime Forms available with support for the new Lime BankID API. Lime Forms v2.87.2 have full support for Lime BankID API v2 as well as an updated frontend package.

1st of January - 30th of April 2024 - Adaptation period for services and applications consuming the Lime BankID API.

1st of May 2024 - “Secure start” is required and non adapted services will not be functional

Affected applications and necessary actions

Lime Forms

An upgrade is highly recommended for all customers having BankID enabled in Lime Forms. Contact your customer responsible to schedule it during the adaptation period. Lime Forms v2.87.2 available from 2024-01-10 has full support for Secure start.

Lime Portal

No changes are required for customers using BankID for Lime Portal authentication.

eSign

An upgraded version of Lime eSign will be released in the beginning of 2024 and announced separately to affected customers. Lime Technologies will take care of all necessary upgrades for Lime CRM cloud customers but Lime CRM on-premise customers need to make sure that eSign is upgraded well before 1st of May 2024.

BankID desktop application in Lime CRM

An updated version will be released in February 2024 and communicated separately to affected customers.

The installer portal (För- & Färdiganmälan)

Lime Technologies will take care of all necessary upgrades.

Custom integrations towards Lime BankID API

Customers that have built their own integrations towards Lime BankID API are responsible to redirect the integration towards the new version of the API. The same goes for any necessary UI changes used with the integration. The documentation of v2 of Lime BankID API is now available at https://bankid.lime-technologies.com/api/v2/docs

"ActiveX component can't create object" when starting Lime CRM Desktop

Background

The error occurs when a user logs in to Lime CRM Desktop using major version 11, leaving the client in a broken state. This issue is caused by a recent update of WebView2 Runtime by Microsoft (version 120.0.2210.61). An issue has been open with Microsoft and others have experienced the same problem.

Update to WebView2 Runtime 120.0.2210.77 and later resolves the issue for all versions of Lime CRM Desktop. The updated versions was released 16th of December 2023 and should be generally installed by automatic updates by the 18th.

Lime CRM Desktop version 11.1.3088 resolves the login issue, but some customizations may not work correctly.

Lime CRM Desktop version 10.18.962 or older are not affected.

Solution

Upgrade to Lime CRM Desktop 11.1.3089 or later.

Download the installer from one of the links below. Ensure that you shut down the desktop client before running the installer. Double-click on the installer and follow the provided steps. You should now be able to use the Desktop Client again.

Auto Update Enabled

This solution assumes the auto-update feature is installed in your environment. By using the auto-update feature, the user does not require admin privileges, and the new Lime CRM version can be installed by the user themselves.

Download Lime CRM Desktop (requires auto-update to be enabled)

Administrators

For this solution, the user needs admin privileges to run the installer.

Download Lime CRM Desktop (requires admin privileges)

Lime CRM Desktop Client 11.1.3088

Product Lime CRM Desktop Client Version 11.1.3088 Date published 2023-12-08 Platform Windows Availability Manual installation and Automatic Updates.

This build primarily target error “ActiveX component can't create object” reported after Windows Update broadly distributed 8th of December 2023.

Fixes

  • Use C++-level object creation instead of COM for internal object.
  • Fixed regression in cookie transfer that broke session handing for WinINET.
  • Removed obsolete reference to loginwithsession, session transfer is since long time handled via cookie sync. Switched to InternetSetCookieEx2 to properly handle expiration and removal of obsolete cookies.
  • Updated MSVCRT to match VS 2022
  • Removed dependency for deprecated .Net Framework v4.0
  • Updated bootstrapper for WebView2
  • Improved robustness for tracking modifications for relations in user interface
  • Avoid reporting errors for abandoned/orphaned operations.
  • Coerce optional parameter-argument in Application.RaiseEvent to string-compatible type to ensure compatibility with existing VBA customizations.
  • Ensure session state is cleared before initiating login.
  • Separate sessions using WebView2 profiles.
  • Ensure SSPI does not take priority over explicit login.