10.1 Unlimited changelog
This document details the technical changes and enhancements introduced in Creatio 10.1 Unlimited. It is intended for developers, system administrators, and DevOps engineers responsible for maintaining and extending Creatio customizations.
For a comprehensive overview of the new features, refer to the 10.1 Unlimited release notes.
The update guide for the on-site applications is available in a separate article.
Creatio products and apps
Creatio AI app development toolkit
Category | Feature | Description |
|---|---|---|
Creatio.ai | AI Skills | Added the "classic-to-freedom-migration" skill to the Creatio AI app development toolkit. The skill rebuilds a Classic UI section as a parallel Freedom UI counterpart that includes the list page, form page, expanded lists, and mini pages. Previously, these pages had to be rebuilt in Freedom UI manually. The skill requires a coding agent that has the Creatio AI app development toolkit and Clio MCP connected, and access to the Creatio environment that contains the Classic UI section. This change enables app creators to move Classic UI sections to Freedom UI from a reviewable plan and confirm the result against a verification table. It reduces manual rebuilding effort and the risk of missing section elements during the transition. |
Creatio.ai | AI Skills | Added dashboard generation to the "creatio-app-orchestrator" skill used by the Creatio AI app development toolkit. Previously, the skill generated the data model, sections, pages, and business logic of a new app but produced no analytics, and users added dashboards manually after the app was created. This change makes the skill always suggest analytics during app creation, treating a plan with no analytics as incomplete. The skill generates section dashboards for the roles that work with a specific section, and app-level dashboards placed on the workplace home page of the app. If the app has none, the skill reuses the existing workplace or creates a new workplace. Widgets are built from the data model of the app, can reference base Creatio objects, and support metrics, charts, and list widgets. Out of the box, only users that have the "All employees" organizational role can access generated dashboards. The access rights are delivered with the app package to preserve them while transferring between environments. This enables developers and no-code creators to obtain apps with meaningful analytics immediately after generation, without manual dashboard setup and repeated access right configuration. |
Creatio.ai | Widgets | Added the ability to add charts, list widgets, comparison metrics, and calculated metrics to a Freedom UI page and configure them from a natural-language request using the Creatio AI app development toolkit. Previously, only a limited set of widgets was available for agent-based generation, and the rest had to be configured in the Freedom UI Designer or Dashboard Designer. This change enables app creators to generate complete analytics pages without manual widget setup and provides consistent widget configuration across generated apps. This capability is standalone and can be used independently of app generation — on any existing Freedom UI page, whether generating a new app or editing an existing app. |
Creatio.ai | Widgets | Added the agent-facing contract and authoring guide for generating and configuring pivot tables on Freedom UI pages using the Creatio AI app development toolkit. Previously, the widget registry exposed no descriptions for the bindable properties of a pivot table and the |
Creatio.ai | Dashboards | Added the ability to create a dashboard using the Creatio AI app development toolkit and define which user roles or dedicated users can see it. Previously, creating dashboards and configuring their visibility had to be done manually. This change enables app creators to deliver dashboards together with the correct access setup in a single request, reducing the risk of exposing a dashboard to unintended users. This works both when generating a new app and when editing an existing app. |
Creatio.ai | Business rules | Added the ability to manage page-level and object-level business rules using the Creatio AI app development toolkit. Coding agents let you create, read, edit, and delete business rules, including rules with conditions based on a system setting value or a data source. Previously, agents could not modify or remove existing rules, and these condition types were not covered. This change enables app creators to maintain page logic across iterations of a generated app instead of reworking rules manually in the Business Rule Designer. |
Creatio.ai | Business rules | Fixed a runtime issue where business rules that set field values did not run after a record was copied. Previously, the page model of a copied record stayed in the copy state after the copy operation was completed, so changing a field that triggers a business rule did not recalculate the dependent field values. The same rule worked as expected on a newly created record, which forced no-code creators to instruct users to save the copy and reopen it before the calculated values appeared. Creatio now processes a change of a triggering field on a copied record as an edit and runs the rule. A record that is only opened without changes does not trigger the rule. This change enables no-code creators to rely on identical business rule behavior for copied and newly created records, and they no longer need to document a save-and-reopen workaround for end users. |
Creatio.ai | Workplaces | Added the ability to manage workplaces in the Creatio AI app development toolkit. Coding agents can create, update, or delete a workplace, and add or remove sections within a workplace or move a section between workplaces. Agents can also grant, change, or remove permissions to work with the workplace for specified user roles. Agents also create and update data bindings so workplace configuration data is transferred with the package. Previously, workplace setup and its data bindings had to be configured manually on the administrator level and in the package. This change enables app creators to prepare a complete workplace structure, its access, and its package bindings from a natural-language request. It reduces the risk of a workplace configuration reaching a target environment without the required data bindings. |
Creatio.ai | Pages | Added the ability to create Freedom UI desktop and home pages in the Creatio AI app development toolkit. Previously, coding agents could not generate these page types, so they had to be created manually in the Freedom UI Designer. This change enables app creators to deliver the entry points of an app together with the rest of the generated content. |
Common features
Category | Feature | Description |
|---|---|---|
WhatsApp Chat Channel | Customer communication hub section | Added the ability to connect a WhatsApp (Meta Cloud API) chat channel using the Add channel button list in the Manage channels toggle panel of the Customer communication hub section. The WhatsApp chat channel connects a WhatsApp Business account to Creatio through the Meta Cloud API. An administrator confirms the connection in the Meta sign-up flow. It is delivered as part of the WhatsApp Chat Channel app available in Creatio Sales, Creatio Service, Bank.AI and deprecated Bank Customer Journey and compatible with Creatio 10.1 and later. On a product that does not include the app, for example, Creatio Business Studio, installing it also installs the Contact Center app automatically. Previously, WhatsApp communication was available only through the Twilio integration, which remains supported and is displayed as "WhatsApp (Twilio)" in the Add channel button list. This change makes the WhatsApp chat channel available to administrators out of the box and enables companies to process WhatsApp conversations in Creatio without a third-party messaging provider. |
WhatsApp Chat Channel | Customer communication hub section | Added the ability to refresh the connection of a WhatsApp (Meta Cloud API) chat channel on the settings page in the Customer communication hub section. Access tokens issued by Meta expire, and an expired token stops message delivery. The administrator reconnects the channel using the Reconnect button, and the channel starts receiving messages again. Channel settings remain unchanged. This change enables administrators to restore a channel that stopped receiving messages without deleting and connecting it again. |
WhatsApp Chat Channel | Customer communication hub section | Added the ability to activate and deactivate a WhatsApp (Meta Cloud API) chat channel on the settings page in the Customer communication hub section. An administrator deactivates the channel to stop receiving messages sent to the connected number, and activates it again to resume, without deleting the channel or its settings. This change enables administrators to pause a WhatsApp channel temporarily whenever needed, for example during maintenance or a planned pause in customer communication. |
WhatsApp Chat Channel | Customer communication hub section | Added the ability to delete a WhatsApp (Meta Cloud API) chat channel. The Delete row action is available in the Messaging channels block on the Manage channels toggle panel of the Customer communication hub section. Deleting the channel also removes the message subscription of the connected phone number, so Creatio no longer receives messages sent to that number, and the same number can be connected again as a new channel. This change enables administrators to disconnect and reconnect a WhatsApp number on their own. |
Contact Center, | Agent Inbox panel | Added the ability for human agents to receive incoming messages in the WhatsApp (Meta Cloud API) chat channel in the Agent Inbox panel. A message from a customer creates a chat that is routed to the queue of the channel, or is added to the open chat of the same customer. This way, one conversation always produces one chat. The contact is matched by phone number or created automatically, including contacts that were created earlier through the WhatsApp (Twilio) channel. Human agents accept the chat and can view all previous conversations with the contact. This change enables human agents to handle WhatsApp messages together with the messages of the other chat channels, with the full communication history of the customer available. |
Contact Center, | Agent Inbox panel | Added the ability for human agents to receive incoming files and media in WhatsApp (Meta Cloud API) chat channels in the Agent Inbox panel. Images, documents, audio, video, and stickers are supported and validated against the system settings and WhatsApp limits for each media type. Each file arrives as a separate message in the conversation. This change enables agents to receive the full context of a customer request, including screenshots and documents, without switching to another tool. |
Contact Center, | Agent Inbox panel | Added delivery statuses of outgoing messages in WhatsApp (Meta Cloud API) chat channels to the Agent Inbox panel. An outgoing message is displayed with the "Sending," "Sent," "Delivered," and "Read" statuses as the delivery progresses, or with the "Failed" status when WhatsApp rejects it. The failure reason returned by WhatsApp is stored and displayed to the agent. This change gives agents visibility of message delivery and enables them to react to a failed message immediately instead of waiting for the customer to report a missing reply. |
Contact Center, | Agent Inbox panel | Added the ability for human agents to send files and media in the WhatsApp (Meta Cloud API) chat channel in the Agent Inbox panel. Images and files are supported and validated against the system settings and WhatsApp limits as incoming files. When a file cannot be sent, the agent receives a notification that names the reason. This change enables agents to share images and files with customers directly in the conversation. File type restrictions are managed by the "File extensions deny list" ( |
Contact Center | Agent Inbox panel | Added the ability for human agents to reply to customers in the WhatsApp (Meta Cloud API) chat channel in the Agent Inbox panel. Replies are sent as free-form messages, which WhatsApp permits within the messaging window — the 24 hours that follow the last message from the customer. This change enables human agents to handle WhatsApp conversations in the same UI as other chat channels. |
Contact Center | Agent Inbox panel | Added support for file drafts in the Agent Inbox panel. Previously, attached files were kept in the page memory only and were lost as soon as the human agent opened another chat. Creatio now uploads every file attached to a chat in the background immediately after it is attached, and keeps it as a draft of that chat on the server. This change enables agents to attach a file, switch to another conversation, or reload the page without losing the attachment. Agents can now also work on multiple conversations in parallel without re-attaching files, and send messages with attachments without waiting for the upload to complete. To stop using this functionality, disable the Draft files are cleared when the message is sent, when the chat is completed or transferred to another agent, when the agent logs out of the last session, or when the retention period expires. The retention period is managed by the |
Contact Center | Agent Inbox panel | Added the ability to manually translate outgoing chat messages using the |
Contact Center | Agent Inbox panel | Added the Show original button to outgoing translated messages in the Agent Inbox panel. Previously, after an outgoing message was translated automatically, agents could no longer see the wording they had entered. The translated version that the customer received is displayed by default. Clicking the button switches the display to the text entered by the agent, and clicking the |
Contact Center | Agent Inbox panel | Fixed a runtime issue where a conversation started by the human agent did not appear in the Agent Inbox panel until the page was reloaded. Previously, when the human agent started an outbound conversation from the message composer, the chat was created and assigned to that agent. The panel displayed the chat only after the page was reloaded, the panel was reopened, or the agent status was changed. This change makes the conversation appear in the In progress panel list immediately after the message is sent. Human agents can continue an outbound conversation right away, without extra actions to refresh the panel. |
Contact Center | Agent Inbox panel | Fixed a runtime issue where the text of an incoming message was not displayed in the Agent Inbox panel when the customer sent text and an image in a single message. Previously, only the image was displayed and the text was not shown, although it was delivered together with the message. Messages that contained text and a file attachment were not affected. This change displays the text and the image in the conversation as separate messages. Human agents now see the full content of a customer message and no longer miss details sent along with an image. |
Contact Center | Agent Inbox panel | Fixed a runtime issue where an image or file that the customer sent more than once in a Telegram chat was not delivered to the Agent Inbox panel. Previously, Creatio identified duplicate incoming Telegram messages by the content of the attached file. Telegram returns the same file identifier for identical content. When a customer sent the same image again, the message was treated as a repeated delivery of an earlier message and was discarded silently, without an error, and the human agent never received it. This change identifies incoming Telegram messages by the chat and message identifiers instead. Every new message is now delivered even when it includes a file that has already been sent, while a message that Telegram genuinely redelivers is still filtered out. |
Contact Center | Agent Inbox panel | Fixed a runtime issue in the Agent Inbox panel where completing a chat that contained no messages exchanged between the human agent and the customer did not work correctly. Previously, the request to complete such a chat failed, the loading mask never cleared, and the chat tile kept reappearing in the panel, although the chat had already been marked as completed in the database. For example, this could happen when a conversation was handed over to a human agent by an AI agent and the human agent completed it without replying to the customer. This change makes Creatio complete such chats correctly and return control of the conversation to the AI agent that handled it before the handover. Human agents can now close chats in which they did not participate, and completed chats no longer remain visible in the panel. |
Contact Center | Agent Inbox panel | Fixed a runtime issue where the "Queued tasks" filter of the Agent Inbox panel showed queue items assigned to other human agents. Previously, the filter built by the |
Contact Center | Agent Inbox panel | Fixed a runtime issue where the "Queued tasks" filter in the Agent Inbox panel loaded the first 15 queue items without access filters when all queues available to the human agent were blind or the agent was not a member of any queue. Previously, the filters were not applied to the queue item request in these cases, so agents saw items that were not theirs. This change applies the same access rules as the Agent desktop Classic UI section and shows only the items assigned to the agent, keeping agents focused on their own work items. |
Contact Center | Agent Inbox panel | Fixed a runtime issue where a false "Leave page" browser dialog was shown when a user downloaded a file from a chat while the "Queued tasks" filter was applied in the Agent Inbox panel. Previously, applying the filter wrote the |
Contact Center, | Agent Inbox panel, | Fixed a runtime issue where call pages stayed in the Agent Inbox panel and in the "Calls" sidebar in the communication panel after a call had ended while the Creatio browser tab was in the background. Previously, browsers throttle timers in background tabs, so the keep-alive of the messaging service connection was delayed. The connection was dropped and re-established about every two minutes, and a call teardown event delivered during the gap was lost. This change makes the connection to the .NET Core messaging service (Asterisk V2 connector) survive the throttled keep-alive of a background tab. Call state events are no longer lost, and agents can switch to other applications during a call without stale call pages. |
Web Chat | Web chat channel settings page | Changed the implementation of the web chat channel settings page: the handler logic was moved out of the page schemas into a separate remote module. Previously, the logic of the "Web chat channel adding page" ( |
Web Chat | AI and automation | Fixed a runtime issue where the system message about chat completion was displayed in the live preview on the web chat channel settings page with unresolved macros. Previously, users configuring the channel saw the raw macro text in the preview instead of the actual values. This change shows the preview with resolved values, so users can verify how the notification looks to customers before it goes live. |
Web Chat | AI and automation | Fixed a runtime issue where AI did not process Web chat conversations because the access permissions required by the "Creatio WebChat Inbound Service" technical user were not applied. Previously, the membership of this technical user in the "Communication Channel Service" functional role was saved, but the corresponding role hierarchy record was created only by an asynchronous recalculation of the organizational structure. Until the recalculation completed, record permissions to conversations authored by this technical user were not granted to the "AI Communication Service" functional role, so AI could neither read nor update Web chat conversations. On affected environments, the recalculation did not run for weeks. Creatio now creates the role membership and the corresponding role hierarchy record within the same provisioning pass that creates the technical user. It also grants read and edit record permissions on the "Chat" ( |
Customer communication hub, | Customer communication hub section | Fixed a runtime issue where the Total chats metric on the chat channel settings page in the Customer communication hub section displayed only the chats created on the current day instead of all chats of the channel. The change applies to the base chat channel settings page, so it affects all chat channels. This change gives administrators an accurate view of the load of each channel. |
Customer communication hub | AI and automation | Changed the calculation of the "AI effectiveness" column value for email chat channels in the Channel performance block on the Overview tab of the Customer communication hub section. Previously, Creatio divided the number of closed cases with an AI-autosent reply by the total number of email cases registered within the last 7 days. Mailboxes that handled a large share of cases without AI involvement showed a low value, and the column could not be compared to the same column for other chat channels. This change divides the number of closed cases with an AI-autosent reply by the number of AI-assisted cases instead, which are cases where AI generated at least one reply draft or sent a reply automatically. |
Integrations and APIs | Chats | Added support for automatic handoff of AI-processed chats to the chat queue when the Use AI in the channel checkbox on the AI automation tab of the chat channel settings page is cleared. Previously, clearing the Use AI in the channel checkbox in the channel settings mini page in the Chat settings page left the chats that were already being processed by AI without an assigned agent. Incoming messages in those chats did not route them to agents either. This change transfers every chat that is being processed by AI in the channel to the chat queue specified in the channel settings, making the chat available to agents in the Agent Inbox panel. |
Integrations and APIs | Chats | Changed the storage mechanism for chat message translations so that they are retained permanently and remain available on the chat page in the Chats section. Previously, translations of incoming messages were held in temporary storage and were available only while the agent handled the chat, and only the original text was saved to the database. A completed conversation could no longer be reviewed in the translation language. This change stores translations together with the original text, with both versions available through the |
Integrations and APIs | Chats | Fixed a runtime issue where message text in a completed chat could be displayed without the anonymization that had been applied to it. Previously, cached message translations were not cleared when a chat was completed and were not covered by anonymization. This change clears cached translations for a chat and all related chats when the chat is completed, so anonymized data stays anonymized throughout the conversation. |
Integrations and APIs | Chats | Fixed a runtime issue where the first response time of a chat could be set by an automatic outgoing message instead of the reply of the human agent. Out of the box, this had no effect, because an AI agent handles the conversation in a separate chat. However, in environments where automatic replies are sent by a custom solution into a chat that is already handled by a human agent, such a message was counted as the first response, and the first response SLA was measured against it rather than against the actual reply. This change makes an automatic message no longer set the first response time in a chat handled by a human agent. In a chat handled by an AI agent, it continues to count as the first response. |
Integrations and APIs | Chats | Fixed a runtime issue where the |
Integrations and APIs | Chats | Fixed a runtime issue where conversations handled by an external chatbot were transferred to the agent queue before the chatbot requested a handoff. Previously, when an incoming message arrived in a conversation that had the "Bot processing" status on a channel whose Use AI in the channel checkbox on the AI automation tab of the chat channel settings page was cleared, Creatio handed the conversation over to an agent regardless of which bot was processing it. Conversations driven by the Ada AI Chatbot connector appeared in the agent queue even though no handoff request was received from Ada. Creatio now verifies that the conversation is owned by Creatio.ai before performing the recovery handoff. This change enables external chatbot integrations to retain full control over the moment a conversation is passed to an agent, and agents no longer receive conversations that an external chatbot is still handling. |
Integrations and APIs | Chats | Fixed a runtime issue where Telegram chat channels reported a false duplicate bot error after every Creatio restart. Previously, a starting Creatio process began polling a bot token that a still-running process was already polling. Telegram returned a polling conflict, and Creatio set the "The "{channel name}" chat channel is not receiving messages because another Telegram bot instance is configured" channel error and notified administrators. No external consumer of the token existed, however. The error did not clear by itself and reappeared after each restart, and while two readers were active, incoming messages could be duplicated or lost. This change stops Telegram readers when Creatio shuts down and treats a polling conflict that occurs immediately after its own reader starts as part of the reader handover. No error or notification is raised in that case. A conflict caused by a genuine external consumer of the bot token is still reported, and incoming Telegram messages are no longer duplicated or lost while processes overlap. |
button in the message editor of the Agent Inbox panel. Previously, outgoing messages were translated automatically upon sending, and agents had no way to translate a message manually or review the translation before it reached the customer. The functionality is managed by the "Automatically translate outgoing messages" (Creatio Marketing
Category | Feature | Description |
|---|---|---|
Marketing campaigns | Campaign Designer | Added the Audience transfer pace setting block to the setup area of the Timer campaign element in Campaign Designer. The block enables marketers to set granular control over audience delivery pace. This change enables marketers to prevent processing spikes and manage Creatio load in time-sensitive campaign scenarios. The Audience transfer pace setting block is available for the Timer element whose Frequency of timer start setting is populated. The Audience transfer pace setting block includes the following options: |
Marketing campaigns | Campaign Designer | Fixed incorrect record targeting in transition by filter conditions that follow the Add data and Modify data campaign elements. Previously, when a filter condition was applied on the element transition after one of these elements, Creatio evaluated all records of the target object associated with the campaign participant's contact. This happened instead of evaluating only the specific record the element had just created or modified. In scenarios where a contact had multiple associated records of the same type, for example, multiple leads, the campaign triggered on unintended records. This change restricts evaluation to the specific record created or modified during the current element execution, referencing it through the "CampaignParticipantInfo" ( |
Email Marketing | Bulk emails section | Fixed a runtime issue with bulk emails that use advanced macros. Previously, these emails remained in the "Queued" status in the Bulk emails section after Creatio finished sending them. This change updates the status to "Completed" once sending is finished, giving marketers an accurate view of delivery progress. |
Segmentation | Segment page | Added support for scheduled population of a segment based on the "Scheduled" value of the Population mode field on the segment page. Previously, segment membership could be refreshed on demand only, and activating a scheduled segment always enqueued an immediate population. This change enables users to keep segment membership up-to-date without manual intervention and gives them predictable population timing that matches the configured schedule. |
Segmentation | Segment page | Added the ability to schedule automatic population of a segment in the lifecycle area of the segment page. Previously, segment population could be started only manually, and a population schedule could not be configured in the UI. This change enables users to schedule automatic segment population without leaving the segment page and shows them exactly when the next population runs. |
Segmentation | Segment page | Fixed a regression on the segment page where the Matching contacts metric always showed the total number of contacts and did not react to changes in the segment entry filter. Previously, the metric's binding to the entry filter had been lost in the page schema during an unrelated change to the segment form. This change restores the binding, so the metric counts only the contacts that match the current entry filter and shows "0" when the filter is empty. The metric also updates on every filter change without saving or reloading the segment. |
Creatio Sales
Category | Feature | Description |
|---|---|---|
Sales Forecasts | Sales forecasts section | Added the |
Sales Forecasts | Sales forecasts section | Added the opportunity toggle panel to the Sales forecasts section. Clicking an opportunity name in the forecast drill-down list opens the panel with a compact record summary. The panel refreshes automatically when the list selection changes. The panel displays only data to which the user has access. This change gives sales managers and reps immediate access to an opportunity's details, activity, and history directly from the page. It also gives administrators a way to adjust the panel configuration. The opportunity toggle panel includes the following tabs: The opportunity toggle panel is horizontally resizable by dragging its left border from 424 px to a maximum of 50% of the Sales forecasts section. Out of the box, the opportunity toggle panel width is 480 px. The panel is hidden when the Sales forecasts section content takes 848 px or narrower. Width is saved per user. |
Sales Forecasts | Forecast hierarchies section | Added a new Forecast hierarchies section to view, search, and maintain forecast hierarchies independently of a specific forecast, supporting base sorting, filtering, and search by name. It is delivered as part of the Sales Forecasts app and is displayed in the "Sales forecast" workplace. The section is available to administrators only. Previously, forecast hierarchies could only be created and edited from within the forecast configuration flow. Forecast hierarchies and Sales forecasts configuration sections use the same hierarchies. Editing a hierarchy already bound to a forecast with existing submissions displays a warning listing the affected forecasts and requires user confirmation before applying the change. |
Sales Forecasts | Hierarchy builder | Added the ability to apply filters to a hierarchy on the Hierarchy builder page in the Forecast hierarchies section. Previously, a hierarchy always included every record from its source object, with no way to narrow the structure to only the relevant objects. Filters can be applied regardless of how the hierarchy was built: manually from scratch or automatically by a parent column. Filters are defined using the base filtering mechanism over the source object columns. Adding filters rebuilds the hierarchy so that only matching records are included, while preserving the parent-child relationships between the remaining records. The filter is a hierarchy-level structure parameter, so it applies to every forecast that uses the hierarchy. Defined filters are persisted with the hierarchy and reapplied automatically when it is reopened or recalculated. This change enables users to exclude records from forecasting, without maintaining a separate, manually created structure. |
icon to each opportunity row of the forecast drill-down list in the Sales forecasts section. The icon is displayed to the left of the opportunity name, shows a tooltip when the user points to it, and follows the same visual and pointing treatment as other page icons. Clicking the icon triggers the existing "Summarize opportunity" sub-agent and passes the opportunity ID as context. Creatio.ai chat panel opens or switches to the current task and returns the summary for that exact opportunity, without prompting the user to select an opportunity. List selection, submission state, or any opportunity or forecast data remain unchanged. This change enables sales managers and account executives to get AI-assisted opportunity context directly from the drill-down list, reducing the steps needed to review a specific deal.Industry cases
Category | Feature | Description |
|---|---|---|
Field sales | System settings and tools | Changed the "Color" column in the Account types lookup of the Field Sales app to add color coding for "Retail chain," "Sales outlet," and "Distributor" values. Previously, these account type values displayed without color, like all other account types. This change enables users to distinguish these account types quickly across Accounts section and account pages. Added: Other account types remain unchanged. |
Field sales | Account page | Added the Product tab to the account page. The tab is shown when the Field Sales app is installed. Previously, an account's related products could not be viewed from the account page. The tab shows an empty state when the account has no related products. This change enables users to review an account's full product footprint and visit recency in one place directly from the account page. |
Creatio Business Studio
No-code customization
Category | Feature | Description |
|---|---|---|
No-code tools | Freedom UI Designer | Changed the way container properties are saved to the Freedom UI page schema in the Freedom UI Designer. Previously, saving a page wrote the full set of container property values to the |
No-code tools | Freedom UI Designer | Changed the out-of-the-box status of the |
No-code tools | Freedom UI Designer | Changed the out-of-the-box status of the |
No-code tools | Dashboard Designer | Added the ability to open the source code of the dashboard page using the Source code item in the |
Localization | Translations | Added clean-up of obsolete localizable values when a configuration schema is saved. Creatio now compares the localizable keys stored for the schema with the keys the schema declares, and deletes the stored values that are no longer declared. Previously, the title and the description of a schema item that was removed or renamed remained in the |
Apps and packages | App management | Changed the installation logic for apps that use the technical "0.0.0" version. Previously, if an environment already had a higher version of the target app installed, attempting to install a package with version "0.0.0" caused that app to be skipped from the installation bundle. An app with version "0.0.0" is now always included in the final installation bundle and reinstalled, regardless of the version currently installed on the environment. Version values "0," "0.0," and "0.0.0" are treated as the same technical version for this purpose. This applies only to the target app's own version, for both single and group installations, across Application Hub, WorkspaceConsole, and Clio utilities. Creatio Business Studio version comparison and other dependency resolution logic, including finding the best suitable version, downgrade handling, and conflict detection, remain unchanged and continue to ignore the "0.0.0" technical version. This change enables users to reliably deliver updates packaged under the trunk "0.0.0" version, ensuring their changes are always applied instead of being silently skipped. |
Apps and packages | App management | Changed the installation workflow to automatically run the backend cache-clearing logic used by the Run app button in the Application Designer. This now runs for all installed apps immediately after a successful installation, without navigating the user into any app or changing their current screen. Previously, a newly installed or updated app could require a manual cache reset before it became fully functional, since some of the caches needed for correct operation were not refreshed automatically during installation. This change enables users to install or update apps without needing to manually reset caches afterward, since installed apps are immediately ready to use. The user is not redirected or navigated into any app, unlike manually clicking the Run app button. |
Apps and packages | App management | Fixed a runtime issue where installing an app from the Application Hub could fail with the "The process cannot access the file" error. This happened when a leftover package archive in the shared installation working directory was locked by another process, for example, an antivirus scanner or backup agent. Previously, every package operation (validation, backup creation, and installation) cleared this shared working directory at the start. The operation failed immediately if even one file inside it, including files left over from a previous installation, could not be deleted. Package operations no longer fail outright when a locked file is found in the working directory during cleanup. Files that do not belong to the archive being installed are skipped with a named warning instead of aborting the operation. Package archives are now deleted right after they are unpacked, so leftovers no longer accumulate between operations. This change enables users to install or update apps reliably even when antivirus software, indexers, or other processes briefly lock files in the installation working directory, reducing installation failures caused by transient file locks. To stop using this functionality, disable the |
Apps and packages | App management | Fixed a runtime issue where installing or updating an app that delivers additional feature bindings did not invalidate the client feature cache. Previously, the additional feature was created and enabled on the server, but client sessions that were already open kept using a stale cached feature list. The feature stayed unavailable to client code and dependent UI even after a page reload or a full logout and login. Only a manual cache reset or enabling the feature in the Feature toggling section made it available, whether the feature was newly added or had changed status. Creatio now invalidates the client feature cache in this scenario, so delivered features become available to client code and the UI after a plain page reload, without any manual step. This change enables users to install or update composable apps that deliver additional features without extra manual steps, and prevents existing users from silently missing functionality delivered by an app update. |
UI Design | Freedom UI components | Added the Which folder the filter can be saved to? parameter to the setup area of the Filters component in the Freedom UI Designer. This parameter enables no-code creators to connect the Filters component to folders that use the same Object type schema, so end users can save filters to those folders using the |
UI Design | Freedom UI components | Added the Recipients pre-fill parameter to the setup area of the "Email" channel in the Message composer component in the Freedom UI Designer. Previously, this functionality was available in Classic UI only. This change enables no-code creators to set recipient rules for the composer in the designer and enables users to send emails from record pages without entering recipients manually. |
UI Design | Freedom UI components | Added the Allow disabling conditions checkbox to the setup area of the Filters component in the Freedom UI Designer. The checkbox enables no-code creators to control whether end users can disable and enable individual conditions, groups, and predefined filter presets. Out of the box, the checkbox is selected. |
UI Design | Widgets | Added the Apply filter by page data parameter, Add calculated field button, support for related object columns in the Rows, Columns, and Values parameters to the setup area of the pivot table in the Freedom UI Designer and Dashboard Designer. Additionally, added grouping of "Date/time" type columns and a design-time structure preview for the pivot table. Sorting of rows and columns and row totals are not supported. This change enables no-code creators to deliver cross-tab analytics that previously required Classic UI dashboards or custom development. It also enables them to validate the widget structure before saving instead of publishing a page to check the result. |
UI Design | Widgets | Changed the out-of-the-box status of the |
Business processes | Elements | Fixed a runtime issue where the Send chat message process element could not send the first message to a contact in an SMS channel. Previously, before sending a message, Creatio required an existing conversation with an inbound message from the contact, regardless of the channel. The process element failed with the "Unable to find the sender's contact data for this channel" error, and an SMS could be sent only after the contact had written to the channel first. This change sends SMS messages to the primary mobile phone number of the contact even if the contact has never written to the channel, letting administrators use business processes for proactive SMS notifications. The behavior of the other channels remains unchanged. |
Business processes | Elements | Fixed a runtime issue where column titles were not displayed in the Formula window when value mapping was configured in Process Designer. Previously, column titles were not displayed when the |
Business processes | Elements | Fixed a runtime issue where the Call web service business process element omitted nested collections from the request body. Previously, if a request parameter was a collection whose items contained another collection, the element sent the outer collection and its scalar values but dropped the inner collection, so the external service received an incomplete payload. Creatio now resolves nested collection parameters through the parameter value provider and includes them in the request. This change enables developers and no-code creators to integrate Creatio with services that expect nested collection structures, for example, e-signature providers, directly from a business process, and removes the need to build a workaround to assemble the request body. To stop using this functionality, register and enable the |
Business processes | Process execution | Fixed a runtime issue where the warning notification did not appear when the number of records selected to run a business process in a section exceeded the processing limit. Previously, the notification was not displayed and the loading mask remained on the page, so the run appeared to hang. This change shows the notification immediately, enabling users to see why the process did not start and adjust their selection without reloading the page. |
Integrations and APIs | OAuth authorization | Changed the way the email address is resolved during JWT Assertion token generation. Previously, the token included an email address only when the "Email" ( |
Integrations and APIs | OAuth authorization | Fixed a runtime issue where provider-specific query parameters configured in the Application URL field in the Application information expansion panel on the Settings tab of the OAuth application page were dropped from the generated authorization request. Previously, Creatio rebuilt the authorization request query string from a fixed set of generated OAuth parameters and overwrote the query of the configured URL, which discarded provider extras, for example, audience. The identity provider then issued an identity-only token that had no API audience, and subsequent API calls returned the 401 Unauthorized status code. Creatio now preserves provider-specific query parameters from the configured URL and forwards them into the generated authorization request. This change enables administrators to integrate Creatio with identity providers that require provider-specific authorization parameters without custom development, and removes a source of authorization failures that were difficult to diagnose from the client side. To stop using this functionality, register and enable the |
Integrations and APIs | OAuth authorization | Fixed a design-time issue where the Creatio update failed when the OAuth grant type lookup did not include the "Server-to-server (client credentials)" value. Previously, the install script that assigns the default grant type to OAuth 2.0 integrated applications wrote the identifier of that lookup value without verifying that the value existed. This caused a foreign key violation and aborted the update at the configuration update step. Creatio now verifies that the lookup value exists before it updates integrated applications, and skips the assignment when the value is missing. This change enables administrators to complete the Creatio update on databases where the lookup is incomplete, instead of ending with a failed update that blocks any further version update. |
Integrations and APIs | DataService | Fixed a regression where custom HTTP response headers, including Lone Unicode surrogates still serialize to |
Integrations and APIs | Calendars | Added synchronization of Microsoft Teams meeting attendance to the Creatio event audience. Previously, after a webinar delivered as a Teams meeting, nobody recorded who attended, so the event audience could not be reported as participated or did not participate. To start using this functionality, register and enable the |
Integrations and APIs | Calendars | Fixed a runtime issue where a |
Integrations and APIs | Calendars | Fixed a runtime issue where the legacy Google calendar synchronization failed for users whose date and time format uses a period as the time separator, for example, Finnish. Previously, the |
Integrations and APIs | Calendars | Fixed a runtime issue where the participant status in synchronized meetings did not update when a participant deleted the meeting in Microsoft Outlook without sending a response to the organizer. Previously, the status in Creatio stayed unchanged. This change updates the status to "Declined" after the next calendar synchronization of the organizer and the participant, giving organizers an accurate picture of who declined a meeting. |
Integrations and APIs | Telephony | Added the ability to manage agent status in the Asterisk V2 phone connector, based on the AMI When the Asterisk is the single source of truth: the connector reads the real state from the On call connect, the agent is paused automatically and unpaused when the call ends. A manual status change takes precedence over the automation, and the agent stays "NotReady" through wrap-up. Queue-delivered calls are shown in Creatio while ringing, and the queue number is added to the call's Available parameters in the The status codes must match the agent states configured in the User status reasons while messaging lookup. Direct-extension routing is not affected, and the V1 connector remains unchanged. |
Integrations and APIs | Telephony | Added the display of a clear message about a missing or expired phone connector license to all out-of-the-box phone connectors that work through Creatio Messaging Service. Previously, when the user had no license for the connector, the connector failed silently. The phone did not connect, nothing appeared in the "Calls" sidebar in the communication panel or the browser console, and the cause could be found only in the messaging service logs. This change enables administrators of on-site and cloud installations to see immediately that telephony does not work because of licensing, instead of investigating logs. |
Integrations and APIs | Telephony | Fixed a runtime issue where the Asterisk V2 phone connector closed the call page of the transfer target after an attended transfer. Previously, when Asterisk optimized the local channel after the transfer completed and hung up the orphaned local channel halves, the connector treated that hang-up as the end of the active call. It found the call by the |
Integrations and APIs | Telephony | Fixed a runtime issue where the |
Integrations and APIs | Emails | Added the ability to filter incoming emails by sent date during mailbox synchronization. Previously, the Exchange Listener selected mailbox items by their last modification date, so old emails re-entered the synchronization period whenever they were modified or moved on the mail server, and were created in Creatio as new activities. To use this functionality, register and enable the |
Integrations and APIs | Emails | Changed the error handling of Microsoft Graph mailboxes. An invalid access token now shows the "Connect mailbox again" link in the "Emails" sidebar of the communication panel. Previously, an error that matched no "Synchronization error handler" ( |
Integrations and APIs | Emails | Changed the handling of the |
Integrations and APIs | Emails | Fixed a runtime issue where the Exchange Listener re-fetched a Graph API message endlessly when Microsoft Graph returned a 404 Not Found status code for it. Previously, such a message was classified as poison, but on the real-time path nothing acted on the classification. The worker then requeued and reloaded the same message about eleven times per second, flooding the logs and consuming Graph API quota. This change applies a retry budget to the real-time path and drops the message after the limit, keeping the service and its logs clean when a message disappears from the mailbox before it is loaded. |
Integrations and APIs | Emails | Fixed a runtime issue with the recipient selection in the modal window opened from the To, CC, or BCC fields in the email mini page, accessed via the "Emails" sidebar of the communication panel. Previously, records that a user selected and then hid with a filter were not added to these fields when the user clicked Select. This change adds all selected records regardless of the current filter, letting users pick recipients across multiple filters in one go. |
Integrations and APIs | Emails | Fixed a runtime issue where an incoming email reply was linked to the wrong case when one conversation contained messages of multiple cases. Previously, when the |
Integrations and APIs | Emails | Fixed a runtime issue where duplicate activities were created for emails sent from Creatio when mailbox synchronization processed the sent message before sending had completed. Previously, a draft had no |
button menu in the action panel of the Dashboard Designer. Previously, the item was unavailable in the Dashboard Designer, unlike other designers, which forced developers to reach the source code of the dashboard schema using other tools. The item behaves identically to the equivalent item in other designers. The item is displayed to all users, while opening the source code remains available only to users who have permission to the "Can manage configuration elements" (
button at runtime.Advanced customization
Category | Feature | Description |
|---|---|---|
Framework updates | Angular version update | Changed the Angular framework version used by the Creatio platform to version 22. This change aligns the platform with Angular 22 standards and ensures continued compatibility with the latest framework capabilities. |
Schema design and management | Schema inheritance | Added the ability to install composable apps with same-named inherited indexes into any product bundle without configuration build failures. Previously, an inherited index re-added under a new internal ID but the same name survived the schema fold. Installing such an app into a bundle that already declared an index with that name then caused a configuration build failure. This change enables no-code creators and developers to deliver and install composable apps with same-named inherited indexes freely, and enables administrators to revert to the previous fold behavior per environment without a rebuild. To stop using this functionality, disable the |
Schema design and management | Schema inheritance | Fixed an issue where the title of a replacing "Object" type schema reverted to the original title after a package installation. Previously, when a schema title was renamed in an intermediate package, a dependent package that replaced the same schema without changing the title caused the installation to apply the title from the base package instead. This caused the rename to be lost. Creatio now resolves the title from the nearest ancestor package in the dependency hierarchy of the package being installed. This change enables developers to deliver packages that build on renamed object titles without re-applying the renames after every installation, and keeps titles consistent between the development and target environments. |
UI Design | Freedom UI components | Added click rate limiting support to the Button component using new The The |
Integrations and APIs | File processing | Fixed a runtime issue where file content written through the |
Integrations and APIs | Chats | Added the ability to define custom identifiers for omnichannel chat channels. Previously, a custom channel had to use an identifier from the fixed list of channel providers, which could not be extended. It was therefore not possible to set up more than one channel of the same type. This change resolves the messenger by the |
Administration
Category | Feature | Description |
|---|---|---|
No-code tools | Creatio theming | Added Theme Designer to create and customize Creatio themes. The designer opens when clicking the The designer includes: To save changes, click the Save button. |
No-code tools | Creatio theming | Added a new Theming tab to the Appearance setup section to centralize the management of all available themes in one place. The tab includes the Themes expanded list, which displays every theme discovered in the file content of active packages, excluding the built-in Freedom theme. The list includes the "Name," "Enabled for users," "Default," and "Package" columns. Administrators can rename a theme and select its Enabled for users and Default checkboxes. Changes are applied immediately after saving. This change enables administrators to manage all available themes from a single centralized location, reducing the effort required to configure, enable, or remove themes across the environment. |
System settings and tools | System Designer | Changed the location of desktop management functionality by moving it from the Appearance setup section to a new Desktop setup section in the System Designer. Previously, desktop configuration was only accessible through the Appearance setup section, which is licensed and unavailable for the Growth subscription plan. This unintentionally restricted access to desktop management as well. The desktop configuration options themselves remain unchanged. This change ensures that desktop management is available regardless of subscription plan, giving administrators consistent access to this functionality. |
Performance | System performance | Fixed a runtime issue where a query rule with an unresolvable "Schema" ( |
Performance | System performance | Fixed a runtime issue where the rule and action caches in the |
Performance | System performance | Fixed a runtime issue where the |
Logging and monitoring | Configuration activity log | Added a new "get_text_file_content" MCP tool that lets a connected AI Agent read the text content of a file stored in Creatio by its file ID. Previously, an MCP-connected AI agent had no way to retrieve the content of a file, for example, an installation log attached to a configuration activity log record. This limited its ability to analyze such files as part of troubleshooting. The tool is published through Creatio's existing MCP publishing mechanism and returns the file's text content for any file ID to which the agent has access. This change enables AI Agents to read files stored in Creatio, for example, installation logs, as part of automated analysis tasks like investigating installation or compilation issues. It removes the need for a person to retrieve and pass the file content manually. It is intended as a first step toward AI-driven root cause analysis, for example, correlating configuration activity log records with attached installation logs. |
Logging and monitoring | Configuration activity log | Added the Replaced column to the Configuration activity log section and Replaced checkbox to the log page for the "Create," "Update," and "Delete" operations on replaced schemas. Previously, these records did not indicate whether the schema that was created, updated, or deleted was itself a replacement of another schema. This made it harder to distinguish standard schema changes from replacement-related changes during an audit. The checkbox is set automatically based on whether the affected schema is a replacement of another "Object" or "Client module" type schema. This change enables administrators and support specialists to identify replacement-related schema changes directly from the log without inspecting the schema itself, speeding up configuration audits and troubleshooting. |
Logging and monitoring | Configuration activity log | Added the ability to generate a human-readable AI explanation of schema changes from a configuration activity log record using the Explain with AI button on the log record. This submits the record's unified diff and the verbatim before/after file versions as file attachments to a new Human-Readable AI Explanation agent running the GPT-5.6 Luna model. The button is available when the record has comparable changed files. The resulting explanation is appended to the Description field on the General information tab, after any existing platform-generated description text and separated by a horizontal rule. The explanation is generated only once per record. The AI-generated response is escaped and rendered from Markdown through a fixed, server-side element set, rather than allowing arbitrary markup from the model. A Regenerate button enables the user to request a new explanation on demand. The response always includes a disclaimer that the content is AI-generated. A reduced-coverage note is shown when not every changed file could be attached to the request, since at most 50 files are sent per request. The functionality is available for users registered in Creatio AI Studio, on environments where AI Twin is configured. This change enables administrators to understand a schema change without manually reading the raw diff, while still being able to verify the AI-generated summary against the change details themselves. To use this functionality, make sure that: Creatio Business Studio is integrated with the Creatio AI Studio, where the agent is deployed and reachable by agent ID and slot. The following system settings are populated: |
Logging and monitoring | Configuration activity log | Added support for comparing changes to packages in the Change details tab on the log page in the Configuration activity log section. Previously, Creatio could only build a comparison for "Schema"-type records, requesting a comparison for a package record returned no diff. The comparison for a package is now built from the "app-descriptor.json" and "app-descriptor-extension.json" files of the current and immediate previous version of that package. It uses the same response contract and UI already used for schema comparisons. When no previous comparable version exists, or a required descriptor file is missing or contains invalid data, Creatio now returns a deterministic "Unavailable" result with a reason instead of failing with an unhandled error. Existing authorization rules are enforced, so no comparison data is returned to a user who is not permitted to see the underlying package. Existing schema comparison behavior and its response contract remain unchanged. This change enables administrators and developers to review package-level configuration changes with the same level of detail already available for schema changes, without needing a separate tool. |
Logging and monitoring | Configuration activity log | Added support for comparing changes of "Data" type schemas in the Change details tab on the log page in the Configuration activity log section, regardless of which operation logged the change. Previously, compared content was reliably generated only for schema modifications made through the |
Logging and monitoring | Configuration activity log | Added the "Save schema files snapshot" ( |
Logging and monitoring | Configuration activity log | Changed the way configuration activity log backups are configured. Previously, backup creation behavior for the configuration activity log was managed through the |
Logging and monitoring | Configuration activity log | Changed the calculation of the backup file size in the configuration activity log to use the size of the resulting backup *.zip file. Previously, the size was calculated as the combined size of the individual *.gz files before compression. This provides a more accurate size check against the limit determined by the "Max configuration backup size, MB" ( |
Logging and monitoring | Configuration activity log | Changed the format of the "Install" operation recorded in the configuration activity log to be consistent across all installation sources. Previously, the same install action could be logged differently depending on where it originated, for example, as a "Create" operation for the package from one source and as an "Install application" operation from another. This made it difficult to reliably track and compare "Install" operations across Application Hub, WorkspaceConsole, and Clio utilities. Install operations from all these sources are now recorded under a single parent operation, "Install application or package." This parent operation contains the main configuration activity log record along with the child operations specific to the originating source. This change enables administrators and support specialists to consistently locate and interpret "Install" operations in the configuration activity log regardless of the installation source, simplifying auditing and troubleshooting. |
Logging and monitoring | Configuration activity log | Fixed a runtime issue where a failed app installation was recorded in the configuration activity log with a "Success" status, and the installation log file was not attached. This happened when the installation failed without throwing an exception, for example, when the installed packages could not be confirmed. In that case, the configuration activity log record was never finalized and kept its default "Success" status, with no duration, description, or attachment. Installations that failed with an exception were already finalized correctly, which is why the issue appeared to affect only some installations. The installation operation record is now finalized on every exit path across Application Hub, WorkspaceConsole, and Clio utilities. Finalization now writes the actual status ("Success" or "Error"), the operation duration, the modification timestamp, and a description of the outcome. It also attaches the installation log file whenever a description is present. This change enables administrators and support specialists to consistently rely on the configuration activity log status to detect failed app installations across Application Hub, WorkspaceConsole, and Clio utilities. They no longer need to separately inspect the installation log or the Application Hub. |
Logging and monitoring | Configuration activity log | Fixed a runtime issue where a configuration compilation or app installation operation interrupted by an unexpected app restart was recorded in the configuration activity log as successful, or was missing from the log entirely. Neither outcome reflected the actual failure. Such an operation is now recorded with an "Error" status instead of "Success" or a missing record. This change enables administrators to reliably detect configuration compilation and installation operations that were interrupted by an unexpected app restart. |
Logging and monitoring | Configuration activity log | Fixed a runtime issue where configuration activity log records for the same operation could be logged under two different users. Previously, an administrator other than the system user could install an app, create an app, create or update a section, or save or delete a schema in a designer. Part of the resulting log records included the user who performed the action. The rest included the system user instead, because those steps run internally on the system connection. Examples include generating source code, installing data, generating static content, generating runtime metadata of an "Object" type schema, updating the database structure, and creating localizations. Configuration activity log records for these operations, including operations without a parent record, are now consistently logged under the user who initiated the operation, regardless of which internal connection performed the underlying work. This change enables administrators to reliably audit who performed a configuration change by trusting the author included in the configuration activity log. |
Logging and monitoring | Configuration activity log | Fixed a runtime issue where saving a business process could fail and abort the save if writing an audit record to the configuration activity log failed at the same time. This could happen, for example, due to a foreign key error when a child configuration activity log record was written before its parent record had committed. Previously, this kind of configuration activity log write failure propagated to the business process save and was reported to the user as a save error. A failure while writing to the configuration activity log no longer interrupts or fails the operation being audited, for example, saving a business process. This change enables users to save business processes reliably even if an audit record cannot be written at that moment, instead of having the save itself fail because of an unrelated logging error. |
Logging and monitoring | Configuration activity log | Fixed a runtime issue where a deadlock could stall saving a business process version, or using the Set as actual version action, for up to 500 seconds. Other requests on the same node were blocked while it lasted. The Set as actual version action is available in the |
Logging and monitoring | Configuration activity log | Fixed a runtime issue where "Client module" type schemas were not tracked in the configuration activity log when a new section was created in an app built based on the template. Previously, opening the parent "Create" record for the new section did not show change details for these schemas. "Client module" type schemas created together with a new section in a template-based app are now tracked in the configuration activity log, together with their change details. This change enables administrators to fully audit schema changes introduced when adding sections to template-based apps. |
Logging and monitoring | Configuration activity log | Fixed a runtime issue where an error occurred when a user created, edited, or deleted a record of the "Activity" ( |
Creatio maintenance | Caching | Changed the cache invalidation logic for the IndexedDB storage by excluding column changes that do not affect page rendering from the cache reset conditions. Previously, the cache was reset on changes that had no impact on the rendered page, which discarded valid cached data and forced Creatio to rebuild pages on the next load. This change reduces page loading time at runtime for administrators and end users and lowers redundant client-side processing on environments where configuration changes are frequent. |
User and access management | Organizational roles | Added the Synchronize with LDAP checkbox and the LDAP element field to the Managers tab of the organizational role page. Previously, LDAP synchronization was configured for the organizational role only, and users had to be added to the management role manually after every change in the corporate folder. LDAP synchronization remains unchanged in all other scenarios. This change enables administrators to bind an LDAP element to the management role of an organizational role. The users of that element are included in the role automatically during synchronization, in the same way as for existing LDAP element to Creatio role bindings. This keeps management permissions aligned with the corporate folder without manual role assignment after every staff change. |
User and access management | Access rights | Added the ability for administered operation right changes to take effect without a re-login. Previously, the current user's administered operations were served from a session-scoped cache that nothing invalidated: the operation was updated only in the "Permission granted to" ( |
User and access management | Object permissions | Added the ability to control access to the "Chat queue" ( |
User and access management | Object permissions | Added the ability to control access to records of the "Attachments and notes detail object in "Services" section" ( |
User and access management | System operations | Added the ability to control who can change the "Default theme" ( |
User and access management | Single Sign-On | Added an API that registers an OpenID SSO provider on a Creatio instance in a single call. Previously, an OpenID provider had to be registered manually by an administrator, which made it impossible to configure SSO as part of an automated environment provisioning flow. The API accepts the code, display name, issuer URL, client ID, and client secret of the provider, and optionally the auto-login setting. It creates the provider record configured against the supplied issuer, enables it, and returns the identifier of the created record. Registration is atomic, so no partial provider record remains if any step fails. A call with a code that already exists, a missing required field, or an issuer URL whose discovery document is unreachable returns a validation error and creates no record. The API is used by the Clio utility, so an SSO provider can also be registered from the command-line interface. This change enables administrators and provisioning tools to configure SSO on a new environment automatically, without registering the provider by hand before users can sign in. |
User and access management | Single Sign-On | Added the "OIDC user identity" ( |
User and access management | Single Sign-On | Added the OIDC user matching rules expanded list to the Single Sign On configuration section in the System Designer. The list resolves an incoming SSO identity to an existing Creatio user when no OpenID Connect identity record matches. Previously, a user who had been created in Creatio before being onboarded to OpenID Connect, or who signed in through a second OpenID Connect provider for the first time, was not recognized. The login then attempted to create a new user and either failed with a duplicate error on name or email, or silently created a duplicate user record. Customers therefore had to pre-populate identities for every existing user before rollout. Each rule maps a claim of the identity provider token to a column of the "System administration object" ( |
User and access management | Single Sign-On | Added the ability to enable token-based sign-in to the Creatio Mobile app on Microsoft Intune-managed devices. Administrators do this using the "MSAL Mobile sign-in via Entra Id" value when adding the provider in the External identity provider expanded list of the Single Sign On configuration section in the System Designer. Administrators register the provider using the values from the Creatio Mobile app registration on the Microsoft Entra ID portal. Creatio receives ID and access tokens through MSAL, with Microsoft Company Portal used as the broker app. Creatio then validates the received token and resolves the Creatio user, whose identity and permissions are used for the entire mobile session. Previously, authorization on Microsoft Intune-managed devices was possible, but a seamless sign-in experience was not. Users entered their credentials manually in the Creatio Mobile app, unlike in their other corporate apps. This change enables administrators to deliver corporate-grade sign-in for the Creatio Mobile app through a dedicated provider. The provider is configured separately from the web SSO provider. Existing SSO configurations remain unchanged. |
User and access management | Single Sign-On | Added the key identifier ( |
User and access management | Single Sign-On | Changed the OpenID Connect SSO login flow to apply user matching rules even when JIT provisioning is disabled. Previously, disabling JIT provisioning also disabled automatic matching to existing users, so SSO logins were not linked to the user records created by an administrator, and an administrator-controlled provisioning model could not be configured. Creatio now evaluates the rules of the OIDC user matching rules expanded list in the Single Sign On configuration section of the System Designer in priority order. It resolves the incoming identity to an existing user by the mapped column of the "System administration object" ( |
User and access management | Single Sign-On | Fixed a runtime issue where login through an OpenID SSO provider failed when the provider had been registered through the provider registration API. Previously, the client secret of such a provider was encrypted twice when it was saved. The value sent to the identity provider during the authorization code exchange therefore did not match the configured secret, and the identity provider rejected the request as an invalid client. The user received a general login error that gave no indication that the stored client secret caused the issue. Creatio now encrypts the client secret once when it is saved, so the value sent during the token exchange matches the secret that was configured. This change enables administrators to register OpenID SSO providers programmatically and have users sign in on the first attempt, instead of investigating a login failure that the error message does not explain. |
User and access management | Single Sign-On | Fixed a runtime issue where the "Default identity provider" ( |
button or theme name in the Themes expanded list in the Theming tab in the Appearance setup section. This change enables administrators and no-code creators to create and adjust custom themes visually, without manually editing theme files, and to validate the visual result immediately before applying a theme.
button menu on the Versions detail on the Process versions tab of the business process page in the Process library section. This occurred when the End user experience
Category | Feature | Description |
|---|---|---|
Communications | Notifications | Fixed a runtime issue where the notification mark did not appear in the "Feed" sidebar on the communication panel after a new system notification arrived. This happened when that panel was already open in another browser tab of the same session. Previously, this could happen, for example, a notification about updated record permissions. The notification mark now appears in the "Feed" sidebar on the communication panel in this scenario, regardless of which action generated the notification. This change enables users to reliably notice new system notifications on the communication panel. |
Communications | Message templates | Added a new |
UI and navigation | Creatio login page | Added support for custom logo configuration on the Creatio login page for .NET builds. Previously, this functionality was available only for .NET Framework builds. This change ensures .NET and .NET Framework builds now support the same login page branding configuration. |
UI and navigation | Workplaces | Added the Segments section to the "Marketing" workplace. Previously, users added the section to the workplace manually using the Workplace setup section in the System Designer. This change enables marketers to build audiences and set up campaigns within a single workplace, without configuring the workplace manually. |
UI and navigation | Workplaces | Fixed a runtime issue with the user group setup of the "My applications" workplace whose "Usage type" column in the Workplace setup section is set to "Web." Previously, on fresh deployments the workplace could be created without the "System administrators" user group in the User groups detail on the Workplace setup tab of the workplace page. Its user groups were then empty, and the workplace was unavailable to administrators until the role was added manually. This change ensures that administrators can access the "My applications" workplace immediately after deployment, without manual post-installation setup. |
UI and navigation | Workplaces | Fixed inconsistent selection for primary Freedom UI sections that share the same code on one object. Previously, the primary section was resolved using the first workplace accessible to the user by position, rather than the workplace the user actually had open, and the outcome could vary depending on the Creatio database. Users with different workplace access, or the same data on different database frameworks, could see different sections in the navigation panel. This led to inconsistent navigation from global search, record links, and other flows that open a record without specifying a section. The primary section is now resolved based on the workplace the user actually has open, with a consistent result across database frameworks. Creatio now selects the section present in the current workplace first. If none is present, the section from the highest-priority accessible workplace is used. Otherwise, any remaining candidate is used. Primary section ordering in the "All Apps" workplace now follows the alphabetical order of section captions instead of falling back to the first accessible workplace. This change enables users to consistently reach the correct record section from global search and other primary-section-dependent flows, regardless of the database framework or their workplace configuration. The new logic applies only when the "Use Freedom UI interface" ( |
UI and navigation | App management | Fixed a runtime issue where the icon of the Web Chat app in the New application window in Application Hub was displayed with a green background instead of a transparent background. The issue occurred when adding a new app or editing an existing app. This change ships a correctly formatted icon with a transparent background, ensuring the Web Chat app icon matches the other app icons in the Application Hub. |
UI and navigation | Pages | Changed the backward navigation behavior in the Freedom UI so the "Close" action and the browser Back button open the desktop whenever no in-app page remains below the current page. Previously, opening a Freedom UI page through a redirect from a Classic UI link left a stray Classic UI record in the browser history. "Close" action or Back button could then return users to that Classic UI page instead of the desktop, or exit the instance entirely once that record was consumed. The changes are applied automatically when updating to version 10.1 Unlimited. This change enables users to rely on consistent, predictable backward navigation for Freedom UI pages, reducing support requests caused by users unexpectedly landing on outdated Classic UI pages or leaving the instance. To stop using the functionality, register and enable the |
UI and navigation | Pages | Fixed a runtime issue where saving a record returned an error. This happened on a Freedom UI page that has an additional data source related to the primary data source by a "Guid" type column, for example, |
UI and navigation | Pages | Added support for theming in the blank-slate illustration on the feed. Previously, its colors and white background were hard-coded. This change makes the illustration use the |
UI and navigation | Pages | Fixed a runtime issue where the activity status was not set to "Finished" when a user completed an activity with a pre-filled result from the "Activity mini page (Freedom UI)" ( |
UI and navigation | Pages | Fixed a runtime issue where the "The page contains unsaved changes" dialog appeared when a user completed two or more next steps in a row through the "Activity mini page (Freedom UI)" ( |
UI and navigation | Pages | Fixed a runtime issue where progress bars did not load on Freedom UI sections, such as Cases and Leads, for regular and portal users. Previously, the mechanism responsible for initializing progress bars failed for non-administrator and portal users because the underlying schema lacked the necessary access rights after a related schema change. Administrators were unaffected, since they bypass object-level access rights, so accurate section progress visibility was previously available only to administrators. Progress bars now load correctly for administrators, regular users, and portal users alike. This change restores accurate section progress visibility for regular and portal users in Freedom UI. |
UI and navigation | Pages | Added the ability to attach files from Creatio sections to an email in the message composer. Previously, the |
UI and navigation | Pages | Added the ability to save an advanced filter or one of its top-level groups as a folder using the |
UI and navigation | Pages | Added the ability to automatically pre-fill the To, CC, and BCC fields of the message composer based on the current record, for example, the account or contact page. Previously, this functionality was available in Classic UI only. This change enables users to send emails from pages without entering recipients manually. Recipients already present in the composer, for example when a user replies to a message from the timeline, are not overridden. |
UI and navigation | Pages | Changed the recipient search in the To, CC, and BCC fields of the message composer in the email mini page to return the same results as global search. Previously, the composer split the query into words, kept only the records that contained every word after the ElasticSearch response, and returned at most the first 15 hits. Results were incomplete, differed from global search, and were slow for broad queries. To use this functionality, register and enable the |
UI and navigation | Pages | Fixed a runtime issue where the attachment extension check in the message composer blocked valid file types. File type restrictions are managed by the "File extensions deny list" ( |
UI and navigation | Pages | Fixed a runtime issue where the message composer overwrote the Subject entered by the user with the default Title field value passed from the page, for example, the case number, when the email draft was saved. Previously, the page default values were applied after the composer had set the |
UI and navigation | Pages | Fixed a runtime issue where the quote of a plain-text email was broken in the message composer, and saving the email page corrupted the original email. Previously, when a user replied to or forwarded an email that had arrived as plain text and expanded the quote, the quoted text lost its line breaks, and addresses in angle brackets disappeared because they were parsed as HTML tags. Saving the email page then overwrote the stored body of the original email with escaped markup. This change keeps line breaks and angle brackets intact in the quote, and no longer changes the original email when the page is saved. |
UI and navigation | Pages | Fixed a runtime issue where the blank slate animation of the timeline did not follow the applied theme. Previously, the animation was rendered outside the placeholder component and used hard-coded colors on an opaque background, so it kept the same appearance regardless of the theme and looked inconsistent in custom and dark themes. This change renders the animation through the placeholder component, makes it react to the |
UI and navigation | Pages | Fixed a runtime issue where an email that had an empty body was displayed with a permanent loading mask in the timeline. Previously, the mask was shown whenever the email body was empty, which did not distinguish an email whose body had not been loaded yet from an email that had no body at all. An email that contained only a subject and an attachment displayed a loading mask that never disappeared, and users assumed the content had failed to load. This change drives the mask by the actual loading state and hides it once Creatio finishes retrieving the email content, while emails whose body is loaded separately because of its size continue to display the mask. Users no longer see misleading loading masks in the timeline, and it is clear when an email has no body text. |
UI and navigation | Pages | Fixed a runtime issue where the secondary field disappeared from narrow calendar events for timed activities that share a time slot. Previously, when the event content did not fit vertically, the |
UI and navigation | Pages | Fixed a runtime issue where an activity that spanned multiple days was drawn one day shorter in the Calendar section. Previously, Creatio stored the due date as the inclusive end of the activity, while the calendar expected the end of an all-day event to point at the next day and truncated it to the start of that day. This change extends the end of such activities so that they cover every day up to and including the due date, letting users see the real duration of multi-day activities. |
UI and navigation | Pages | Added the ability to resize the Filters toggle panel horizontally by dragging its right border. Previously, the panel used the fixed width configured in the Freedom UI Designer at runtime, which made filters that have multiple conditions and nested groups difficult to read. This change enables end users to adapt the Filters toggle panel to complex filter structures without requesting a page change from a no-code creator. No-code creators, in turn, can maintain a single page configuration that suits users who have different screen sizes and filtering habits. To stop using this functionality, register and enable the |
UI and navigation | Pages | Added the ability to disable and enable individual conditions, groups, and predefined presets in the filters. Previously, a condition had to be deleted to exclude it from the filter and re-created to apply it, causing intermediate filter logic to be lost. This change excludes a disabled condition from the query that the filter generates, keeps the condition visible in the filter, and displays it in a distinct color. End users can now test variations of a complex filter without rebuilding conditions, which also lowers the risk of losing filter logic that is only temporarily not needed. |
UI and navigation | Pages | Changed the filter editor that opens in the Setup filters window when clicking the |
UI and navigation | Pages | Replaced the static icon in the blank state of the filters with an animated icon. Previously, the blank state displayed a static illustration, which was inconsistent with the animated blank-state icons already used in other components. This change ensures consistent visual representation of blank states across components. |
UI and navigation | Pages | Fixed a runtime issue where the email page opened from a business process through the Open edit page element. Previously, when the page was opened this way from the Process library section and the user edited the draft and clicked Send, the email could be sent with the old body. After sending, the page also showed outdated data. This change makes the page send the current body and refresh its data after the email is sent, letting users edit and send drafts opened by a process safely. |
button uploaded files only from the user device. This change enables users to attach existing Creatio records to an email in one action and enables administrators to expose any section as an attachment source without additional coding.
icon in the Folders toggle panel. Previously, the window opened the Classic UI advanced filters editor. To stop using the functionality, register and enable the Creatio Mobile
Category | Feature | Description |
|---|---|---|
Integrations and APIs | OAuth authorization | Added support for automatic detection of the authentication type in Creatio Mobile for Android and iOS. Previously, Creatio Mobile did not check whether the authentication type configured on the server had changed. When the server returns a 401 Unauthorized status code during synchronization, Creatio Mobile now requests the current authentication type from the server before it opens the login page. Creatio Mobile then uses the updated authentication type, for example, OAuth 2.0. The changes are applied automatically when updating the Creatio Mobile app. This change enables administrators to switch the authentication method on the server without asking mobile users to sign out and sign in again manually. It also reduces the number of support requests after authentication settings are updated. |
Beta testing of new features
Category | Feature | Description |
|---|---|---|
WhatsApp Chat Channel | Customer communication hub section | Added the ability to connect the WhatsApp number of an individual employee to Creatio using the Add channel button list in the Manage channels toggle panel of the Customer communication hub section. The WhatsApp chat channel connects a WhatsApp Business account to Creatio through the Meta Cloud API. The functionality is based on WhatsApp Coexistence, the capability that enables the same number to be used in the WhatsApp Business app and in the WhatsApp Business Platform at the same time. Previously, WhatsApp did not allow the same number to be used in the WhatsApp Business app and the WhatsApp Business Platform at the same time. Employees can now connect their number as a personal channel and keep chatting from the WhatsApp Business app on their phone, while every chat from the phone is synced into Creatio at the same time. To use this functionality, register and enable the AI automation is not available for a personal channel, and the AI automation tab is hidden on the WhatsApp chat channel settings pages. |
Integrations and APIs | Emails | Added support for SMTP sending without authentication for mailboxes marked as anonymous. Previously, the Exchange Listener always authenticated on SMTP, so a mailbox that sends through a corporate relay accepting unauthenticated messages could not be used in Creatio. To enable this functionality, execute the |
UI and navigation | Pages | Added support for Creatio.ai-assisted filter creation in the Filters toggle panel. Previously, users had to build every condition manually by selecting columns, operators, and values, which required knowledge of the object model and the data structure. Users can now enter a free-form description of the required filter and let AI Twin generate the filter conditions automatically. After clicking the |
button in the message composer inside the Filters toggle panel, Creatio displays the standard loader. Creatio then opens the generated filter, where it remains available for review and editing. Users can also adjust the filter using Creatio.ai without rewriting the original prompt. The functionality is available for users registered in Creatio AI Studio, on environments where AI Twin is configured. This change enables users to assemble filters on their own without understanding the underlying data model, and reduces the time administrators spend assisting users with complex filter setup. To stop using this functionality, register and enable the 
button, placed on the same level as the Apply and Clear all buttons.