• The new Kanban view makes it possible to create, arrange, and move tickets as cards in customizable columns.
• With the new Euro-Office plugin, Office files can be viewed and edited directly from the ticket application, Drive, and the inventory.
• The new Messengers plugin connects Telegram, WhatsApp, Instagram, and Facebook Messenger channels to ticket processing.
• The new Calendar application brings together personal, shared, and external calendars and provides comprehensive appointment planning.
• The WebAPIs have been revised and expanded, including new interfaces for managing HelpDesk settings.
• The Task Planner offers new filtering options for ticket changes, support for rating ticket fields, and Auto Texts for system tasks.

• To prevent broken or slow resources (such as images in HTML or Markdown) from delaying report generation, short download timeouts have been introduced. This also applies to the BytesFromFile and TextFromFile functions. If you rely on external servers that are slow or under heavy load, consider increasing these timeouts.

• The Users and Groups WebAPI has been redesigned and is not backward compatible. Existing integrations must be migrated to the new request and response models. The users and groups base paths remain /usersandgroups/users and /usersandgroups/groups.
• User and group data that depends on installed field definitions is now exposed through the fields object. Update integrations to read and write these values by field key. Memberships are managed separately through the group-members endpoint.
• Updating an existing user or group uses partial-update semantics for both PUT and PATCH: properties omitted from the request remain unchanged. Do not rely on PUT replacing the complete resource.
• For details about the new API, see the WebAPI's swagger.json. The new endpoint /usersandgroups/user-fields is available when the WebAPI Core and Field Settings plugins are installed and requires the configuration permission. The remaining Users and Groups endpoints require the Users and Groups Manager permission.

• You can now change the values of the Subject and custom fields in bundled sub-tickets.
• The Tickets Dashboard widget is now highly configurable to support many features:
• Supports many new metrics such as the processing time of tickets (MTTR) or the percentage fraction of tickets which were resolved with one answer (FCR)
• Supports different aggregations such as average, median, sum, count and percentage.
• Supports the representations for single value, trend and ticket table.
• Supports a time window to dynamically take only a configured subset of tickets.
• Resources can now be deactivated and permanently deleted.
• Categories can be deactivated.
• Markdown files attached to tickets can be opened in the preview.
• For the automatic status change that occurs when a supporter marks a new ticket as read, the status can be changed now and the feature can be entirely turned off.
• Users get a notification when a ticket is shared with them (Share Ticket).
• Resources can be assigned a status message that appears in the interface when that resource is selected. This status can be set by any member with write access.

Fixed Bugs

• LDAP and JDBC user import errors now include the affected username in the log.
• Category names are now consistently trimmed in the configuration and HelpDesk settings WebAPI. Case and accents remain ignored for uniqueness, while hyphens, spaces, and other punctuation remain distinct.
• Saving the category configuration no longer incorrectly requires unrelated inactive categories to be activated when their database sender value is NULL.

• Can now import data into custom user fields.
• Administrators now receive notifications when user or asset imports fail with an error.

• Added a WebAPI for listing, inspecting, paging, and editing forms, including their folders, sections, conditions, fields, and submit actions.
• Forms and folder bundles can be exported and imported through the WebAPI with preview, fail, overwrite, and copy conflict handling.
• Added machine-readable Forms capabilities, dependency rules, examples, and references to canonical HelpDesk settings endpoints.
• Can now change the type of existing forms (Create Ticket, Modify Ticket, Notify Taskplanner)
• The form for changing a ticket can now send emails. These emails will appear in the related ticket.
• Can now use the operators "contains" and "contains not" for select-fields which allows multiple values.
• Form names can now contain up to 50 characters. Long start page form button names are shortened automatically.

