Back to resources

Release Notes

New features, improvements, and fixes from each release of e! by Lexemo.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • Four new layouts are available for the forms your users fill in: Conversation, Workspace, Motion and Flow. Alongside them, new appearance settings let you adjust the background, font, corner radius, spacing, content width and animations, and choose how loading is shown: a minimal indicator, a branded screen, or a detailed view with your own loading messages. The settings preview shows the real layout as your users will see it. Animations are reduced automatically for users who have turned down motion on their device. Existing layouts keep their look, and the layout you have already chosen for each bot is kept.

  • The Azure OpenAI models have been upgraded to the GPT-6.1 generation, replacing GPT-5.6 luna, terra and sol, for better results from AI agents.

Improvements

  • When you delete a bot, the dialog now makes clear whether you are deleting a single version or the entire bot.

  • Files that exceed the upload limit are now rejected right away, instead of being uploaded completely before the error appears.

Bug Fixes

  • Fixed a security issue where a user with access to a bot could open or change another user’s run of that bot if they knew the run’s ID. Runs are now only accessible to the person who started them, to bot viewers, and to users with reporting access.

  • Fixed a security issue where the client secret of a single sign-on configuration could be included in the data loaded for user groups. It is no longer sent to the browser.

  • Fixed an issue where a completed run could turn back into a draft and disappear from “See Data” if the result page stayed open for more than a minute after submitting. Note: runs that were affected before this fix are not restored automatically. If a completed run is missing from “See Data”, contact support.

  • Fixed an issue where a bot could no longer be saved after a text field in a Send & Result node that contained a reference to another node was switched off.

  • Fixed an issue where date fields rejected every date for users in time zones behind UTC, for example in North and South America.

  • Fixed an issue where table content could be missing from generated PDF and Word documents when the table’s columns had been resized in the editor.

  • Fixed an issue that made the document generation service restart every few hours under heavy use, which could cause document generation to fail or take longer.

  • Knowledge bases now accept CSV files that use semicolons as separators, such as exports from German Excel. If a file cannot be added, the actual reason is now shown instead of a generic error.

  • Fixed an issue where the commercial register (Handelsregister) company search failed for companies with name or location changes in their history.

  • Fixed duplicate or flickering scrollbars in the Pipeline and Compact layouts, for example when switching layouts or when a long result is shown.

  • Fixed AI agents on Azure OpenAI that failed on every request with the newest models, and fixed PDFs failing when “parse as image” was used with Claude models.

  • Fixed an issue where the data analysis for machine learning nodes no longer warned about input columns that duplicate each other.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • When you duplicate a bot, its “See Data” settings, such as renamed columns and other display settings, are now copied to the new bot as well. Previously you had to set them up again on every copy; they now carry over the same way they already do when you create a new version.

Improvements

  • The bot template library has a refreshed design with updated animations.

  • Gemini 3.1 Pro is no longer available. AI Agents that used it have been switched to Gemini 3.8 Flash automatically, so no action is needed on your side.

Bug Fixes

  • Fixed an issue in forms where a step that maps data into variables could finish too late, so a condition directly after it briefly took the wrong branch and showed the wrong content. The form now waits until the mapping is complete before deciding which path to follow.

These updates have completed testing and will be deployed to production in the next release.

Improvements

  • Generated DOCX and PDF documents from a completed run now stay available for download for as long as the run exists, without the workflow having to be processed again in the background.

  • Documents and uploaded files created on a path you later abandoned, for example after going back and changing an earlier answer, are no longer kept or offered for download once the run is completed. Only files that belong to the final path of the run remain available.

  • Dates and times in the data report, such as run and approval dates, are now shown in your local time zone instead of UTC.

  • The template library now loads faster, because it only fetches the information needed to display the template cards.

  • Bots that use clauses from the Clause Manager now run faster, especially for companies with a large clause library.

