Cumulative release for 11.3.x
Additional details:
ms-msdt) and elevation verbs (runas) outright, and lets ordinary web, mail, telephony, Teams, Slack and document-management links through unchanged. For a program or document that could be unsafe, the client now makes the decision itself rather than handing the launch to Windows: it checks the file against the Windows attachment and zone rules and, when those would warn, asks for confirmation through its own prompt - shown in your language and the same whether the file is being launched, opened or saved - in place of the Windows “Open File - Security Warning”. When the client runs with no user interface, such as an unattended automation, a flagged target is blocked outright instead of launched. The underlying Windows zone check is never bypassed. Administrators can tighten or loosen the behaviour per machine, including a no-prompt hard-block mode.%WINDIR%\Logs\Lime. The VBA setup, the setup program that starts the client after an update, and the update package for the Lime Maintenance Service write their logs there when they run with administrator rights. When they run without administrator rights, the logs stay under %ProgramData%\Lime\Setup.LimeMaintenanceService (events 1000 to 1003). Administrators can follow updates in Event Viewer.Application\UnsentDocumentsScanDelay (default 20 seconds).http: or https: in the database selection dialog, the client now keeps that protocol and also reads a database= parameter from the address. When a secure (https) connection to a server on a non-standard port fails because of the secure channel, the client asks before it connects over unencrypted http. Your answer is remembered for that server. While the connection is unencrypted, the login dialog shows a red footer and a warning icon with an explanation.Application.DisplayAlerts, so an unattended run no longer stops at a dialog that nobody can close. They also use the same dialog style as the rest of the client. The error window of the Template Manager is replaced by the standard client dialog, and its button that sent the error by e-mail is removed.alert() from a page in an action pad or web bar is now shown through the client. It follows Application.DisplayAlerts and names the page that showed it. An alert with empty text shows a standard text instead of an empty box. When a VBA call from a page fails, the message now names the VBA method, the error text and the error code.NOT IN conditions joined with OR, or two IN joined with AND over disjoint value lists; or any leaf arriving with an empty value list - now shows the affected leaves in the report's filter tree inside a dashed amber frame with an “(eliminated by optimiser)” badge whose tooltip names the rule that dropped it. For the operator-flipped pattern (same operator on both sides plus the opposite boolean) the diagnostic log adds an actionable hint such as “If the intent was to exclude both values, the surrounding group should be ALL OF (AND), not ANY OF (OR)”. The same collapse occurring inside a programmatically-merged filter (sub-filter fused into a host filter during evaluation) is logged at Info instead of Warning - the elimination there is an expected merge by-product rather than a usability problem.Application.RunEx — positive values mean foreground, 0 is normal, negative is background, and -10 or lower is idle. Existing scripts continue to default to normal.ORDER BY against non-nullable columns, and certain sub-filter null guards — now emit SQL that the optimizer can use indexes for. Expect noticeable speed-ups on the affected filter shapes.QueryTimeout now bounds total wall-clock duration, not just the backend command time. Filter QueryTimeout previously governed only the time the backend had to answer; the client-side wait — initial grace period plus the simultaneous-queries queue — was outside the budget. For short timeouts behind a busy queue the perceived wait could be many times the configured value, even when the backend itself completed within budget. The budget is now resolved once up front and applied both to the queue wait and to the resulting backend command timeout. When the entire budget is consumed before the request leaves the client, the user sees an explicit “Wall-clock timeout expired while waiting in the client-side query queue” message rather than a generic failure — distinguishable in telemetry and support from a server-side timeout. Sub-filter timeouts no longer extend the top-level budget.+ when more results were truncated at the server fetch limit); on the right, a glyph indicating where the current results came from — the field's preloaded option list, the local search cache, or a live server lookup. Hovering either area shows a tooltip with details and the relevant keyboard shortcut. When the cache produces no matches, the footer replaces the counter with an explicit hint that a server search is one keystroke away.File 2 sorts before File 10 rather than between File 19 and File 20. Fields backed by a fixed option list retain their curated order.Use relevance scoring for searching relations checkbox under Options → Misc ranks search candidates against a small set of signals — how recent the record's activity is, the position of certain option values (todo / SOS / history / document status), and whether the record is associated with the active user (responsible coworker, creator, or last editor). Off by default and stored per user. Intended for solutions where the obvious “best match” rarely sorts first alphabetically.ForceClose is 1.%, # or ?, and a web address built from an application name, could open the wrong location or not open at all. These characters are now encoded. Spaces and non-English letters are left as they are.NoLock client setting: set NoLock to 1 under Application\FileExtensions\*.* to disable it for every type (for example HKCU\Software\Lundalogik\Lime\Settings\Custom\Application\FileExtensions\*.*\NoLock = 1), or under Application\FileExtensions\<extension> for a single type such as docx.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.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.EnableInspectorFullTextSearch admin checkbox under Options → Misc. 11.2 behavior is restored: the bar shows on inspector cards only when the admin has opted in. The main window's bar follows the same capability check and stays hidden when neither the webclient integration nor server-side full-text search is available. Setting changes — the opt-in, the IntegrateWebClient / AllowWebClient toggles, or the server's full-text configuration — now reflect on every open inspector and the main window without needing to close and reopen anything. A new View → Bars → Search bar menu entry lets users hide the bar manually within the limits of the capability gate; the menu item is greyed out when no supplier is configured.NOT IN A OR NOT IN B was producing the wrong set. The simplification is corrected.active (value 0 = inactive) now compose the auto-include-inactive filter with the correct polarity. Classes using the legacy quit convention continue to work unchanged.document.fileextension — could fail with a misleading “is not a valid value” error from the backend after the first attempt failed. The internal resolver was caching the partial path it had walked before the error, so subsequent calls saw the cached prefix as a successful resolution and produced a condition that referenced the wrong column. The resolver now caches only after the full path resolves cleanly; failures stay failures, and the next call retries against current schema state.Record.Value with mixed-case field names works again. A regression introduced earlier in 11.3 caused Record.Value(“xyz”) (or any other case variant of a field name) to silently return nothing once a different field had been looked up first in the same record. Mixed-case lookups now work consistently regardless of the order they're made in.Field.Value = “Privat” bypassed the option-label lookup that Field.Value = Array(“Privat”) performed. Both forms now produce identical conditions.AfterSave or BeforeSave handler writing back to the record while the underlying record load was still in flight could deadlock the client until it was force-killed. The locking and async-load sequence is now coordinated so the handler proceeds without blocking.Controls.AfterSave handler calling Controls.Refresh() could deadlock against the still-running save flow. Refresh now defers correctly until the save flow exits and runs from there. A small set of related save-state tracking issues were addressed in the same pass.relationsingle field marked invisible-everywhere, the wizard's confirm step threw Item not found and aborted. The wizard now excludes virtual fields from its candidate field list — those fields were never assignable, so listing them was always a no-op (silent in 11.2, loud after 11.3's stricter field-list checks).-1 “fill remaining” indicator on a multi-line field (such as Notes / Anteckningar in History inspectors) regressed to only two lines in earlier 11.3 builds. They now extend to the bottom of the inspector, matching 11.2 behavior. Short notes display without scrollbars; longer notes that need a scrollbar still get a usable three-line pane minimum even when the inspector is heavily compressed.AllowWebClient is opt-in again. A regression caused AllowWebClient to default to enabled in the Misc options page; opening Options → Misc and clicking OK silently persisted it as enabled. The dialog default now matches the runtime opt-in design. The setting also moved from per-Windows-user (HKCU) to database scope, so admins can manage it centrally and stale per-machine values from earlier 11.3 builds are ignored.GetSettingInherited previously threw when Application.Database wasn't available - typical during early startup or after a disconnect - instead of falling through to the application-scope value. Missing database now means “no value at the database scope” and the lookup continues.Record.Copy / Record.CopyTo no longer moves or duplicates related records. Two distinct issues fixed: related entities reachable through any relation whose foreign-key column lives on the related side (virtual or not, single-link or multilink) were being reassigned to the new copy when saved, effectively moving them rather than copying — the source no longer loses its links. Separately, a 11.3-era deep clone branch for plain 1:1 link relations fabricated a phantom companion record on every copy; that branch is reverted to 11.2's no-op for the 1:1 case, so copying no longer creates extra related records the user didn't ask for.lime.exe. The original logo is restored. Users on machines where the icon cache had latched onto the wrong icon may need a one-time Explorer restart before the corrected icon shows up.Status alongside the built-in Status (System)), the dialog could open against the system field instead of the one the user picked from the column-header menu. The menu now passes the actual field reference instead of re-resolving by display name. The same fix applies to the explorer's view, filter, and Send-to menus, and to field pickers in the view-edit, filter-condition, and formula dialogs.is a dummy now log as an error rather than silently no-opping, and any inspector that does end up bound to a dummy now opens read-only so accidental edits can't be lost.Index out of range or a generic Invalid parameter error, with the inspector refusing to move to the requested record. The inspector's current-record position resolution is more robust against the case where the active item's stored position hasn't been renumbered against the explorer's sorted view, and a related validation step that was rejecting otherwise valid navigation targets has been corrected.%2520 instead of %20 and the link no longer resolved. The redundant second encoding is removed; the plain-text clipboard format was never affected.Record.Value lookup let writes such as rec(“dealstatus”) = x fail with Status (System) is read-only on classes that had both a built-in status field and a user-defined dealstatus field — the lookup was crossing the two during cache resolution. The lookup now keys on each field's own local name, so writes go to the field the script names and read-only system fields no longer absorb the write.