Web Client Patch 7 (2026-09-03)

Version 8.4.0.20260903054500
Desktop integration 8.4.4.200

• The CLOB (rich-text) editor now supports editing the value of a placeholder. If an email is composed from a template, its placeholders are resolved to real values (a recipient's name, the sender's signature, and so on). In value mode, these resolved values are displayed as non-editable fragments, and such a value may now be changed directly in the editor. (CRM-1042)
• The CLOB editor now offers a “default image alignment” option. The alignment of newly inserted images may be set to left, centered, or right, and the editor automatically applies this alignment to every image added. The selected setting is stored per user together with all other user preferences. (CRM-1293)
• CLOB editors displayed without a toolbar now show a small arrow button in their top-right corner that opens the extended (maximized) editor. Previously, the only way to maximize such an editor was the F2 key, which was difficult to discover. (CRM-1433)
• Logging can now be configured through environment variables, which is convenient in containerized environments and for enabling diagnostics in production without modifying files. All variable names begin with PISASALES_WEBCLI_LOG_. ..._LEVEL_ROOT sets the root log level (INFO, DEBUG, and so on). ..._LEVELS sets levels for individual loggers as a comma-separated logger=level list. ..._DIR overrides the log directory. ..._STDOUT also writes the log to the console. ..._RECREATE re-applies the environment values to the logger configuration on the next start or configuration reload. The environment provides the initial configuration, and an administrator may still adjust logging at runtime on the admin page. (CRM-1444)

• Inserting a signature into an email no longer corrupts the editor state. When a signature was inserted into an existing HTML body, the editor could display a stray “ghost line”, and the caret became stuck. Signatures are now inserted cleanly at the cursor position. (CRM-973)
• The “Desktop” view is no longer invisible upon display. On a fresh session, the docked “Desktop”, “Browser”, or message view could open as a barely visible strip only a few pixels wide, and logging out and back in was the only available workaround. Such a view now always opens at a usable size. (CRM-1263)
• Closed CLOB editors are now reliably released from memory. A CLOB editor that was no longer in use could remain in memory after its form was closed, so a long session in which many forms with CLOB fields were opened could accumulate memory over time. Such editors are now cleaned up completely. (CRM-1434)
• The CLOB editor's toolbar now matches the application's visual style. Active toolbar buttons and the focus frame were rendered in the editor's own blue color. They now use the standard product colors. (CRM-1437)
• A custom logo now appears correctly on the exit / logout page. If a custom logo was configured, its image address was constructed incorrectly (the application path was included twice), causing the logo to fail to load. Built-in logos were not affected. (CRM-1443)
• The small “permissions” button on the login page is now more clearly identifiable. It displays a bell icon and a tooltip that explains its purpose (allowing desktop notifications), replacing the previous unlabeled smiley icon. (CRM-1452)
• Pressing F5 or Ctrl/Cmd+R while editing a CLOB field no longer reloads the entire page. The keystroke now refreshes the current form record, consistent with its behavior elsewhere in the application. (CRM-1474)
• Selecting text with the mouse in a multi-line text field now works correctly again in Firefox. Dragging across the text to select it had ceased to work in recent Firefox versions, rendering drag-based selection unavailable. Selection by dragging now behaves as expected. (CRM-1492)
• Navigating the rows of a table with the keyboard now updates the attached details form again in Firefox. After clicking a row and then moving through the table with the arrow keys, the selection moved, but the details form continued to display the previously selected row. The details form now follows the keyboard selection as expected. (CRM-1569)