Bug Fixes

  • Fixed an issue where the Account Members page could not be used at all when opened through the “Manage Users” menu: no buttons, fields or icons on the page responded to clicks.

  • Fixed an issue where AutoMate could not generate bots that include Clause Manager nodes.

  • Fixed an issue where an API connector could not send a file as its request body when that file came from the response of another API connector earlier in the same run.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • A new “Template Builder” role is available for company admins to assign. Template Builders can browse and use the existing bot template catalog and edit bot content, but cannot create blank bots from scratch or edit a bot’s underlying workflow structure — useful for giving less technical team members safe, limited access.

  • API Connector requests now omit optional URL query parameters entirely when they have no value, instead of sending them as empty (for example filter=), so connected APIs that distinguish between “not provided” and “provided but empty” now behave correctly. Note: static (non-variable) parts of a connector’s URL path can no longer be blank or whitespace-only — this was previously accepted silently but is now rejected with a clear validation error when you save the connector.

  • The default Gemini Flash model has been upgraded again, to Gemini 3.8 Flash, bringing further improvements in speed and output quality.

  • You can now set your own maximum file size and maximum total upload size for each File Upload node, instead of relying on one fixed limit for every bot. Limits are enforced as soon as an upload is attempted, with a clear message if a file is too large.

Improvements

  • AutoMate is now more selective about which examples it references when generating nodes and bots, improving the quality and relevance of what it builds.

  • Consumer-facing bot and API connector views now show a loading indicator while data is being fetched, instead of briefly flashing an incorrect “nothing found” message.

Bug Fixes

  • Fixed security issues that could, under specific conditions, allow an API connector to be executed by a user, automation, or AI agent that wasn’t actually authorized to use it — including across different companies. All connector executions are now properly verified before they run.

  • Fixed a critical issue where a scheduled bot run could crash the entire application if it reached an AI step that no longer had an AI agent configured. Scheduled runs that fail this way are now handled gracefully, and the schedule is paused after repeated failures, just like any other error.

  • Fixed an issue where emails sent by bots through Microsoft mailboxes were no longer being saved to the sender’s “Sent Items” folder, even though delivery itself was unaffected.

  • Fixed several issues with “Add to Statistics” and bot duplication where reusing files from a previous run or a duplicated bot could corrupt previously stored files or show incorrect file dates. Note: loading a file that’s expected to be unique — such as a company template, bot logo, or generated document — will now show a clear error if duplicate records exist for it, instead of silently picking one as before. A cleanup step automatically removes known duplicate company template records; if the error appears elsewhere, contact support.

  • Fixed an issue where generated DOCX and PDF documents could show an unwanted black line or empty row above an otherwise borderless table.

  • File downloads that don’t include a filename (for example, some Microsoft Graph responses) now get a sensible default name instead of failing.

  • In Clause Manager, deleting an individual clause version versus deleting the entire clause are now handled as clearly separate actions, and deleting a clause or version no longer leaves behind orphaned tags or placeholders.

  • Fixed an issue where the placeholder text configured for a Text Area field was not shown to end users filling out a form.

  • Fixed an issue where the classic design showed “Next ->” instead of “Send” as the label for the final submit action.

  • Fixed an issue where a chart showing values by date displayed each date as a separate point instead of grouping them by day, making trends hard to read.

  • Fixed an issue where reviewing a run from a standard (non-Pro) AI agent could break the run debugger view.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • Place individual variables anywhere in your Word templates. DOCX and PDF creation nodes now offer a second content mode alongside the editor: single template variables. Instead of pushing all content through one block, you can map bot variables to your own tags and drop them exactly where you want them in an uploaded Word template, inline inside a sentence or as standalone content with its own paragraphs. This gives you far more control over the layout of generated documents. The template variables dialog lets you create tags, copy them individually or all at once, and add several variables in one action. Switching between modes or swapping the template never discards your mappings. Alongside this, document rendering has been reworked and made more accurate, so complex existing templates may look slightly different than before and are worth a quick review after the update.

  • AutoMate now shows text as it is being generated, instead of making you wait for the complete response. Long-running automations give you visible progress from the first moment, and cancelling or navigating away mid-generation is handled cleanly.

  • The AI models behind AutoMate and the AI Hub have been upgraded. AutoMate and AI Portals now run on Gemini 3.7 Flash, and the OpenAI and Azure OpenAI options have moved to the GPT-5.6 generation (terra and luna), with the new GPT-5.6 sol model added as an additional choice.