• The new "Affected Assets" task series runs jobs and actions once for each affected asset of a ticket.
• The new "Set Asset Field" action supports editable standard fields and custom asset fields with the appropriate input controls.
• The new "Add Attachment to Asset" job and "Add Result as Attachment to Asset" action let you add files, folder contents, URLs, and file results from jobs as asset attachments.
• Approaching Asset Date task series now support configurable day, week, and month offsets with clearer earliest, latest, and closed date-range boundaries relative to task execution.

Fixed Bugs

• The Low/High Inventory task trigger no longer shows "null" for an empty asset query and now displays the validation message for negative asset counts correctly.
• Approaching Asset Date task series no longer show unresolved placeholders when the comparison mode is missing.

• Added copy buttons to the ticket-page Knowledge Base extension so supporters can copy article solutions, including embedded images, to the clipboard for pasting into the ticket editor.
• Added a Knowledge Base Web API for searching, reading, creating, editing, and deleting articles, including safe attachment metadata.
• Added a creation date field to articles.

Fixed Bugs

• Work-in-progress Knowledge Base articles are no longer shown in the ticket-page Knowledge Base extension, including for users with permission to edit and delete articles.
• Creating a Knowledge Base article with AI now fails with a clear error when the AI connection is unavailable instead of creating a regular article without AI-generated content.
• Task Planner actions for creating Knowledge Base articles now support multiple ticket IDs and resolve ticket category placeholders correctly for each article.
• Task Planner actions for creating Knowledge Base articles now offer all configured article languages and require a concrete language selection.

• Live Support: create unknown users from visitor email and keep the request text focused on the inquiry.

• Moved Login Domain maintenance functions to the core "Maintenance" plugin.

• Added the new "Messengers" plugin, which connects Telegram, WhatsApp, Instagram and Facebook Messenger channels to the ticket processing.
• Incoming messenger messages open or update tickets in the matching ticket channel, including texts and attachments.
• Added the ticket action "Messenger Reply" for answering messenger requests directly from the ticket, including attachments.
• Reactions to sent messenger messages are recorded in the ticket as user comments.
• Added user fields for the Telegram, WhatsApp, Instagram and Facebook IDs, so that messenger senders can be matched to HelpDesk users.
• Added the option to configure an auto-reply that confirms ticket creation to the messenger sender, including a placeholder for the sender email address.
• With the AI plugin, messenger requests are answered by the AI first and can be handed over to a human supporter on request.

• Added WebAPI support for listing, inspecting, importing, exporting, and updating ticket processes, including folders, activities, transitions, parallel tickets, and editor metadata.
• Automatic connections between activities now also trigger in a closed ticket.
• Corrected validation of automatic connections with ticket value conditions.
• Can specify the close-action to apply on parallel tickets when the main ticket is completed or the process is left.

Fixed Bugs

• Fixed an error message stating that a ticket was already closed when the action performed was intended to close the ticket via an automatic transition.

• If errors occur when applying Quick Tickets in the Task Planner, the name of the problematic quick ticket will now be included in the error message.

Fixed Bugs

• Tasks created from the "Create Ticket Before Asset Expiry" template now display the asset expiry condition correctly before the task is edited for the first time.

• Added a new ticket step action to assign a ticket owner from the request step. The action can reuse an existing user found by email or create a new user if needed.
• The ticket action "Termin vereinbaren" offers a checkbox to send a calendar invitation (.ics file) via email to the ticket owner. Requires the Calendar plugin.
• AI answer suggestions for email replies now generate only the answer body (without greeting or sign-off) and insert it directly at the signature cursor position. If the signature template does not contain {cursor.position}, the system now determines a suitable insertion point, adds the cursor placeholder there, and reuses that template position for answer insertion.
• Links to ticket steps can be copied and shared.
• Ticket processing steps with text content can be translated using providers from the active Translations plugin. Stored translations can be switched by language or deleted; the original ticket content remains unchanged.

Fixed Bugs

• Improved and deepened AI answer suggestions which are sourced from other tickets.
• In the "New Ticket" dialog, fields that were once mandatory could not be hidden.

