Lime CRM Desktop Client 11.3.4511

Cumulative release for 11.3.x covering everything since the 11.3.4502 baseline.

Improved

Find a related record by typing its id. Typing a number that is a record's id into a relation field's search now pins that exact record at the top of the dropdown, even when the record's description does not contain those digits. The match resolves instantly from the already-loaded entries, or is fetched from the server when the record has not been loaded yet. The matched id is shown as a bold, right-aligned badge on the pinned row so it is clear why that row is there.

Multi-value option fields can be operated from the keyboard. Fields that present a checkbox list of options (multi-select “set” fields) now support full keyboard use: Down or Space opens the dropdown; the arrow keys, Home / End and Page Up / Page Down move the highlight; and Space checks or unchecks the highlighted option. Previously these fields could only be operated with the mouse.

Type-to-find inside multi-value option fields. With the dropdown open, start typing to jump the highlight to the first option that matches what you have typed. The current search text appears next to a magnifier glyph in the dropdown footer and clears itself after a short pause with no typing. Backspace erases the last character and Delete clears the search; pressing any arrow key ends the search and returns to plain navigation. While no search is in progress, Backspace and Delete clear all checked options.

Clicking an option in a multi-value field toggled it twice. A single click on an option in a checkbox-list (multi-select “set”) field checked it and then immediately unchecked it, so the click appeared to do nothing; if the mouse moved between pressing and releasing the button, two different options toggled. A click now toggles exactly one option, on release. Mouse and keyboard handling in these fields was reworked in the same pass.

“Save as…” on a document could silently do nothing. On machines with a restrictive Windows attachment-security policy, choosing “Save as…” for a document opened the file dialog but then saved nothing, with no error message. The shell security check - intended only to warn about risky files - was being applied before the file was written and treated a policy block as a silent cancel. The check now runs the same way it does when opening a document: a file the policy considers unsafe raises a prompt offering to save it anyway, while an ordinary document saves without interruption.

A saved document's file name could repeat its extension. When a document record carried its name with the extension already included, saving it produced a doubled name such as report.pdf.pdf. This affected “Save as…”, the multi-document save, and documents attached to an outgoing e-mail. The extension is now appended only when the name does not already end with it.

Copying a record could leave out a field named like a built-in column. Copying a record (Record.Copy / CopyTo) skipped any field whose name matched a system column - most often a customised status field - treating it as the built-in column and excluding it, so the copy came back missing that value. Such fields are now copied; only the genuine built-in system columns are skipped.

Opening an inspector could occasionally hang. When an inspector's VBA read a record value that was still being lazy-loaded, the UI thread could take the record's lock and then wait for the background load, while the load worker waited for that same lock to deliver the value - a deadlock that froze the application. The pending load is now drained before the lock is taken, and its result - the loaded value or a load error - is applied or surfaced rather than left unhandled.