Improvements

  • Messages about inputs that might be missing in a template are now shown as warnings rather than blocking errors, so they no longer stop you from saving your configuration.

  • Action icons on workflow nodes, including delete, copy, paste and path actions, now show tooltips explaining what they do.

  • The application handles busy periods more efficiently, reducing delays on requests when many people are working at the same time.

  • Date fields now clearly reject an invalid or malformed date entry instead of silently accepting it and storing an incorrect date. Note: if you previously relied on an invalid entry being accepted, you will now see a validation message and will need to correct the date.

Bug Fixes

  • Fixed an issue where the option to generate an image for a plan disappeared even though no image had actually been created, leaving you unable to try again. You can now retry image generation after a failed or interrupted attempt.

  • Fixed an issue where cancelling an AutoMate action and immediately starting a new one could interfere with the new request, causing stray error messages or a loading indicator that cleared too early.

  • Fixed an issue where chatting with an AI agent that had no knowledge sources attached could fail to return a response.

  • Fixed an error when reprocessing a completed run, for example through “Add to Statistics”, if the run included a file upload step connected to a file collection.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • You can now schedule bots to run automatically and unattended on a recurring basis — daily, weekly, or at a set interval. Set up and manage schedules directly from the bot card using a visual, color-coded time-slot picker that shows company-wide availability, and account admins get a dedicated dashboard with usage stats across all scheduled bots. Note: only published bots that support bulk (CSV) processing can be scheduled, and any required input the bot needs — such as an email field without a default value — must be satisfied for the bot to stay eligible. Existing scheduled bots that no longer meet this after being republished will have their schedule automatically paused until the input is resolved.

Bug Fixes

  • Fixed several issues in the bot scheduling experience: the schedule indicator on bot cards now only reflects whether a bot has any schedules, and no longer changes unexpectedly when a bot is published, unpublished, or edited. Turning a schedule on or off now shows clear loading feedback without flickering, and other controls are disabled only for as long as needed.

  • Fixed an issue where the Microsoft integration’s connection status could show as needing reauthentication even after a successful manual or automatic refresh, which could cause requests to fail. Refreshing your Microsoft connection now reliably keeps it active.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • File nodes can now output the names of their files as text, so you can build logic conditions that branch based on which files are present. The output is a comma-separated list of file names; an empty file collection produces an empty text value.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • You can now open the Release Notes directly from e! — a new menu item takes you straight to the release notes page in a separate browser tab, so you can catch up on the latest updates without leaving your current work.

Bug Fixes

  • Fixed a critical issue where workflow steps that call an external API with an optional file attachment would fail the entire run if no file was provided. These steps now complete normally whether or not a file is included.

  • Fixed an issue where account administrators could not see bots that other administrators had added to a shared user group. Bot access for user groups is now visible and manageable by any administrator in the company.

  • Fixed a display issue in multi-section forms where navigating past certain sections could briefly clear the progress indicator and section highlights. Your position and progress now stay accurate as you move through the form.

  • Fixed an issue in the variable mapper where declining the confirmation for “Remove unused” would still delete the unused variables. Cancelling now correctly leaves all variables in place.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • API Connector now supports multipart/form-data requests, including file fields. You can connect to APIs that require file uploads or a mix of structured form fields and files.

  • Runs now save automatically. Your progress is preserved about once a minute, so you no longer lose work if your browser closes or a session ends unexpectedly. Resuming an auto-saved run works exactly like resuming one you saved yourself.