• Task Planner: Status change triggers can now filter by text contained in the action step that caused the ticket change.
• Added the ability to filter for and set ticket rating fields.
• Auto Texts can now also have the Application Area "Task Planner (System Tasks)", which means they can be selected for the "Add Auto Text" job for system tasks in the Task Planner.
• Task Planner: Resource statuses can now be set by actions, including resources and status texts supplied through placeholders.

Fixed Bugs

• The "action.user" placeholder in tasks triggered by ticket actions now correctly resolves the action's user's display name.
• In the "Run Formula" job, placeholders in the optional condition value are now resolved correctly before comparison with the formula result.
• Saving a "Run Formula" job without entering a formula no longer causes a null pointer exception.
• The "Add Users to Ticket Sharing" action now shows "Access Type" as the field label and "Read and Write" as the write option label.
• Manually running a task containing an Add Text To Request action would cause the endless loop detector to throw a false alarm.
• Task Planner tasks triggered when a ticket deadline was exceeded could be executed twice.

Fixed Bugs

• The AdHoc AI assistant completes selected follow-up actions directly, instead of only describing the next step.
• The AdHoc AI assistant now uses the current report structure after manual report changes when adding new components.

• Added a dedicated AI Web API extension under /api/ai with endpoints for providers, requests, resources and configured skills.
• Added an OpenAI-compatible chat completions proxy at /api/ai/chat/completions and /api/ai/v1/chat/completions that forwards to the configured default provider.
• Added provider selection by unique provider name for AI requests and resource uploads, while still supporting the configured default provider.
• Added the new permission ai.api for AI Web API access, including Web API help integration and permission labels.
• Added configurable AI slash commands for the CoWork bot, including provider selection and command-specific system prompts; adding, renaming or deleting commands updates CoWork command availability accordingly.
• Added the ability to determine the desired response format of a Task Planner AI Query Job: Plain Text, HTML, or Markdown.
• Added per-job AI tool selection to Task Planner AI Query Jobs. Only tools selected for the job and enabled in the Task Planner AI settings are provided to the request.
• Added TypeSafe Jev support, including a Jev job for the Task Planner and AI configuration for the encrypted API key and configurable base URL. Jev is TypeSafe's decision model: it evaluates natural-language context and returns structured choices, scores or yes/no probabilities that software can use directly, instead of generating prose. It can support semantic workflow steps such as classifying or routing tickets, checking conditions and ranking relevant knowledge base content.

Fixed Bugs

• Added handling for tools such as AI Triggers which have spaces in their names.
• The AI Query job in the Task Planner no longer allows empty request texts.
• The AI Trigger's placeholders are now offered to subsequent task components.
• The "Classify Ticket with AI" action now reports missing AI configuration instead of a misleading error message.
• Added connection and read timeouts for AI communication to prevent potential system hangs if an AI provider stops responding.

• AI Websource automatically detects sitemap.xml and sitemap.txt and displays the last detected crawl mode in the URL editor.

Fixed Bugs

• Removed web sources are no longer crawled again from cached URLs, and their cached index entries are deleted.

• The calendar application supports planning and managing appointments in personal, shared and external calendars:
  • Appointments are displayed in year, month, week and day views, complemented by a mini calendar and full-text search
  • Own, shared and external calendars (ICS, CalDAV, Google, Outlook) are consolidated in one place with automatic synchronization
  • Appointments and recurring appointments with reminders can be created, edited, moved and deleted
  • Calendars can be shared with read, write or administrator permissions for users and groups
  • Calendars can be subscribed to via ICS, CalDAV and WebCAL URLs in other calendar programs such as Outlook, Google Calendar or Apple Calendar
• The calendar trigger in the Task Planner can filter events.

