10X Unlimited changelog
This document details the technical changes and enhancements introduced in Creatio 10X 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 10X 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 | Creatio AI app development toolkit | Replaced the directory of instructions used by the Creatio AI app development toolkit with the "Creatio-app-orchestrator" AI Skill. Previously, coding agents such as Claude Code, Codex, and GitHub Copilot referenced the instructions distributed as a folder directly. Coding agents now use the guided toolkit instructions through a skill. This change gives developers a simpler and more consistent way to invoke the toolkit instructions across supported coding agents. |
Creatio.ai | Creatio AI app development toolkit | Added support for creating and configuring business rules and placing metrics on existing pages using coding agents. Previously, business rules and widget placement required manual configuration in the respective designers. This change enables coding agents to automate UI behavior configuration and widget setup as part of development workflows. Creatio AI app development toolkit supports the following: |
Common features
Category | Feature | Description |
|---|---|---|
Customer 360 | Contact page | Added the Manager field to the Contact info tab of the contact page. The field lets users store a direct contact manager and includes values from the Contact lookup. Out of the box, the lookup is unregistered. To register it, add a lookup based on the "Contact" ( |
Productivity | AI and automation | Fixed a runtime issue when the "New meeting" AI Sub-agent added incorrect or missing attendees. Previously, the sub-agent could resolve a participant to an identifier from a non-contact and pass it to meeting creation, so some requested attendees were omitted. This change updates the sub-agent to search each participant separately, treat only contacts as valid attendees, and exclude unresolved participants from meeting creation while reporting them back to the user. |
Creatio Marketing
Category | Feature | Description |
|---|---|---|
Marketing campaigns | Campaign Designer | Added a new "Records in a specific segment" value to the Specify which records will be converted to the campaign audience parameter of the Add audience and Exit from campaign elements in the Campaign Designer, allowing users to search for and select a single segment compatible with the selected source object. The value is available only when the Select an object (entity) that holds the campaign audience data parameter of the Add audience element is set to "Contact." Segment membership is evaluated at execution time — contacts that enter or leave the segment afterward are not enrolled or removed automatically unless the element runs again. To use this functionality, create and activate a segment in the Segments section. After that, the segment is available for selection in the Add audience and Exit from campaign elements of the Campaign Designer. |
Marketing campaigns, | User and access management | Changed the subscription model for Creatio instances that have Marketing campaigns, Digital Ads, Lead Generation, Email Marketing, Event management apps installed. Instances that have no unsubscribe feedback and no records in the |
Lead Generation | Landing page | Fixed a runtime issue where hidden non-string fields on landing pages submitted an empty string in the webhook payload instead of the configured default value. Previously, the input type of such fields was overridden to "hidden" regardless of the original field type, so browsers ignored the checked attribute of "Boolean" type fields such as checkboxes and serialized their value as an empty string. |
Lead Generation | Submissions section | Added external form capture functionality to the Lead Generation app. The functionality enables automatic collection of submissions from static HTML forms on external websites without rebuilding forms in Creatio, preserving the existing web infrastructure. The tracking script required for form capture can be obtained per environment from the Submissions section using the "Get external form capture script" section action. Administrators can define allowed domains to ensure submissions are collected only from websites. |
Lead Generation | Embedded forms section | Added a new Embedded forms section to create reusable forms, map form fields to a target object, and publish each form as a stable embed code snippet that can be placed on any external website. It is delivered as part of the Lead Generation app compatible with Creatio 8.3.4 and later and is displayed in the "Lead Generation" workspace. Previously, forms could be created only as part of a landing page and were bound to it, which prevented reuse across multiple websites. Updates to a published form are applied centrally without repasting the embed code. |
Lead Generation | Freedom UI components | Added pre-defined filters available in the Add new filter button list when clicking the Filters button in the Contacts section. The filters target specific lead capture sources and are implemented using the Filters Freedom UI component. They are delivered as part of the Lead Generation app. Previously, building these required manual configuration with no out-of-the-box reference. Available pre-defined filters: "Facebook submissions," "Submissions from Creatio landing pages," "Web page visitors." |
Lead Generation, | Freedom UI components | Added pre-defined filters available in the Add new filter button list when clicking the Filters button in the Contacts section. The filters target distinct campaign lifecycle states and are implemented using the Filters Freedom UI component. They are delivered as part of the Lead Generation, Email Marketing, Event management apps. Previously, building these filters required manual configuration with no out-of-the-box reference. Available pre-defined filters: "Currently in campaign flow," "Never participated in any campaign," "Participated in campaign flow," "Reached campaign goal." |
Event management | Freedom UI components | Added pre-defined filters available in the Add new filter button list when clicking the Filters button in the Contacts section. The filters target distinct event attendance outcomes and are implemented using the Filters Freedom UI component. They are delivered as part of the Event management app. Previously, building these filters required manual configuration with no out-of-the-box reference. Available pre-defined filters: "Participated in events," "Registered for event but did not attend." |
Segmentation | Segment management | Added a segmentation engine that manages pre-computed audience segment membership and exposes it through DataService, Added the Segments section for managing audience segments. When a user creates a segment and sets up entry rules that define which contacts enter the segment, the Matching contacts metric on the segment page shows the number of contacts that meet the entry rules. Active segments cannot be edited and can only be re-populated using the previously set entry and exit rules. When a user deactivates a segment, it moves to the "Paused" status. When the segment is activated again, the user can choose to repopulate it from scratch or top it up with new contacts. A user controls the segment status with the corresponding buttons. Segments are available for the "Contact" ( Added the "Segment" ( Added the following lookups that drive segment behavior: Added automatic provisioning of a dedicated Added the Added the |
Segmentation | Segment management | Added duplicate-name validation on the "Segment" ( |
Segmentation | Segment management | Added the "Are in segment" and "Are not in segment" pre-defined filters available in the Add new filter button list when clicking the Filters button in the Contacts section. The filters target contacts based on their segment membership and are implemented using the Filters Freedom UI component. They are delivered as part of the Segmentation app. To stop using this functionality, register and enable the |
Segmentation | Segment management | Added a configurable timeout for segment actualization. The timeout is managed by the "Segment candidate tables maintenance database command timeout (seconds)" ( |
Segmentation | Segment management | Added the "Queued" value to the lookup based on the "Segment system status" ( The |
Segmentation | Segment management | Added the "Is usable while updating" ( |
Segmentation | Segment management | Added orphan cleanup to segment actualization. Previously, when a record was deleted from the target object, its ID remained in the |
Segmentation | Segment management | Added the optional The same behavior is available in the UI through the "Replace — start fresh" option in the Segment resume mode field of the Resume and re-populate mini page that opens after clicking the Resume segment button on the segment page. The response reports the number of removed and added members in the |
Segmentation | Segment management | Added configurable exit rules to the data segmentation engine that control how segment members are removed during actualization. Each segment references exit rules defined in the Segment exit strategies lookup, and the actualization service applies the selected rule on every cycle. Available exit rules: "No longer matches entry," "On specific conditions," "Never exits." Removal is performed as a soft delete that sets the |
Segmentation | Segment management | Added the Unlike segment actualization, which performs a soft delete by setting |
Segmentation | Segment management | Added the |
Segmentation | Segment management | Added column-level access enforcement to segment filters and to the The |
Lead Generation | Landing pages section, | Added live web tracking to capture visitor web activity on Creatio landing pages and external websites and connect anonymous activity to known Creatio contacts. It is delivered as part of the Lead Generation app compatible with Creatio 8.3.4 and later and is displayed in the "Lead Generation" workspace. Previously, visitor actions on landing pages could be captured via Matomo or Google Analytics but with a 24-hour time lag only. Tracking scripts are injected automatically when a Creatio landing page is published or exported in the Landing pages section, and external websites can be connected for tracking in the Web analytics section using the Settings button, which generates an embeddable tracking script for the external domain. When live web tracking is enabled, the Creatio web analytics script replaces the Google Analytics script previously added via the Connect Analytics tab on the landing page. Once a visitor submits a form on a tracked page or follows a personalized bulk email link, anonymous activity is linked to a contact and subsequent web actions are recorded in near real time. Captured web activity is displayed in the Web sessions and Web actions expanded lists on the Marketing tab of the contact page. This change gives marketers near real-time visibility into contact web behavior, so they can follow up based on actual browsing activity. |
Creatio Sales
Category | Feature | Description |
|---|---|---|
Lead and Opportunity Management | Opportunity page | Added the Forecast category field to the opportunity profile on the opportunity page. The field classifies each opportunity by its forecast position. Previously, the opportunity page provided no built-in forecast classification, and the forecast category was not visible in the change history. Changes to this field are now saved in the change history. |
Lead and Opportunity Management | Opportunity page | Added the MEDDPICC tab to the opportunity page. The tab lets users qualify an opportunity using the MEDDPICC framework. Previously, sales teams tracked MEDDPICC assessments outside Creatio. |
Lead and Opportunity Management | Opportunity management | Added the |
Sales Engagement | Sequence page | Added the |
Sales Engagement | Sequence page | Added drag-and-drop steps to the Steps tab of the sequence page. Users can now drag a step using the drag handle, and the new order is saved when the step is dropped. Clicking fields, buttons, or menus of a step does not start a drag. |
Sales Engagement | Sequence page | Added automatic naming for new steps when configuring a sequence on the Steps tab of the sequence page. Previously, step names had to be entered manually. Existing step names are left unchanged. |
Sales Engagement | Sequence page | Added per-step execution statistics to the steps on the Steps tab of the sequence page. Each step card now shows how many participants are in each state, with type-specific metrics. |
Sales Engagement | Sequence page | Added a new "LinkedIn URL" variable to the Variables list for the Description field of "Call" and "Task" type activities and the Body field of "Email" type activities when configuring a step on the Steps tab of the sequence page. When selected, Creatio inserts the |
Sales Engagement | Sequence page | Added the ability to prevent a contact from participating in multiple sequences at the same time. To use this functionality, add the |
Sales Engagement | Sequence page | Added a new Reassign sequencer bulk action to the Sequence audience expanded list on the Audience tab of the sequence page. It lets you change a target sequencer for the selected participants, reassigning all upcoming steps and already-generated upcoming activities to the new owner. Completed, canceled, and historical work is left unchanged. After the action is completed, Creatio displays a notification with the number of reassigned, updated, and skipped contacts. If the target sequencer is inactive or ineligible, Creatio blocks the reassignment and displays a detailed error message. |
Sales Engagement | Sequence page | Added a new Activate bulk action to the Sequence audience expanded list on the Audience tab of the sequence page. Previously, each participant had to be activated individually. Creatio now validates that the participant and sequence can continue, moves the participant to "Active" status, and resumes or re-generates upcoming work without duplicating the participant or completed steps. |
Sales Engagement | Sequence page | Added a new required Email mode field to "Email" type activities when configuring a step on the Steps tab of the sequence page. Previously, an email step did not provide a per-step option to control whether the email was sent manually or automatically. Available field values: "Manual" and "Automatic." Out of the box, the value is set to "Manual." |
Sales Engagement | Sequence page | Added a new required Email threading mode field to "Email" type activities when configuring a step on the Steps tab of the sequence page. Previously, threading could not be controlled per step. Available field values: "New thread," "Continue previous." Out of the box, the value is set to "New thread." For the "Continue previous" value, if the recipient replied, that reply becomes the threading source and chained steps continue the latest applicable thread. |
Sales Engagement | Sequence page | Added email threading for sequences that include multiple "Email" type activities on the sequence page. Previously, sequence emails were not linked into a single conversation. Creatio now sends the first sequence email as the start of a conversation and follow-up emails as continuations that include the prior history, so recipients see one thread in email clients, for example, Outlook and Gmail. Threading is scoped per participant, recipient, and sequence — emails from different participants, recipients, or sequences are never merged. When a user opens a sequence email activity, Creatio displays previously sent emails of the same thread as a read-only, chronological history that preserves the sender, recipient, date, subject, and body. The Activity execution panel is unchanged and still uses the current template. |
Sales Engagement | Sequence page | Added automatic reaction to inbound replies for sequence emails. Previously, sequencers had to monitor replies manually and update participant status and stage by hand. Creatio now correlates an inbound reply to the originating outbound sequence email using the "Id" ( A reply from the primary participant updates the participant status based on the "When primary recipient replies" ( The participant stage is taken from the "Participant replies" ( A reply from a non-participant raises an alert task without affecting the primary participant. Re-importing an already-processed reply does not re-apply status or stage transitions. |
Sales Engagement | Sequence page | Added automatic processing of bounced sequence emails. Previously, bounced emails were not processed automatically, so invalid email addresses were not flagged and outreach continued. When a bounce occurs, Creatio now matches the event to the original sequence-generated "Email" type activity and participant, records the bounced result, sets the participant stage in the "Stage" column from the "Email bounces" ( |
Sales Engagement | Sequence page | Added end-to-end unsubscribe and opt-out handling for "Email" type activities. Creatio adds an unsubscribe link to every sequence email regardless of send mode, including automatic and manual sends and both new emails and replies in an existing thread, and does not add a second link when one already exists. When a recipient unsubscribes, all contacts that share the same primary email receive the "Not Interested" value in the "Stage" column and the "Paused" value in the "Status" column in the Sequence audience expanded list on the Audience tab of the sequence page and their active and pending participation is paused, so future sequence emails respect the unsubscribed state. |
Sales Engagement | Sequence page | Added a new Action field to "Task" type activities when configuring a step on the Steps tab of the sequence page. The field is required and the list of task actions is managed by the new Sequence step action lookup. The selected value is displayed when opening the "Task" activity type in the Activity execution panel. Available field values: "General task," "LinkedIn: Interact with post," "LinkedIn: Other," "LinkedIn: Send connection request," "LinkedIn: Send message," "LinkedIn: View profile." Out of the box, the value is set to "General task." |
Sales Engagement | Activity execution panel | Added a new Skip action to the menu of an activity opened in the Activity execution panel. When clicked, Creatio dismisses the current activity, sets its status to "Complete," sets the Result field to "Skipped," and advances the participant to the next step. The action is supported by all activity types. Unlike opt-out, the participant remains enrolled in the sequence. |
Sales Engagement | Sequences section | Changed the behavior of the Copy row action in the Sequences section. Previously, copying a sequence did not recreate its steps, requiring users to rebuild them manually. The action now recreates all sequence steps together with their parameters. |
Sales Engagement | Sequence page | Changed the scheduling logic for activity types on the Steps tab of the sequence page. Previously, the next activity was scheduled from the original planned due date. Creatio now schedules the next activity from the previous activity's actual completion time plus the step postpone time. |
Sales Engagement | Sequence page | Changed the sequencer resolution logic for sequence participants in the Sequence audience expanded list on the Audience tab of the sequence page. Previously, the sequencer was determined by a fixed rule that could not be changed without additional coding. Creatio now resolves the sequencer from a contact column managed by a new "Sequence participant sequencer column name" ( |
Sales Engagement | Sequence page | Changed sequence email sending to route all sends through a single queue with a configurable daily limit. Previously, sequence email sending was not centralized or throttled, and changing the dispatcher interval required Creatio restart. Both manual and automatic sends now go through one queue that respects a configurable daily limit per UTC day. Over-limit emails stay queued and resume the next day. Changing the dispatcher interval reconfigures the running job at runtime without Creatio restart. |
Sales Engagement | Activity execution panel | Changed the behavior of the Subject field when handling the "Email" activity type in the Activity execution panel. Previously, the subject had to be entered manually for each "Email" type activity. The Subject field is now inherited from the previous thread and cannot be edited. This change applies to the "Email" activity type whose Email threading mode field is set to "Continue previous" when configuring a step on the Steps tab of the sequence page. |
button to the sequence page. When clicked, Creatio reloads UI elements without requiring the user to reload the entire page.Creatio Service
Category | Feature | Description |
|---|---|---|
Contact Center | Agent Inbox panel | Added the ability to identify an anonymous web chat visitor and link the conversation to an existing contact in the Agent Inbox panel. Out of the box, web chats start without a linked contact because visitors are anonymous. Once the enabled AI Agent or a human agent identifies the visitor during the conversation, the agent can select the matching contact from the chat contact profile and confirm the link. This reassigns all chats of the current anonymous contact to the selected contact and updates the contact profile and chat messages automatically, without a page refresh. This change keeps the full interaction history consolidated under a single contact. |
Contact Center | Agent Inbox panel | Fixed a runtime issue where the agent status toggle did not appear after closing the Agent Inbox panel and refreshing the page. |
Contact Center | Agent Inbox panel | Fixed a runtime issue where the Agent Inbox panel did not open automatically on an incoming call. Previously, an incoming call appeared in the status toggle but the panel did not react. The panel now opens automatically and restores its previous display mode when a call arrives. |
Contact Center | Agent Inbox panel | Fixed a runtime issue where the |
Contact Center | Agent Inbox panel | Fixed a runtime issue where the Agent Inbox panel opened automatically while the user was working in the "Chats" sidebar of the communication panel. The issue occurred when the user sent a message from an existing chat, opened an active chat from the list, or changed the agent status toggle. The Agent Inbox panel now stays closed in these cases. |
Contact Center | Agent Inbox panel | Fixed a runtime issue where attachments exceeding the limit defined by the "Attachment max size" ( |
Contact Center | Agent Inbox panel | Fixed a runtime issue in the Agent Inbox panel where pressing Enter did not send a message that contained only an attachment with no text. |
Contact Center | Agent Inbox panel | Fixed a runtime issue in the Agent Inbox panel where the chat transfer details in the chat tile showed the technical user name instead of the AI assistant personality name for chats transferred from the AI assistant to a chat agent. |
Contact Center | Customer communication hub section | Added the Chat queues and Chat actions expanded lists to the Chat routing tab of the Customer communication hub section. Administrators can view, create, edit, and delete chat queues and chat actions according to their existing permissions. Both lists use the same records as the Chat settings page, so no data is duplicated. It is delivered as part of the Contact Center app available in Creatio Sales, Creatio Service, and Bank Customer Journey. The Contact Center app requires the Customer Communication Hub app. |
Contact Center | User and access management | Added the ability to control Agent Inbox panel visibility using the "Access to Agent Inbox sidebar" ( |
Contact Center | Apps and packages | Fixed an issue where the Contact Center app failed to install into Lending, Bank Customer Journey, Bank Sales, and the bundle that includes these products. Previously, installation failed with an unresolved package dependency, because the |
Case Management | Schema design and management | Fixed a compilation error in the Case Management app that occurred on Linux due to a duplicate |
Case Management | Schema design and management | Fixed an issue where the |
Customer communication hub | AI and automation | Renamed the technical user used for AI-generated actions from "ExternalChatAiUser" to "AiAgentUser." Previously, the name of the technical user did not clearly indicate its purpose. |
Customer communication hub | AI and automation | Added the Customer communication hub app to the Creatio Sales and Creatio Service products. The app is available in the "Service," "Contact Center Supervisor," "Case management" workplaces. Previously, the app was available on the Creatio Marketplace and had to be installed separately. The Customer communication hub app requires the Case Management or Contact Center app. |
Customer communication hub | AI and automation | Added the Customer communication hub section for connecting and monitoring all inbound web chat, Telegram, WhatsApp, Facebook Messenger, SMS chat channels and email channel and the AI that handles them. The section is available in the "Service," "Contact Center Supervisor," "Case management" workplaces. It is delivered as part of the Customer communication hub app. Previously, email, web chat, and social channels relied on different logic, which prevented connecting and tracking them together in one place. The section centralizes setup and monitoring for every inbound channel type. |
Customer communication hub | AI and automation | Added the Channel performance block to the Overview tab of the Customer communication hub section. It is delivered as part of the Customer communication hub app. The block lists all connected channels and displays an empty state when no channels are connected. Each channel includes the following columns: "Name," "Channel type," "Status," "AI response," "Volume," "Avg first response time," "AI effectiveness." Creatio refreshes the Channel performance block immediately after adding or removing the channel. |
Customer communication hub | AI and automation | Added the ability to open a channel settings page by clicking the channel name in the Channel performance block on the Overview tab of the Customer communication hub section. This change gives the "Supervisor" users direct access to channel settings without additional navigation. |
Customer communication hub | AI and automation | Added the Live dashboard block to the Overview tab of the Customer communication hub section. The block displays the current state of contact center operations with metrics that refresh automatically. Available metrics: Chats in progress by AI, Chats in progress by agents, Chats in queue, Cases in progress by agents, Cases in progress by AI, Cases in queue. Each metric is clickable and opens the filtered list of the chats or cases it counts. This change enables the "Supervisor" users to monitor contact center operations in real time from a single view. |
Customer communication hub | AI and automation | Added the Chats block to the Overview tab of the Customer communication hub section. The block displays chat throughput and AI-versus-agent performance for a selected period and channels. The Chats block requires the Contact Center app. Available widgets: Chat volume, Completed by AI, Handed off to agents, Completed by agents, Time to first respond AI vs agents, sec, Chats by status. Each widget is clickable and opens the filtered list of the chats it counts. This change gives the "Supervisor" users a unified view of chat activity without switching between sections. Chat volume displays the count of chats or email-originated cases created in the last 7 days. Completed by AI is displayed as a whole percentage. Time to first respond AI vs agents, sec displays the average time to the first response. |
Customer communication hub | AI and automation | Added the Cases block to the Overview tab of the Customer communication hub section. The block displays case throughput and AI-versus-agent performance for a selected period and channels. The Cases block requires the Case Management app. Available widgets: Case volume, Assisted by AI, Completed by AI, Completed by agents, AI responses: drafted for review vs autosent, Cases by status. Each widget is clickable and opens the filtered list of the cases it counts. This change gives the "Supervisor" users a unified view of case activity without switching between sections. |
Customer communication hub | AI and automation | Added a connection flow of the email channel in the Customer communication hub section. In the Step 1 of 2 – Setup channel mini page, users select an existing mailbox using the Choose mailbox field or connect a new mailbox using the Connect new mailbox button and select a case registration category using the Case registration category field. In the Step 2 of 2 – Enable AI assistance mini page the Use AI in the channel checkbox is selected with preconfigured AI capabilities and "Sofia, AI assistant" personality with a friendly tone of voice that users can customize. After channel connection, Creatio provides a copyable mailbox address for sending a test email. The email channel requires the Case Management app. |
Customer communication hub | AI and automation | Added the General settings tab to the new email channel settings page. The tab includes Mailbox, Case registration, and Message language expanded lists to manage email settings from a single page. Previously, working with the mailbox list was available using the List of mailboxes for case registration lookup only. The email channel requires the Case Management app. Mailbox expanded list includes the following fields: Case registration expanded list includes the required Case category field to select the category applied to all cases created from incoming emails to this mailbox. The field includes the "Incident" and "Service request" values from the Case categories lookup. Message language expanded list includes the following elements: |
Customer communication hub | AI and automation | Added the AI automation tab to the new email channel settings page of the Customer communication hub section. The tab includes AI automation settings for the email channel. Previously, all email responses were composed manually by agents. The email channel requires the Case Management app. This change enables the "Supervisor" users to scale email response handling with AI while keeping human oversight. The Mode field in the Reply mode expanded list on the AI automation tab of the email channel settings page includes the following values: When the Use AI in the channel checkbox is cleared, all emails are handled by agents and bypass AI. |
Customer communication hub | AI and automation | Added auto-reply decision logic for the email channel based on the quality score of each AI-generated response. When the Use AI in the channel checkbox is selected on the AI automation tab of the email channel settings page, administrators can define the quality threshold a response must reach to be sent automatically. After a response is generated, its quality score is compared against the selected threshold. The email channel requires the Case Management app. This change enables administrators to control how confidently AI sends automatic email replies and to balance automation against review based on response quality. Out of the box, Creatio provides the following auto-reply modes, each with a default quality threshold: The auto-reply modes are stored in the AI Email Auto-Reply Mode lookup. Out of the box, the lookup is unregistered. To register it, add a lookup based on the "AI Email Auto-Reply Mode" ( The calculated quality score is saved on the generated email in the "AI quality score" ( |
Customer communication hub | AI and automation | Added a quality score calculation mechanism for AI-generated responses in the email channel. The mechanism evaluates each generated response and produces a single The score is calculated using the following formula: |
Customer communication hub | AI and automation | Added prompt-injection protection to the the AI in the email channel to protect AI email responses against prompt-injection attacks. The prompt used for AI email flows — for example, drafting, classifying, and summarizing — now includes a dedicated untrusted-input security policy that instructs the model to treat email body, subject, signatures, quoted text, attachments, and links as untrusted and to never follow instructions embedded in it, switch persona, reveal system-prompt content or internal tools, expose data outside the current case scope, or deviate from its task. The emails sent from the "Emails" sidebar of the communication panel are not affected. |
Customer communication hub | AI and automation | Added handling for large email templates and long case chains in AI email response generation so the request stays within the LLM context window. Creatio pre-processes the template to extract only its meaningful content, discarding styles, images, and other visual content before the template is passed to the model, and trims long case chains to keep the request within the context budget while preserving conversation continuity. This change ensures AI email drafts are generated reliably regardless of how the template was authored or how long the case has been running. |
Customer communication hub | AI and automation | Added the "AI-generated" tag that marks email replies created by AI in the timeline on the Conversation tab of the case page. Previously, email replies prepared by AI were indistinguishable from manually written replies. The tag is shown next to the existing "Draft" tag when AI generated the reply and its body has not been changed, which covers AI-generated drafts awaiting review and replies sent automatically in auto-reply mode. The tag is removed the first time the email body is edited, so it always indicates content that remains exactly as AI produced it. Replies the agent writes from scratch or copies into a new editor are separate activities and are never tagged. It is delivered as part of the Web chat app available in Creatio Sales, Creatio Service, and Bank Customer Journey. The Web chat app requires the Customer Communication Hub and Case Management apps. |
Customer communication hub | AI and automation | Added the |
Customer communication hub | AI and automation | Added a monthly budget cap to Creatio.ai email response generation. AI email processing is now limited by the organization-level monthly AI budget, which protects against high-volume email attacks on a single mailbox. The email channel reuses the same budget-cap system setting already applied to chats, so once the monthly budget is reached, AI stops generating email responses. The cap is applied on the email AI processing path, alongside the existing per-contact rate limit and per-case turn limit checks. The limit is managed by the "AI monthly budget (actions)" ( |
Customer communication hub | AI and automation | Added configurable limits on AI email draft generation: a per-contact daily limit and a per-case limit. The per-contact daily limit is managed by the "AI email max drafts per contact per day" ( |
Web chat | Customer communication hub section | Added a web chat channel to the Customer communication hub section. The channel enables administrators to configure and connect a web chat for their website directly in Creatio, eliminating the need for separate configuration tools and reducing deployment time. It is delivered as part of the Web chat app available in Creatio Sales, Creatio Service, and Bank Customer Journey. The Web chat app requires the Customer Communication Hub app. When providing required details in the Customer communication hub section, Creatio adds the channel from a minimal set of settings and provides a working channel with the embed code for the website. A full channel configuration page provides advanced setup with a live preview of the channel. |
Web chat | Web chat channel settings page | Added the ability to configure the web chat position and spacing in the Layout expanded list on the Appearance tab of the web chat channel settings page in the Customer communication hub section. It is delivered as part of the Web chat app available in Creatio Sales, Creatio Service, and Bank Customer Journey. The Web chat app requires the Customer Communication Hub app. |
Web chat | Web chat channel settings page | Added the ability to configure multilanguage privacy notice text and a privacy policy URL for the web chat. Administrators can set them using the Privacy notice text and the Privacy policy URL fields in the Privacy notice expanded list on the Security tab of the web chat channel settings page in the Customer communication hub section. The privacy notice text is displayed at the bottom of the chat. Creatio uses the privacy policy URL as the clickable "Open privacy policy" link in the chat that opens in a new modal window. It is delivered as part of the Web chat app available in Creatio Sales, Creatio Service, and Bank Customer Journey. The Web chat app requires the Customer Communication Hub app. |
Web chat | AI and automation | Added real-time message testing to the live preview on the web chat channel settings page. Administrators can send messages from the preview after a channel is created, and the messages are delivered to Creatio through the standard web chat messaging flow. When the Use AI in the channel checkbox is selected and the AI Agent is added to the AI capabilities expanded list on the AI automation tab, it processes the incoming message and its reply appears in the preview. Replies from an agent are also shown after a handover. This change enables administrators to validate channel behavior, AI processing, and agent replies before publishing the channel, reducing the risk of configuration issues in production. |
Web chat | Web chat channel settings page | Added support for incoming file attachments in the web chat channel. Website visitors can send images and files, and agents receive them in the Agent Inbox panel where images can be opened in full size and other files can be downloaded. It is delivered as part of the Web chat app available in Creatio Sales, Creatio Service, and Bank Customer Journey. The Web chat app requires the Customer Communication Hub app. File type restrictions are managed by the "File extensions deny list" ( |
Web chat | Web chat channel settings page | Added the ability to send file attachments in the web chat channel. Agents can send images and files to website visitors during a web chat conversation. File type restrictions are managed by the "File extensions deny list" ( |
Web chat | Web chat channel settings page | Added support for emoji insertion in the web chat channel. It is delivered as part of the Web chat app available in Creatio Sales, Creatio Service, and Bank Customer Journey. The Web chat app requires the Customer Communication Hub app. |
Customer communication hub, | AI and automation | Added the AI automation tab to the web chat, Telegram, WhatsApp, Facebook Messenger, and SMS chat channel settings pages of the Customer communication hub section. The tab includes AI automation settings for chat channels. Previously, these settings were not available on the channel settings page, requiring the "Supervisor" users to switch between different areas to configure them. This change enables the "Supervisor" users to view and configure AI settings for each chat channel from a single page. |
Customer communication hub, | AI and automation | Added the Audience rollout expanded list to the AI automation tab of the web chat, Telegram, WhatsApp, Facebook Messenger, and SMS chat channel settings pages. The setting lets the "Supervisor" users control the share of incoming chats handled by AI. Previously, audience rollout could not be defined per channel, so AI handling could not be introduced gradually. Out of the box, the Audience rollout (%) field is set to "100." This change enables the "Supervisor" users to introduce AI gradually in a chat channel and monitor its impact before expanding it to the full audience. |
Customer communication hub, | AI and automation | Added the AI capabilities expanded list to the AI automation tab of the web chat, Telegram, WhatsApp, Facebook Messenger, SMS chat channel settings pages and email channel settings page of the Customer communication hub section. The list lets the "Supervisor" users manage the AI Agents available for a channel. Previously, managing AI Agents per channel was not available. The expanded list is available in the channel connection step-by-step flow and on the channel settings page. This change enables the "Supervisor" users to limit AI Agents to the intended scope. The AI capabilities expanded list includes the following elements: |
Customer communication hub, | AI and automation | Added the ability to connect Telegram, WhatsApp, Facebook Messenger, and SMS chat channels and enable AI in them directly from the Customer communication hub section. Administrators can do this using the Add channel button list in the Manage channels toggle panel and the Use AI in the channel checkbox on the mini page when connecting the channel. Previously, Telegram, WhatsApp, Facebook Messenger, and SMS chat channels could only be connected on the Chat settings page. Creatio collects the connection details and the queue for the added channel, then proceeds to the step for enabling an AI Agent. The channel name and link are generated automatically. After creation, Creatio adds the channel to the Channel performance list on the Overview tab. Clicking the channel opens a dedicated channel settings page with the General tab containing channel details such as name, queue, and language, and the AI automation tab with AI settings such as audience rollout, AI personality, AI capabilities, and handoff rule. Creatio refreshes the Manage channels toggle panel immediately after adding or removing the channel. It is delivered as part of the Contact Center app available in Creatio Sales, Creatio Service, and Bank Customer Journey. The Contact Center app requires the Customer Communication Hub app. |
Customer communication hub | AI and automation | Added a separate Enable AI assistance step to the connection flow of the SMS, WhatsApp, Telegram, web chat, and Facebook Messenger chat channels in the Customer communication hub section. Previously, AI configuration for chat channels required a separate step after connection and the "Supervisor" users received no channel-specific guidance on what to do next. In the Step 2 of 2 - Enable AI assistance mini page the Use AI in the channel checkbox is selected out of the box with preconfigured AI capabilities and "Sofia, AI assistant" personality with a friendly tone of voice that users can customize. After channel connection, Creatio provides a next action specific to the channel type. The final step behavior depends on the chat channel: |
Customer communication hub | AI and automation | Added a monthly AI budget cap for anonymous external chats, measured in AI Actions. Usage is tracked per app or channel and checked before each AI call in a chat. When the monthly budget is exhausted, AI is disabled for new conversations and they are handed off to an agent. The budget resets at the start of each month in UTC. The cap is managed by the "AI monthly budget (actions)" ( |
Customer communication hub | AI and automation | Added a configurable limit on the size of AI responses in chats, measured in output AI Actions. The limit is applied to every AI request and is enforced by the model, so generation stops once the configured number of output AI Actions is reached. This change keeps AI replies concise, controls AI Action cost, and prevents abuse through long-form generation loops, for example, repeated "explain in more detail" requests. The limit is managed by the "AI anonymous chat max output tokens" ( |
Customer communication hub | AI and automation | Added a configurable limit on the number of AI responses per anonymous chat conversation. The limit is tracked per conversation and checked before each AI call. When the limit is reached, AI skips the response and the conversation is handed off to an agent. The limit is managed by the "AI anonymous chat max turns" ( |
Customer communication hub | AI and automation | Enriched the auto-reply logic in the email channel to send a response automatically only when it fully resolves the case. Previously, a high-scoring response containing a clarification question could be sent automatically, even though it did not resolve the case. A The quality score is calculated based on the following formula: |
Customer communication hub | AI and automation | Changed the context passed to the LLM when generating AI email responses to include the full case communication. The context now also includes data from the feed on the Conversation tab of the case page, including system messages so the model can distinguish between internal and external information. Sensitive information from system messages, for example, passwords or confidential notes, is not used to generate the customer-facing response. The email channel requires the Case Management app. This change enables AI to produce more accurate and context-aware email responses while preventing internal or sensitive details from being exposed to customers. |
Customer communication hub | AI and automation | Changed the "Email" timeline object on the Conversation tab of the case page to pre-fill the Subject field for new emails. Previously, the Subject field was empty when an agent composed a new email. Creatio now pre-fills the field using the "Case response {CaseNumber} {CaseSubject}" template, for example, "Case response SR00000003 Cannot login to portal." Automatic naming does not affect replies, forwards, or edited drafts. |
Customer communication hub | AI and automation | Changed the chat context provided to the LLM to include the chat ID and the "Object" type schema name of the chat. These values are available to AI sub-agents and the business processes they invoke, enabling developers to identify the originating chat in a business process and use it to route conversations or update connected Creatio records, for example, a lead or opportunity linked to the contact. This change gives developers a reliable way to act on the specific chat from no-code automation. |
Customer communication hub | AI and automation | Changed the knowledge source in the Knowledge sources expanded list on the Knowledge sources tab of the Customer Support Agent so it draws only from a dedicated set of customer-support articles instead of the entire knowledge base. Previously, the knowledge source was built from all articles in the knowledge base. The knowledge source is now scoped to a dedicated dynamic "Customer support articles" folder in the Knowledge base section that automatically includes articles tagged "Customer support." To make the article available to the Customer Support Agent, add the "Customer support" tag to it. |
Customer communication hub | AI and automation | Fixed a runtime issue where the case Classic UI page closed after saving even though the "Close after saving" column in the Case statuses lookup was set to "No" for the case status. |
button menu in active chat sessions in the Agent Inbox panel showed a redundant "Clear selected record" item for every caller. This change shows the item only when a caller is selected.
button to the case page for cases where AI participated in generating a response. The button opens the Debug info modal window that shows how the AI response was formed. On the chat page in the Chats section, the button is hidden when AI was enabled for the channel but the chat was excluded due to the audience rollout split. The functionality is managed by the "Can debug skills" (
button. Clicking the number opens the native SMS client with the number prefilled in the To field.Industry cases
Category | Feature | Description |
|---|---|---|
Creatio Portal | UI and navigation | Added the ability to replace the default portal registration page with a "Client module" type schema using a new "Portal registration module name" ( |
Field sales | UI and navigation | Changed the visit logic in the Field sales app to use the "Visit" type instead of the hardcoded "Visit" category. Previously, rule filtering and title generation in the Activities section depended on the hardcoded "Visit" category, which prevented customers from using custom visit categories. |
Field sales | UI and navigation | Fixed a layout issue in the Field sales app where long names of visit actions pushed the toggle out of alignment on the Details tab of the activity page. Action names now wrap across multiple lines, keeping the toggle in a fixed position regardless of name length. |
Creatio Business Studio
No-code customization
Category | Feature | Description |
|---|---|---|
Localization | Translations | Fixed a runtime issue where custom translations created in the Translation section reverted to their default values. This happened after a page change, for example, when you added or removed a column or changed a summary. Previously, the |
Localization | Translations | Fixed a runtime issue where the Apply translations button in the Translation section failed completely when a translation record contained a data key with an empty schema segment. Previously, the translation cleanup stage accepted a malformed data key whose schema segment was empty and then tried to retrieve a schema by an empty name, which threw an error and aborted the entire "Apply translations" business process run before any unused translation was removed. Such malformed records are not produced by the standard translation flow and typically originate from external data inserts or migrations. The cleanup now treats a data key with an empty schema or column segment as invalid and removes it automatically, so the run completes. |
Apps and packages | App management | Changed the application installation flow for single-app, bundle, and Marketplace installation scenarios to prevent app version downgrades. Previously, when an installation included an app version lower than the version already present in the environment, Creatio displayed a warning but continued anyway, overwriting the newer version with the older version. This change detects the downgrade condition before installation proceeds, skips the affected app, and displays an informational message in the Application installation window identifying which app was excluded, while apps without a downgrade condition install as expected, preventing unintended version rollbacks during bundle and Marketplace installations. |
Apps and packages | App management | Fixed a runtime issue where the install script for a package could fail to resolve during app installation through Application Hub. Previously, the path to the required library was not reliably located, so an installation could complete with errors even when Application Hub reported success. The path resolution is now improved so that the required library is reliably resolved and the install script is found during package installation. |
Apps and packages | Package management | Fixed an issue where installing a valid *.gz package on .NET 8 builds failed with the "Unable to open '{PackageName}.gz'. The file is invalid or corrupted. Check the file integrity or download and reupload it." error, even though the same package installed successfully into .NET Framework builds. Previously, the |
Apps and packages | Page templates | Added the Filters menu and Filters components to the "List page" template available in the Select template modal window of the Application Designer. The components control the visibility of the filters on list pages. Previously, both components were under beta testing. Out of the box, both components are included on the following pages: The Filters component is placed in the same container as the Folders component. |
UI Design | Freedom UI components | Added a new Icon component to the Freedom UI Designer. The component lets no-code creators place icons on Freedom UI pages and configure component parameters directly in the setup area. Available parameter values: |
UI Design | Freedom UI components | Added keyboard shortcut support for the Button component whose Action parameter in the Freedom UI Designer is set to "Save data." Previously, records could only be saved by clicking this button. After saving, Creatio preserves the page scroll position. To stop using this functionality, register and enable the |
UI Design | Freedom UI components | Added the Header template parameter to the setup area of the Filters component in the Freedom UI Designer. Out of the box, the value is set to "Show all records that match {menuOperator} of these conditions," where {menuOperator} is rendered as the condition operator button that switches between matching all or any of the conditions. If {menuOperator} is removed, the operator is appended at the end of the header by default, so the operator control remains available. Previously, the header text was fixed and could not be adjusted to fit the placement of the component. The parameter supports localizable strings. The parameter value is managed by the new |
UI Design | Freedom UI components | Added a new Maximum number of records parameter to the setup area of the Hierarchical list component in the Freedom UI Designer. Previously, the record limit was managed only by the "Maximum number of records in hierarchical list" ( |
UI Design | Freedom UI components | Changed the data loading logic of the Hierarchical list component to allow the "Maximum number of records in hierarchical list" ( |
UI Design | Freedom UI components | Fixed a runtime issue where deleting a single chat channel from the Message composer component in the Freedom UI Designer removed all chat channels at runtime instead of only the deleted channel. |
UI Design | Freedom UI components | Fixed an issue for RTL view in the Freedom UI Designer where the buttons that define filtering options of the Timeline component overlapped each other when the |
UI Design | Freedom UI components | Added the Filters menu and Filters components to the Freedom UI Designer. Previously, both components were under beta testing under the names Advanced filters menu and Advanced filters. The components let users build complex filter conditions, filtering records by object columns and related object columns through forward and backward references. End users can apply filters to records that match all conditions (AND) or any condition (OR). The list of operators depends on the column type to which the filter is applied. |
UI Design | Fields and inputs | Added a new "Switch" type field and input to the Freedom UI Designer element library. It renders as a toggle in the UI. The setup area includes the same parameters as the "Checkbox" type field and input. |
Business processes | Elements | Fixed an issue where the Send chat message business process element did not send WhatsApp messages. |
Integrations and APIs | OAuth authorization | Added the Consent mode field to the Consent mode expanded list on the Authorization code tab of the integration page in the OAuth integrated applications section. The field controls how user consent is handled during the authorization code grant. The functionality is managed by the "Can manage OAuth settings" ( |
Integrations and APIs | OAuth authorization | Added support for registering OAuth redirect URLs that use mobile custom URI schemes, enabling OAuth authorization code grant to return users to the mobile app. Previously, OAuth redirect URL validation required the |
Integrations and APIs | OAuth authorization | Added an API that registers a new OAuth integration in a single call. Previously, registering an integration required an administrator to manually create an OAuth client application and a technical user and wire them together. A caller can now register an integration by providing an integration name. Creatio atomically creates an OAuth client application and a linked technical user, and returns the client ID, client secret, and technical user ID. The client secret is returned only once at creation time. Technical users who have permission to the "Access to "Register integration" action" ( |
Integrations and APIs | OAuth authorization | Added the ability to issue a signed JWT Assertion token for the currently authenticated user as part of the OAuth authorization flow, which can be sent to external applications. To use this functionality, enable the |
Integrations and APIs | OAuth authorization | Changed the default state of the |
Integrations and APIs | OAuth authorization | Changed the Client secret parameter on the OAuth integrated application pages to use the secure string component. Previously, the parameter handled its value as a plain text input, which exposed the credential in the UI. The parameter now masks the entered value while still letting users reveal it by clicking the |
Integrations and APIs | OAuth authorization | Changed the OAuth application model so that a single OAuth application can support multiple OAuth 2.0 grant types at the same time. Previously, an OAuth application was tied to a single grant type, so supporting more than one grant required registering and maintaining separate applications with different client IDs for what was conceptually one application. An OAuth application now carries a configurable set of allowed grant types, and the same client ID can use client credentials and authorization code with PKCE grants together. The token endpoint authorizes each request against the allowed grant types and rejects a grant that is not enabled for the client with the |
Integrations and APIs | OData | Fixed an issue where an OData request for a non-existent schema returned the wrong HTTP status code. Previously, when a request used a valid OAuth access token to access an OData schema that did not exist, the OData middleware returned "401 Unauthorized" instead of "404 Not Found" due to incorrect error code handling in the authorization pipeline. |
Integrations and APIs | Calendars | Added the ability to disable synchronization of Microsoft Exchange tasks. This change ensures that affected mailboxes synchronize email and calendar without tasks, tailoring mailbox synchronization to customer requirements without additional coding. To stop using this functionality, register and enable the |
Integrations and APIs | Calendars | Changed the default mailbox behavior so that Microsoft Graph API mailboxes no longer support task synchronization. Previously, Creatio ran Microsoft 365 tasks synchronization regardless of mailbox type. Graph API mailboxes now synchronize only email and calendars, while Microsoft Exchange/EWS mailboxes keep task synchronization. This change makes mailbox synchronization predictable for administrators. To stop using this functionality, register and enable the |
Integrations and APIs | Calendars | Changed the meeting cancellation behavior for meetings organized by an external user when several invited users have calendar synchronization. Previously, when the |
Integrations and APIs | Calendars | Fixed an issue where calendar events from Microsoft Exchange with a missing organizer were skipped during synchronization, even when they clearly belonged to the synchronized mailbox. Such events are now imported using the synchronized mailbox as the organizer, while events with an ambiguous owner are still skipped. This change enables users to keep their calendar complete without manually recreating meetings that lack an organizer. To stop using this functionality, register and enable the |
Integrations and APIs | Calendars | Fixed an issue where reconnecting a Microsoft 365 mailbox with different letter casing created duplicate records in the |
Integrations and APIs | File processing | Fixed an issue where running the file migration through WorkspaceConsole utility caused blocking locks at the database level, which could stall or hang the migration. The migration logic was updated to avoid the blocking locks. |
Integrations and APIs | File storages | Changed the default state of the |
Integrations and APIs | Telephony | Changed the concurrency control for parallel call updates in the telephony integration. Previously, near-simultaneous |
Integrations and APIs | Telephony | Changed the recovery mechanism for transport failures in the Cisco Finesse CTI provider. Previously, a short websocket or XMPP interruption could trigger a full provider re-initialization, repeatedly calling login, settings, and connection steps and producing a reconnect storm of duplicate requests. Ordinary transport failures now recover through a lightweight, controlled reconnect that reuses loaded credentials and cached settings, with guards against parallel reconnect attempts. This change keeps the telephony connection stable during network instability. |
Integrations and APIs | Telephony | Fixed an issue where the Cisco Finesse CTI integration created duplicate calls. Previously, when two Finesse events for the same dialog arrived almost simultaneously, both were processed against an empty call collection and two records were saved for a single dialog. This change de-duplicates calls per dialog, so later events reuse the existing call, giving contact center teams accurate call records and reliable telephony reporting. |
Integrations and APIs | Telephony | Fixed an issue where reassigning a phone extension to another user resulted in incorrect call ownership and missing WebSocket call updates. Previously, the cached messaging connection was invalidated only when the user identifier changed, so a reassigned extension kept routing calls and updates to the previous owner until the service restarted. This change also invalidates the connection when the user's contact or session changes, so calls route to the correct agent without requiring a service restart. |
Integrations and APIs | Telephony | Fixed a runtime issue where the Mute, Hold, and Transfer buttons became unavailable on an active call in the "Calls" sidebar of the communication panel and the Agent Inbox panel of the Contact Center app. Previously, when overlapping ring-all calls arrived and were answered by other agents, a line state change event without a call identifier was applied to the connected call and reset its available actions. This change ignores such events when they carry no call identifier, enabling agents to keep full call control during high call volume. |
Integrations and APIs | Email Listener | Changed the validation logic in the Email Listener |
Integrations and APIs | Chats | Added a new "Closure reason" ( Available column values: "Completed by agent," "Completed by timeout," "Completed by end user," "Transferred." End-user initiated chat completion is detected in the Ada chat channel. |
Integrations and APIs | Chats | Added the ability for a website visitor to end a chat with a human agent and start a new conversation in the web chat channel. Clicking the End chat button now opens a confirmation window, and confirming completes the current conversation, sets its closure reason to "Completed by end user," and opens a new, empty conversation in the chat. The completed conversation no longer accepts new messages, and if the completion request fails, the current conversation stays active. This change enables website visitors to close a finished conversation with an agent and start a fresh chat when needed, keeping separate interactions clearly separated. |
Integrations and APIs | Chats | Fixed the cleanup process when an SMS chat channel is deleted. Previously, related records in the |
Integrations and APIs | Chats | Fixed an error message text displayed when adding an SMS or WhatsApp channel on the Chat settings page without a configured Identity Service. |
Integrations and APIs | Emails | Fixed an issue where saving the same email activity several times created duplicate participant records. Previously, repeating the save of the same email activity could insert duplicate records into the |
Integrations and APIs | Emails | Fixed an issue where the modified-record business process signal did not fire after editing an unsent email, most often for changes to the Subject, To, or Recipient fields in the email mini page opened from the "Emails" sidebar of the communication panel. Previously, the email auto-relation logic saved the activity a second time during the same save, which reset the record's change tracking, so the signal did not detect the user's edit. This change updates the nested save to persist the relation columns without resetting change tracking, so the modified-record signal reliably sees the original edit and no-code creators can start business processes when an email activity is modified. To use this functionality, register and enable the |
Integrations and APIs | Emails | Fixed a runtime issue with the loading state of the recipient search in the To, CC, and BCC fields in the email mini page opened from the "Emails" sidebar of the communication panel. Previously, these fields displayed "No data" during the search itself, which incorrectly suggested no matches existed. This change shows a loading state while searching and displays "No data" only when the search returns no matches. |
Integrations and APIs | Emails | Fixed a runtime issue where the CC and BCC fields did not appear in the email mini page opened from the "Emails" sidebar of the communication panel in the Safari browser. Previously, clicking the CC or BCC button in Safari did not reveal the fields. This change opens the copy and blind-copy fields correctly in Safari. |
Integrations and APIs | Emails | Fixed a runtime issue where email participants were not removed when a recipient was deleted from the To, CC, or BCC field in the email mini page opened from the "Emails" sidebar of the communication panel. The issue occurred before email sending. Previously, a participant added to one of these fields remained in the participant list even after the recipient was removed from the draft. This change updates the participant list to match the current recipients when the draft is saved. |
Integrations and APIs | Emails | Fixed a runtime issue where signature images were duplicated for outgoing emails on the email page opened from the "Emails" sidebar of the communication panel. Previously, an image from an email signature was added both as an inline attachment and as a separate general attachment. This change adds the image only as an inline attachment. |
Integrations and APIs | Emails | Fixed a runtime issue where synchronized email attachments could not be downloaded due to a data integrity issue in the "Emails" sidebar of the communication panel. Previously, some attachments from synchronized emails were stored empty even though their size was recorded in the database. |
Integrations and APIs | Emails | Fixed a runtime issue where the mailbox-related lookups returned no result due to a stale local repository cache. Previously, the mailbox setting repository could rely on an empty or outdated local cache snapshot and return no data even when the mailbox existed in the database. This change re-checks a lookup miss against the database before returning no result, making mailbox-related lookups reliable under repeated or concurrent access. The previous behavior is left unchanged when mailbox setting caching is disabled. |
.
button. This change reduces the risk of accidental exposure of OAuth client credentials in the UI.Advanced customization
Category | Feature | Description |
|---|---|---|
UI Design | Freedom UI components | Added the ability to configure the current-user photo and attachment loading behavior of the feed. This is available using the new |
UI Design | Freedom UI components | Added the ability to make the email subject read-only in the message composer for the "Email" channel. This is available using the new |
UI Design | Widgets | Added the ability to hide the widget title at runtime and design-time using the new |
Schema design and management | Source Code Designer | Changed the "Provides a class for working with omnichannel chats" ( |
Schema design and management | Configuration section | Changed the configuration compilation process to reduce build time and keep compilation duration predictable as the configuration grows. Previously, compilation processed all packages and ran preparation steps such as dependency restore and OData compilation even when they were not required, which increased build time for large configurations. |
Schema design and management | Configuration section | Fixed an issue where schema resources were incorrectly marked as deleted when the resource name in the "app-descriptor.json" file and the resource directory name differed only by letter case. Previously, the resource search was case-sensitive, so a name such as |
Schema design and management | Configuration section | Fixed an issue where source-regenerating operations in the WorkspaceConsole utility failed to generate campaign schema sources. Previously, WorkspaceConsole did not load the workspace assembly before deserializing campaign flows, so campaign schema source generation failed. Every WorkspaceConsole operation that regenerates campaign schema sources such as |
Schema design and management | Creatio theming | Removed several internal CSS variables as part of the design token-based theming implementation. These variables were not part of the public API and were not subject to backward compatibility guarantees. We recommend reviewing any custom CSS that references the removed variables to ensure compatibility after upgrading to version 10X Unlimited. This change has no impact on customizations that rely exclusively on the public API. Palette variables removed for Full palettes removed for Typography variables removed for Full typography styles removed for |
Feature management | Feature toggling | Changed the |
Framework updates | Angular version update | Changed the Angular framework version used by the Creatio platform to version 21. This change aligns the platform with Angular 21 standards and ensures continued compatibility with the latest framework capabilities. |
Administration
Category | Feature | Description |
|---|---|---|
System settings and tools | Lookups | Changed the list of regions in the States/provinces lookup and the list of corresponding cities in the Cities lookup. Previously, both lookups did not include German regions and cities and included an extensive list of Russian regions and cities. Both lookups now include the major German regions and cities, and Russian records are reduced to Moscow Oblast and Leningrad Oblast for regions and Moscow and Saint Petersburg for cities. This change gives users relevant reference data out of the box and reduces manual lookup cleanup. |
System settings and tools | Lookups | Fixed a runtime issue in the States/provinces lookup where several US states had an incorrect time zone assigned. Previously, for the Alabama, Texas, Louisiana, Iowa, Minnesota, Missouri, and Mississippi states, the "Time zone" column included the "Central America (GMT-06:00)" value instead of "Central Time (US & Canada) (GMT-06:00)," which showed incorrect local times for contacts in those states. |
Logging and monitoring | Audit log | Enabled audit logging for new Creatio installations. Previously, audit logging was inactive after a new install because the Default value checkbox of all system settings in the "Audit log" folder was cleared, which required manual configuration before audit records were captured. The Default value checkbox is now selected for new installations. Existing installations are unchanged, so system settings that were previously stored with an explicit value retain that value after upgrading to version 10X Unlimited. |
Logging and monitoring | Configuration activity log | Added logging for the "Clear configuration activity log" operation to the configuration activity log. Each cleanup operation now creates a log record with a summary of deleted records grouped by "Configuration activity log" ( |
Logging and monitoring | Configuration activity log | Changed the file deletion mechanism of the configuration activity log cleaner to use a storage abstraction layer instead of directly accessing the |
User and access management | Licensing | Fixed a runtime issue in .NET 8 and .NET Core builds where the License manager page opened from the Creatio login page became inaccessible for users without an active license. Previously, such users could not open the License manager page at all, which prevented them from managing licenses even when administrative access was intended. This change restores access to the License manager page in .NET 8 and .NET Core environments by loading the page correctly regardless of the current user's license status. This lets administrators manage licenses without an active license. |
User and access management | Licensing | Fixed an issue where integrations stopped working for the technical user when the Creatio licenses had expired or the wrong customer ID was set. Previously, configuration setup commands ran under the technical user during the licensing process, but the license check failed and returned the "License is missing or expired" error, which blocked the commands from completing. The technical user is now exempt from this license check, so integration and configuration commands continue to run. |
User and access management | Technical users | Changed the business logic that determines whether the current user is a technical user. Previously, the logic ran a database query against the |
User and access management | 2FA | Fixed a runtime issue where password recovery for new users who had not yet configured TOTP (Time-based One-Time Password) required setting up an authenticator app during the recovery flow when 2FA was enabled. Previously, the new password was not saved and the user was redirected to the login page. Password recovery now completes without any 2FA verification or setup step, the new password is saved, and the user is redirected to the login page. The standard 2FA flow starts at the next regular login. |
User and access management | Single Sign-On | Changed the SSO logout flow to no longer get blocked on a failed SAML single logout request. Previously, if the SAML single logout request ( |
User and access management | Single Sign-On | Fixed an issue where the Switch button on the consent page did not work for users logged in through SSO when passing the OAuth authorization code grant. For example, when providing consent for the Creatio.ai add-in for Outlook. Previously, for an SSO user, after logging out the login window reopened with the previous user prefilled, and clicking the button only reloaded the same prefilled state instead of displaying the login form. This happened because the Switch button redirected to the authorization endpoint, where pass-through auto-login silently re-authenticated the user who had just logged out. |
End user experience
Category | Feature | Description |
|---|---|---|
UI and navigation | Creatio theming | Added the ability to change the Creatio theme in the user profile. The default theme is managed by the "Default theme" ( |
UI and navigation | Pages | Added a new Change row height option to the list settings menu. Available row height values: "Small," "Medium," "Large," and "Extra large." Out of the box, the value is set to "Small." When the row height is set to "Medium" or above, text column values wrap to multiple lines within the cell. Non-text columns are always displayed in a single line regardless of the selected height. The selected row height is saved in the user's profile and persists across sessions. Inline editing is supported for all row height values. |
UI and navigation | Pages | Added support for date and time macros in the filters, including parameterized macros with editable inputs. Previously, filters did not support macro-based filtering and this functionality was available in Classic UI only. When a user adds the "Date/Time," "Date," or "Time" type column and selects an operator, users can switch between a constant value and a macro. When a user selects a macro that accepts a value, an input is displayed for that value, and selecting a different macro updates the input accordingly. When the filter is applied, the selected macro is resolved into the query using the existing macro resolving logic. Date/time macros are not available for the "between" operator. |
UI and navigation | Pages | Added the ability to filter "Date/Time," "Date," and "Time" type columns by date, time, or both in the filters. Previously, users had to enter both date and time for a "Date/Time" type column. Filtering by date only or by exact time was not supported, and this functionality was available in Classic UI only. When a user adds a column and selects an operator, Creatio lets the user choose the needed option. This change enables users to build date-only, time-only, and date-and-time filters in Freedom UI. |
UI and navigation | Pages | Added support for filtering by related object attributes through backward references in the filters. Previously, the component allowed filtering by columns of the current object and its directly referenced objects only, so users could not build conditions based on objects that reference the current object. The Add new filter button list now includes the "Explore related data" option that opens the Select field modal window. Each selection through a backward reference creates a separate filter group in the Filters toggle panel, with the criteria combined by the all conditions (AND) or any condition (OR) and a header generated automatically. |
UI and navigation | Pages | Added support for system variables in the Filters component for "Contact" ( |
UI and navigation | Pages | Changed the keyboard shortcut for adding new records inline in the list whose Inline editing parameter is selected in the Freedom UI Designer from Shift+Enter to Ctrl+Enter. Previously, it conflicted with adding a new line in multiline text cells. |
UI and navigation | Pages | Changed the runtime behavior of the "Lookup" type columns in the list whose Inline editing parameter is selected in the Freedom UI Designer. Previously, editing a cell required an additional click to open the dropdown menu. It now opens automatically. |
UI and navigation | Pages | Changed the feed post header to show the specific linked record. Previously, a feed post named only the object in which it was posted, without the specific record title. The post header now shows the primary display value of the linked record, for example, "posted in account Acme." This change enables users to identify the related record directly from the feed without opening it. |
UI and navigation | Pages | Changed the Filters component to keep the state of the Filters toggle panel per section in the user profile. Previously, the expanded or collapsed state of the panel was not saved, so the panel did not retain the user's preferred view after a re-login or page reopen. |
UI and navigation | Pages | Changed the width of the recipient list in the To, CC, and BCC fields of the message composer to show full email addresses. Previously, the list was too narrow to display complete addresses. This change enables users to see full email addresses when selecting recipients. |
UI and navigation | Pages | Changed time selection in the "Date/Time" type fields to use a scrollable time list. Previously, these fields did not offer a list-based time selection. The time interval is managed by the |
UI and navigation | Pages | Fixed an issue in the button where the button menu sometimes opened downward regardless of the button position on the screen. Previously, the menu could open outside the visible area when the button was positioned near the bottom of the page. The menu now detects available space and opens in the appropriate direction. |
UI and navigation | Pages | Fixed a runtime issue in the list where titles and values of the "Number" type columns were aligned to the left in RTL mode. They are now always aligned to the right regardless of the active mode's text direction. |
UI and navigation | Pages | Fixed a runtime issue in the attachments where uploaded files disappeared from the attachment list on unsaved records when both the Enable live data update checkbox in the Behavior property block of Object Designer and Use record permissions checkbox on the Permissions tab of the object page in the Object permissions section were selected. |
UI and navigation | Pages | Fixed a runtime issue where the To field in the message composer for the "Email" channel showed incomplete recipient suggestions. Previously, a pagination condition in the email search compared the returned record count against the requested row count instead of the actual request size, so results could be cut short after access-rights filtering and valid recipients were missing. |
UI and navigation | Pages | Fixed a runtime issue where typing a contact name in the To field of the message composer for the "Email" channel returned no results, even though the same contact was available through the modal window. |
UI and navigation | Pages | Fixed a runtime issue where the message body rendered collapsed in the message composer for the "Feed" and "Email" channels. Previously, the body field could appear as a narrow vertical strip, making messages hard to compose. This change renders the body field at its normal size. |
UI and navigation | Pages | Fixed a runtime issue where the message composer had no internal scroll, so inserting a template could push the Send button out of the visible area. This change adds an internal scroll to keep the Send button visible. |
UI and navigation | Pages | Fixed a runtime issue where unsent draft content was not restored in the message composer for the "Email" channel. Previously, cached draft content was wiped when the record was reopened and ignored when the channel was switched, so typed text and the signature were lost. This change re-applies the cached draft, consistent with the "Feed" channel. |
UI and navigation | Pages | Fixed a runtime issue where the timeline stopped loading additional records when the browser zoom was set to certain fractional values, for example, 67%, because the last-row observer was not detected as visible. |
UI and navigation | Pages | Fixed a runtime issue where timeline records did not display values from the configured |
UI and navigation | Pages | Fixed a runtime issue in the "Number" type fields where letters and other non-numeric characters could be entered. |
UI and navigation | Pages | Fixed a runtime issue where a full-size record page opened from a "Dropdown" type field whose Lookup view parameter in the Freedom UI Designer was set to "Dropdown list" was displayed underneath the still-visible mini page. Previously, when a user typed a new value in the "Dropdown" type field and clicked the Add new button, and the new record was configured to open on a full page rather than a mini page, the full page opened under the mini page. The mini page is now hidden while the full page is open and restored when the user goes back. |
UI and navigation | Pages | Fixed a runtime issue in the iFrame widget where YouTube video previews were displayed in low quality before playback started. |
UI and navigation | Pages | Fixed a runtime issue where chat messages sent from business processes showed no delivery status in the timeline or the Agent Inbox panel. The delivery status is now displayed for messages sent from business processes in the same way as for messages sent manually. |
UI and navigation | Pages | Added the Filters toggle panel to all list pages built on the out-of-the-box "List page" template and to list pages in apps built on the "Records & business processes" template. The Filters menu component controls the visibility of the panel. The panel includes filters implemented using the Filters component. Previously, both components were under beta testing. Out of the box, the panel width is "400px." Clicking the Add new filter button in the panel displays the filter columns of the object selected in the Object parameter of the List component in the Freedom UI Designer. |
UI and navigation | Pages | Changed the visibility behavior of the |
Communications | Message templates | Fixed a runtime issue where emails built from a template in the Message templates section could be sent with unresolved macros and no warning in Creatio, while process-sent emails already removed them out of the box. Unresolved macros are now marked in the UI with a notification. This change enables users to avoid sending emails that contain leftover placeholder text. |
icon at runtime for the "Text," "Number," "Date/Time," "Rich text," "Phone," "Email," "Web link," "Dropdown," "Autonumber," "Encrypted string" type fields. Previously, the icon was displayed only when pointing the mouse, making it invisible to keyboard users navigating via focus. The icon is now also displayed when the field receives focus.Creatio Mobile
Category | Feature | Description |
|---|---|---|
Mobile UI Design | Business rules | Fixed a runtime issue where the "Set values" business rule overwrote field values when opening an existing record page in Creatio Mobile. Previously, this caused the Save and Cancel buttons to appear even though the user had not made any changes. "Set values" business rules are now skipped when an existing record is opened. |
Mobile UI Design | Business rules | Fixed a runtime issue in Creatio Mobile where business rules did not react to changes made through the dynamic cases in the Progress bar component. |
Mobile UI and navigation | Surveys | Removed success notifications from the survey page in Creatio Mobile. Previously, the notifications overlapped the navigation buttons, occasionally blocking interaction. |
Beta testing of new features
Category | Feature | Description |
|---|---|---|
UI Design | Widgets | Added a new pivot table widget to the Freedom UI Designer and the Dashboard Designer. The widget lets no-code creators build and interact with pivot table analytics entirely in Freedom UI, eliminating the need to switch to Classic UI for pivot table configuration. The widget renders at runtime using the existing pivot table component. To use this functionality, register and enable the Available parameter values: The Column, Rows, and Values parameters support |
Integrations and APIs | OAuth authorization | Added the ability to create a non-installed OAuth integration in the OAuth integrated applications section. Administrators and developers can prepare and configure an integration without registering it in the Identity Service immediately. This change enables them to deliver the integration as a set of data bindings inside the Creatio package, so the user only needs to install it instead of configuring it manually. Previously, every new OAuth integration was registered in the Identity Service the moment it was created, which required the Identity Service to be available and configured. An integration in a "Not installed" status has no generated credentials, creates no default relations, makes no Identity Service calls, and keeps the Integration is active checkbox in the Application details profile of the integration page disabled until installation. Once ready, the integration can be installed in a single action that validates the configuration, registers the client in the Identity Service, generates the credentials, and activates the integration. If validation fails or the Identity Service is unavailable, the operation rolls back and the integration remains in the "Not installed" status. To use this functionality, enable the |
Integrations and APIs | Identity Service | Added support for configuring multiple identity provider connections that Creatio uses when authenticating outgoing calls to external applications, and assigning them to specific Creatio services and microservices. This is available using a new Identity providers management section in the Import and integration block in the System Designer. To stop using this functionality, disable the |
Logging and monitoring | Audit log | Added access control and audit logging for the Identity providers management section in Import and integration block in the System Designer. The functionality is managed by the "Access to "Identity providers management" workspace" ( |
and 
actions.