Improvements

  • AutoMate file uploads are more reliable. Supported file types (txt, PDF, JPG, JPEG, PNG) are accepted, unsupported files now show a clear error instead of being silently dropped, and you can attach up to 20 files in one go. New per-user and per-conversation upload limits keep usage in check, with clear feedback when a limit is reached.

  • Clearer wording when editing in AutoMate. Editing prompts now consistently use the term “modify” throughout for a more predictable experience.

  • The Run Debugger window is easier to reposition. You can now drag it from anywhere along its title bar, and it stays visible after you move it.

  • Strengthened security around uploaded image files.

Bug Fixes

  • Fixed an issue where the SharePoint connection would stop working after a period of time. It now refreshes in the background and stays connected without needing to be set up again.

  • Fixed an issue in the Report view where reloading a previous run and resending it without changes could send incorrect values (such as 0) for number fields. Reloaded values are now preserved on resend.

  • Fixed an issue where the CSV multi-process preview only showed the first 10 rows. You can now see all runs both before and after starting.

  • Fixed an issue where statistics and data reports could fail to load or time out for bots with very large run histories. These reports now load reliably.

  • Fixed an issue in AutoMate where the full bot was not automatically included as context after new nodes were added. Follow-up prompts now correctly apply to the current bot.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • A new AI model, Perplexity Sonar Deep Research, is now available for selection, giving you an additional option for in depth research tasks.

Improvements

  • AutoMate and the AI Agent now run on the latest Gemini 3.5 Flash model, bringing better speed, output quality, and consistency across AI powered features.

Bug Fixes

  • Fixed an issue where editing a bot in AutoMate could break its logical conditions and prevent it from being saved. Bots with branching logic can now be edited and saved reliably.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • You can now trigger multiple runs at once by uploading a CSV file. Each row in the file starts a separate run, with each column mapped to an input field, so you no longer need individual files to process work in bulk.

  • Working with large workflows is now much easier. A new multi-node mode lets you keep several nodes open at the same time, toggled via the Open Nodes panel or the Ctrl/Cmd + M shortcut. Holding Ctrl/Cmd while clicking a node still opens it alongside the others as a quick shortcut.

  • Logic Condition nodes now have an expand/collapse toggle that opens or closes all of their nested steps in one click, instead of opening each child node individually.

  • Agents can now use your configured API connectors as tools, allowing them to fetch and act on data from connected systems during a conversation. Note: this is the first stage of the capability, so expect it to expand in upcoming releases.

  • Added authentication support for the advoware integration, enabling secure connections to the advoware practice management system.

Improvements

  • Runs no longer stop completely when an email-sending step fails. The run now continues with the remaining steps and finishes with a clear error status, and the run log records each stage of the email delivery so you can see exactly what happened.

Bug Fixes

  • Fixed an issue where the source document viewer failed to load PDFs, and where clicking a source passage did not highlight the matching text in the PDF, particularly in documents containing umlauts or special characters.

  • Fixed an issue where agent execution logs were unavailable when a knowledge base search failed during the run. Logs now remain accessible so you can see what happened.

  • Fixed an issue where the agent tool selection listed tools from other organizations. You now only see your own company’s tools.

  • Fixed an error that prevented the User Details window from opening in Company Members settings.

  • Fixed an issue where the search bar on the See Data page loaded endlessly and never became usable.

  • Fixed an issue where file and image uploads failed when processed with certain AI models.

  • Fixed an issue where background colors of table cells were removed from rich text content.

  • Fixed an issue where document generation runs could fail due to font styling in rich text content. Note: custom font-family styling is no longer carried over into generated documents; standard formatting is unaffected.

  • Fixed an issue where logic conditions could keep an invalid order until they were opened, and where conditions opened at the same time received the same position.

  • The clause preview now opens in a centered, read-only window instead of taking over the full screen, and no longer shows an unnecessary confirmation prompt.

  • Fixed a layout issue in the Branding tab where the allowed file types text could overlap the upload label on narrow screens.