• Implemented the modern SRTP profiles SRTP_AEAD_AES_256_GCM and SRTP_AEAD_AES_128_GCM.
• The user status is no longer set to idle while in an active call, even if the client is minimized or the screen is locked.
• The screen stays awake on mobile devices during an active call, preventing the microphone from losing input due to screen timeout.
• Added a dedicated call test page for testing audio and video devices as well as the connection before joining a call.
• Whether a transcript is active is now displayed for calls in which the user is not an active participant.
• OVHcloud, Gladia, Mistral AI, and custom OpenAI-compatible endpoints can now be used for call transcription.
• A setting can prefer H.264 for camera video and screen sharing. Compatible clients can thereby use hardware acceleration and reduce CPU load; if H.264 is unavailable, the entire conference automatically falls back to VP8.

• When joining a meeting room, testing the audio settings now also automatically verifies the connection to the server.
• Meeting rooms can specify an optional date until which the room is valid. After that date, the room is automatically deleted.

Fixed Bugs

• The DeepL job now shows a dedicated validation message when the API key is missing. The target language field now defaults to EN-US.

• When an outgoing mail server is not configured, the contact support page now includes a link into the SMTP configuration page.

• Microsoft OneDrive in Office 365 can be connected to Drive as an external storage location. Users can access and manage their OneDrive files and folders directly in Drive, including creating folders, uploading and downloading files, renaming, copying, moving and deleting. Larger uploads and preview images for supported files are available as well.
• Error handling for Dropbox has been improved.
• 7 widgets and a sample dashboard have been added. (Broken links, event logs, share links, largest files, folder statistics, storage space and shortcut)
• Admins can now view the size of folders and their contents in the UI.
• Delete is now available upon multiselection in the search view.

Fixed Bugs

• File sharing via anonymous links has been fixed.
• Deleting Link Root must work even if the target is no longer accessible.
• When a user is deleted, their connections are now deleted as well.
• Prevents storage issues when dealing with a very large number of very large images.

• Office documents attached to inventory devices can now be opened and edited via the EuroOffice integration.
• The optional document server URL fields show the effective fallback URL as placeholder once a document server URL is configured.

Fixed Bugs

• Office documents in Drive that are shared with a single user can now be opened and edited.

Security Fixes

• Editor sessions are now bound to the user's HelpDesk session and expire after a period of inactivity (at most after 24 hours).

• The help now provides WebAPI endpoints under /api/help to search for help pages and to retrieve help pages as HTML or Markdown.

• Messages can be marked with a star and accessed later from a central list in the global navigation.
• Custom statuses are easier to reuse: recently used status combinations are shown as presets in the status menu, and selected statuses can also be saved permanently as presets.
• Long text file previews with a "Show More" option also provide a line wrap toggle, so you can switch between horizontal scrolling and wrapped lines.
• System messages in the channel provide information about relevant changes, such as title changes or added users or groups.
• Messages can be searched for using a message ID or message link.

Fixed Bugs

• Reports can be opened from links in Drive.
• Switching between Drive entries with the same URL now displays the selected user's Home folder.

• Added Login Domains Maintenance functionality for adding, removing, and renaming login domains.
• Added the ability to stop and remove an incomplete restore of a backup which encounters a fatal error.

• DOCX files from different Microsoft Office versions and third-party applications are interpreted more completely, including ISO Strict documents and alternative Office content.
• Footnotes and endnotes are included in page layout, with support for continuation pages, numbering restarts, section placement, and references inside tables.
• Documents with right-to-left, East Asian, and Southeast Asian text benefit from improved font selection, text ordering, alignment, line breaking, and script-specific formatting.
• Automatic hyphenation and discretionary hyphens provide more natural line breaks while respecting the document language and paragraph settings.
• Additional section settings are supported, including vertical alignment, text direction, column separators, line numbering, document grids, mirrored margins, and page-border placement.
• Page counts, chapter-prefixed page numbers, running headings, and document-property fields are calculated from the final document layout.
• Complex tables support more Word formatting, including inherited styles, conditional formatting, automatic and fixed widths, merged cells, repeating headers, nested tables, and multi-page rows.
• Pictures and modern or legacy Microsoft Word drawings retain more of their original crops, colors, effects, grouping, text, positioning, and wrapping.
• Large or complex documents are processed more reliably. Invalid content is isolated where possible, and a cancelled or failed operation does not publish an incomplete result.