This update has completed testing and will be deployed to production in tonight’s release.

Bug Fixes

  • Fixed broken highlighting in the PDF viewer.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • The Send & Result node now has a toggle that lets builders skip the waiting screen in the consumer frontend. When activated, consumers see the success page immediately after submitting, while any subsequent workflow or AI output nodes continue running in the background. Note: if downstream nodes produce files or other consumer-facing output, those artifacts will not be visible to the consumer when this toggle is on.

Improvements

  • In AutoMate, the bot plan editor now uses a single Execute button that saves your latest prompt edits and runs them in one click, replacing the previous split between separate Send and Execute actions.

Bug Fixes

  • Fixed an issue where custom Azure OpenAI portals were using the default Azure endpoint instead of the endpoint configured in the backend, which caused AI output nodes to fail with a permission error.

  • Fixed an issue where adding or removing tags on a clause did not update the clause card until the page was refreshed. Tag changes now appear immediately after saving.

  • Fixed an issue where unpublishing a bot did not update its status in the bot overview. The published indicator now reflects the change right away.

  • Fixed an issue that prevented the login screen from rendering correctly in some configurations.

  • Fixed an issue in the text editor where, when two editors were placed in the same section, the fullscreen action always opened the second one regardless of which was clicked.

  • Fixed an issue where saving a standard agent required two clicks before changes were properly persisted and the unsaved changes prompt would no longer appear.

  • Improved how pasted content from Word is preserved in the consumer frontend, so tables and formatted text retain more of their original styling.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • Bot templates have a refreshed design that makes browsing and selecting templates easier and more visually appealing.

  • Newly created bots now start in pipeline design mode by default, giving you the modern layout right from the beginning. Existing bots are not affected.

Improvements

  • The preview button on bot templates now works for every user, regardless of who originally published the template.

Bug Fixes

  • Fixed an issue where the variable mapper would fail when an external service returned a time value that included seconds. Times are now handled cleanly without needing manual workarounds.

  • Fixed an issue where logic conditions using clause input could lead a run into an unexpected path or appear to do nothing. Clause input is now validated correctly and the chosen path is reached as configured.

  • Resolved an error that could cause the AI engine to fail while processing tool results in certain edge cases, leading to a failed run in the bot.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • The search in the navigation modal now searches within node content as well, not just node names. This makes it much easier to find the right step when workflows contain many similarly named nodes.

Improvements

  • The AI configuration area has been renamed from “AI Settings” to “AI Agent” throughout the interface for clearer and more consistent labeling.

  • The AI models available on Microsoft Azure have been updated to GPT-5.4 and GPT-5.4-mini, replacing the previous versions.

  • Images generated by AutoMate are now displayed properly as rendered images in the chat, rather than as raw inline references.

  • Text formatting in AutoMate responses now uses consistent, correctly sized fonts for headings, paragraphs, and lists.

Bug Fixes

  • Fixed a security issue where logging out did not fully delete the session. Logout now properly ends the session, and a fresh session is created on next login.

  • Fixed an issue where text field nodes placed after a Send & Result node were not correctly displaying the data retrieved from API calls — the fields now update as expected.

  • Fixed an issue where the chat window inside bot nodes could grow indefinitely. The window now has a fixed size and is scrollable.

  • Fixed an issue where selecting the “dashboard” display option in a bot card could not be saved. This option is now fully supported and persists correctly.

  • Fixed a false error in the AI Agent debugger log that incorrectly flagged successful tool executions (such as sending emails) as failed. The log now correctly reflects the actual outcome.

  • Fixed a critical issue where copying workflow nodes caused the copied nodes to share internal reference IDs with the originals. This was leading to data mixups at runtime where copied steps were reading output from the original step instead of their own. Duplicated nodes now always get fresh, unique references.

  • Fixed two AutoMate issues: prompts containing quotation marks no longer cause a failure, and edited plans are now correctly used when generating the workflow instead of falling back to the original version. Note: document support in AutoMate currently works reliably with PDF files.

  • Fixed an issue where tables rendered by AutoMate would overflow outside the chat window with no way to scroll. Tables are now correctly contained and scrollable.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • Pro Agent Tools: AI Agents can now call external APIs as tools during a workflow step. You define the API connection and describe the tool in natural language in the dashboard. The agent then decides when to use it based on the workflow context. Tools are scoped per agent and per workflow step. This allows agents to write data into external systems, trigger actions, or retrieve information without manual intervention between steps.

  • New frontend designs: 6 new layout designs are available for the consumer facing bot frontend. You can preview and switch between them in the bot settings. The selected design applies immediately to your live bot.

  • You can now click on AI generated images in the chat to open them in a full screen view. From there you can download the image directly, making it much easier to save and reuse generated visuals.

Improvements

  • Images generated in AutoMate chat now display as proper standalone visuals instead of being rendered as inline markdown. This makes image responses cleaner and easier to view.

  • Text sizes in chat responses are now consistent across paragraphs, lists, and headings. Previously, some elements appeared larger or smaller than intended, which could make AI responses harder to read.

Bug Fixes

  • Fixed an issue where special characters in file names (such as parentheses) could cause bot runs to fail when using DOCX or PDF nodes. File names with characters like “Test (Draft)” are now handled correctly.

These updates have completed testing and will be deployed to production in the next release.

New Features

  • You can now download PDF and SVG documents directly from the Transparenzregister integration, making it easier to save and share registry records.

  • The Transparenzregister integration now connects to the official production environment, replacing the previous test endpoint.

Bug Fixes

  • Fixed an issue where unpublishing a clause would fail with a validation error, even when the clause was not used anywhere.

  • Subscript and superscript formatting now renders correctly in generated Word documents and PDFs. Previously, these were stripped or displayed as normal text in exported files.

These updates have completed testing and will be deployed to production in the next release tonight.

New Features

  • The Transparenzregister integration is now fully operational. You can authenticate and submit requests to the Transparenzregister directly from the application, with automatic token management running in the background.

  • When you use AutoMate to add or edit nodes in your workflow, the canvas now automatically scrolls to the first node that was changed or added, so you always land in the right place after an AI edit.

  • AutoMate now automatically saves your bot whenever it creates or edits nodes. You no longer need to manually save after making AI-assisted changes to your workflow.

Improvements

  • The action menus on workflow nodes are now easier to read. The background behind those controls was too transparent and could make the icons hard to distinguish — this has been corrected with improved opacity.

  • Passwords must now be at least 10 characters long when signing up or changing your password, in line with updated security policy. If you try to set a shorter password you will see a clear validation message. Existing passwords do not need to be changed.

Bug Fixes

  • Fixed a reliability issue with AutoMate’s node editing where nodes were sometimes incorrectly deleted, replaced instead of added, or duplicated due to ID conflicts. AutoMate should now apply changes accurately and predictably.

  • Fixed a bug where asking AutoMate to delete a logic condition left the Bot in an invalid state. Only the child step was being removed, leaving the parent disconnected from the rest of the flow.

  • We updated the underlying text editor to the latest version, which may resolve an issue where applying formatting to a large block of content could cause an error. If you have been experiencing this, please let us know whether it still occurs.

  • Fixed two issues with annotation widgets: they now render correctly when previewing an annotation node, and the variable picker no longer opens behind the annotation editor when you try to reference another node.

  • Fixed an issue where the PDF viewer inside the source node modal was not rendering the document. The modal was showing only raw extracted text chunks instead of the actual PDF.

  • Fixed an issue where the open nodes counter in the floating toolbar did not update in real time after deleting an open node from the canvas. The count now reflects the correct number immediately.