Fixed Bugs

• DOCX documents use fonts from the configured font directories, including their actual bold and italic faces. Missing fonts use document font hints and improved fallback preferences for consistent text and space widths.
• Corrected exact and minimum paragraph line spacing to match Microsoft Word.
• Improved CJK line breaking and justification to avoid excessive gaps at text run boundaries.
• Corrected fallback font metrics for CJK text to prevent compressed or overlapping lines.
• Preserved vertical VML text when it is split across multiple text fragments.
• Malformed VML text-path font declarations could cause excessive parsing times because of regular-expression backtracking.
• Nested tables could abort when moved to the next page, and words split after a tab near the right margin could start on the wrong line.
• Documents with merged table continuations, page relayout around anchored drawings, or tab stops beyond the text area could fail to finish parsing.
• Text without a font declaration could use an unrelated system font, changing spacing and table breaks.
• Missing Helvetica, Helvetica-Bold, Madame Cosmetics, Aparajita, and AdvLTe50259 fonts could use unsuitable condensed replacements.
• Nested DrawingML shape groups could lose child offsets or use incorrect scaling, reflection, and rotation.
• Stale first-row cell widths could shrink an otherwise coherent AutoFit table grid.
• Anchor-only paragraphs with minimum line spacing could add extra vertical space, and text following a full-width square-wrapped anchor could jump above it.
• Body anchors inside tables could paint in the wrong order relative to other page anchors.
• Word 2010 text outlines and shadows could lose their colors, transparency, geometry, and inherited formatting.
• Downward-arch WordArt could remain flat, including text in rotated shapes and text with outline or shadow effects.
• Direct vertical cell margins could be omitted from minimum row heights, and contextual spacing between same-style paragraphs could be ignored inside table cells.
• DrawingML flowchart delay symbols could appear as rectangles.
• Some documents could lose individual characters at automatic line breaks, show unwanted spaces in fields, or ignore spaces that were deliberately preserved.
• Paragraph borders could be missing, doubled, or repeated incorrectly across pages, columns, and table cells; paragraph shading and framed paragraphs could also differ from Microsoft Word.
• Complex paragraph spacing, indents, tab stops, manual breaks, and keep-together settings could place text on the wrong line, column, or page.
• Hidden text could remain visible, while small capitals, highlights, double strikethrough, shaded spaces, and underlined trailing spaces could be displayed incorrectly.
• Adjacent text with different font details could be combined and displayed with the wrong font or character spacing.
• Documents that combine Latin, Asian, and complex-script fonts could select the wrong font face or use an incorrect line height; regular text could occasionally appear bold.
• Right-to-left and Asian text could show incorrect character order, punctuation placement, tab alignment, list-marker alignment, or line breaks across formatted text.
• Soft hyphens and automatic hyphenation could disappear, become visible without a break, or choose unsuitable line-break positions in paragraphs and tables.
• Missing, cyclic, or incompatible paragraph, character, numbering, and table styles could discard valid formatting or stop the document from rendering.
• List numbering could start or restart incorrectly, display invalid placeholders, use the wrong format or indentation, or fail for large and incomplete numbering definitions.
• Table widths, column grids, AutoFit calculation, floating-table placement, negative indents, and intentionally wide tables could differ significantly from Microsoft Word.
• Table styles could lose inherited or conditional formatting for text, alignment, spacing, cell margins, borders, and preferred cell widths.
• Merged cells, exact or minimum row heights, non-splitting rows, repeating headers, and table continuations could produce missing content, incorrect borders, or wrong page breaks.
• Nested tables, hyperlinks, content controls, SmartTags, and tracked changes inside table cells could lose visible content or appear in the wrong order.
• Anchored pictures and shapes could overlap text, move to the wrong page, use the wrong reference position, or disturb alignment and tab stops in surrounding text.
• Odd- and even-page section starts, continuous sections, mirrored layout, page borders, columns, headers, and footers could use the wrong page or position.
• Page counts, page-number restarts, running headings, dates, and other fields could show stale values, unwanted spaces, or incorrect results in headers, footers, and text boxes.
• Footnotes and endnotes could remain on the wrong page, be repeated, reserve too much space, or be separated from references that moved during pagination.
• Pictures could lose crops, rotations, reflections, borders, colors, or transparency effects, and some embedded images could fail to load.
• Grouped shapes, text boxes, WordArt, gradients, image-based outlines, horizontal rules, and other legacy drawings could be positioned, scaled, colored, or wrapped incorrectly.
• Invalid page-number values, malformed formatting, damaged embedded fonts, or missing optional document parts could produce wrong output, repeated layout attempts, or abort the complete document.
• In some affected documents, tables could be shifted from their Microsoft Word position and individual images could be omitted.

• PDF streams are limited to 1GB.

• Text editor: Added style transfer for text and code formatting blocks. Added strike-through text style.

• Implemented fixed currency symbols for email output and resolved related bugs in other output formats.
• Support for ISO-8601-like date time formats in the 'date' formula function.
• Added support for report paths using the 'drive:' protocol in the 'Report Data' data source.
• Added support for odt (LibreOffice Text), facturx, and peppol (electronic invoicing, plugin required) renderer formats. These formats can be used via the URL parameter init=<format> as well as the API new Engine(format).
• Added connection and read timeout settings for external resources such as images, CSS, BytesFromFile, and TextFromFile.

• Advanced HTML now supports SVG rendering.

• The bundled Eclipse Temurin Java VM was updated to version 25.0.4.

Fixed Bugs

• Field type "rating" now correctly uses the client's locale for display values instead of only the server locale.

Security Fixes

• Stay-logged-in cookie values are now masked in log files.
• Enhanced the Stay-logged-in cookie check to validate the operating system and browser of the original session. Cookies are now restricted to the same OS and browser combination, while seamlessly supporting browser updates.

• Added a "Definitions" context to the Task Planner Web API that provides read-only information about available triggers, jobs, series, and result actions. Each component type lists all available components with their IDs, names, and descriptions. Individual component details include an example JSON representation for use with the task import API.
• The execution information (history) for a task is now stored separately from the task data. This reduces the load on the server, especially when a large number of tasks need to be executed all at once. If you want to back up this separate execution information, you can use the new "Execution History" backup option in Maintenance.

Fixed Bugs

• The "After Task" trigger now blocks circular task dependencies (for example, "Task A after Task B" and "Task B after Task A") during validation to prevent endless execution chains.
• System tasks are now synchronized correctly between multiple cloud nodes after they are created or changed.
• Removed unnecessary error stacktrace logging for tasks that were unable to run for valid reasons.

Fixed Bugs

• Fixed the 2FA title showing plus signs instead of spaces in apps like Google Authenticator on iOS.

• Added a Task Planner trigger for newly created users.
• Added a Task Planner trigger for changed user data.
• Added a Task Planner trigger for deactivated, reactivated, or fully deleted users.
• Added a Task Planner series for iterating over users.
• Added a Task Planner action for setting user field values.
• Can set an avatar for each group.

Fixed Bugs

• The Task Planner action "Set User Field" was not correctly setting values for checkbox user fields.

• SSL certificates with EC/ECDSA private keys can now be used in the configuration upload and Web API certificate upload.
• Support for creating Let’s Encrypt certificates via the DNS-PERSIST-01 challenge has been added, making it ideal for internal systems that are not publicly accessible from the internet.
• Added option to disable HTTP/2. This can help with certain reverse proxies that have buggy HTTP/2 implementations.