Skip to main content

8.3.3 Twin changelog

Release date:

This document details the technical changes and enhancements introduced in Creatio 8.3.3 Twin. It is intended for developers, system administrators, and DevOps engineers responsible for maintaining and extending Creatio customizations.

The update guide for the on-site applications is available in a separate article.

Creatio platform

Category

Feature

Status

Description

AI and automation

AI Agents

Changed

Added a new Landing Page Generation Agent that generates responsive landing pages automatically based on a text description. Users can specify the page goal, target audience, and color palette preferences directly in the Creatio.ai chat panel. Based on this input, the agent selects an appropriate landing page template, generates page content, applies the configured color palette, and produces a ready-to-use landing page. The agent is available in the Lead Generation app and supports "Generic," "Comparison," "Pricing," "Click-through," "Event," "Product," "Lead capture," "Webinar," "Trust and proof," "Informational," "Use case - solution" landing page types. Image selection and generation are not supported. This change reduces manual layout and copywriting efforts, improves brand consistency across campaigns, and accelerates the landing page creation process.

More details

Added the following AI workflow Skills:

  • "Landing page designer" that defines color palettes for landing pages.
  • "Landing copywriter" that generates text content for landing pages.

AI and automation

AI Skills

Changed

Renamed the Usage mode field to Where to use, the "Chat" option to "Prompt agents," and the "API" option to "Workflows" on the AI Skill page to better reflect actual usage scenarios and reduce configuration ambiguity. The tooltip text for the Where to use field was also updated. This change improves clarity and helps users better understand where each skill can be used.

AI and automation

AI Skills

Changed

Changed the out-of-the-box value of the Status field for the "Summarize activity" AI Skill from "Active" to "Deactivated." Previously, users manually triggered this skill to generate a meeting summary as a separate action. Now, the skill is no longer available and Creatio generates an AI meeting summary automatically after synchronizing the meeting transcript and displays it in the Meeting summary tab on the meeting page. The functionality relies on Creatio.ai and uses AI Actions. For example, generating a summary for a one-hour meeting consumes approximately three AI Actions. The update affects only the out-of-the-box "Summarize activity" AI Skill. Customized AI Skills remain unchanged after upgrading to version 8.3.3. The functionality is managed by the Create AI meeting summaries from MS Teams transcriptions checkbox in the Calendar settings mini page. Out of the box, the checkbox is cleared. This change simplifies user workflows and ensures meeting summaries are generated automatically without manual actions.

AI and automation

AI Skills

Changed

Configured Creatio.ai to use the "Create action" system action for contact creation instead of "Create contact record from email" AI Action. The "Create contact record from email" AI Action was removed from the Action list expanded list on the General information tab for the "Identify contacts" AI Skill. The "Create contact record from email" business process is still available in the Process library section. This change unifies contact creation logic, aligns it with the platform action model, reduces duplication of business logic, and simplifies maintenance of AI-driven contact identification scenarios.

AI and automation

AI Skills

Fixed

Fixed an issue where the "Identify contacts" AI Skill was not selected correctly due to insufficient keywords in its Description field. Previously, the description did not contain the required keywords for proper prompt matching, which caused Creatio.ai to skip the skill when identifying email recipients. This change ensures accurate AI Skill selection when processing email-related prompts.

AI and automation

AI Skills

Fixed

Fixed an issue where system actions that have related AI Actions were not included in the request context when a user directly addressed an AI Agent by tagging it. Previously, responses could be generated without required system-level instructions and configured actions could be skipped. The invocation logic was corrected to ensure that system actions are added both when the agent is selected from the list and when it is directly mentioned in a message. This change ensures consistent execution of configured AI Actions and predictable agent behavior across different invocation scenarios.

AI and automation

AI Agents,
AI Skills

Changed

Changed the default value of the "Character limit for creatio.ai user query" (CreatioAIMaxUserQueryLength code) system setting from "50,000" to "100,000." This setting defines the maximum number of characters that can be included in a single request sent to Creatio.ai for LLM processing. This change enables reliable handling of long text inputs, such as meeting transcripts, and reduces the risk of request failures or data truncation when processing large LLM requests.

AI and automation

AI Agents,
AI Skills

Changed

Added support for using the LLM-mini model category for chat title generation in the Creatio.ai chat panel. Previously, the model code was statically configured. The platform now retrieves model codes dynamically from the LLM Model Categories lookup, supporting both default and LLM-mini model categories. Model codes are cached at the application level with automatic invalidation when lookup values change, ensuring up-to-date configuration. This change replaces static configuration with a flexible lookup-based approach, enables the use of lightweight models for specific tasks such as title generation, and improves the configurability and efficiency of model selection.

AI and automation

AI Agents,
AI Skills

Changed

Changed the behavior of AI Agents and Skills to use the model explicitly specified in the Model field on agent and skill pages instead of relying on the default LLM. The configuration now assigns the GPT-4.1 model to the Productivity Agent and the "Identify contacts," "Reply to email," "Check open cases," and "Summarize email" AI Skills. The update is applied automatically to existing data bindings after upgrading to version 8.3.3. This change ensures stable and predictable responses regardless of which model is set as the default LLM and improves consistency of AI-driven functionality across environments.

AI and automation

AI Agents,
AI Skills

Changed

Changed the behavior of the Email Generation Agent to use a template-based generation approach for bulk emails. The agent now selects from predefined email templates covering common marketing scenarios such as promotions, events, confirmations, and re-engagement, and applies skills for text and color generation in a fixed sequence. Additionally, enhanced the "Email designer" AI Skill to support configuration of the email color palette during generation. This change improves the stability and predictability of bulk email generation, ensures consistent branding, reduces the need for manual corrections, and enables marketing users to create high-quality, responsive bulk emails faster and with greater reliability.

AI and automation

Creatio.ai chat panel

Changed

Added support for a strict orchestrated session mode for AI Agent interactions in the Creatio.ai chat panel. The mode binds the chat session to a single explicitly selected agent and disables automatic routing and agent switching while the session is active. All user messages are processed strictly within the context of the active agent without fallback or semantic redirection. The session persists after page reload and ends only after explicit user action. The capability applies to prompt AI Agents. Workflow AI Agents are supported only for safe termination on exit. The functionality is managed by the GenAIFeatures.EnableGuidedSession additional feature. Out of the box, the feature is registered and enabled. This change ensures deterministic agent interaction behavior, eliminates implicit routing, and increases transparency and control over agent-driven conversations.

More details

When the feature is enabled, Creatio:

  • Binds the chat interaction to a single explicitly selected AI Agent.
  • Disables automatic routing and agent switching.
  • Processes all user messages strictly within the active agent context.
  • Excludes descriptions, AI Skills, and AI Actions of other agents from system actions.
  • Restricts function calling to AI Actions of the active agent and system-level actions only.
  • Provides an explicit exit mechanism to clear the bound state and return to agent selection mode.
  • Requires explicit exit before activating another agent via mention-based switching.
  • Cancels workflow execution through CancelProcessExecutionAction when exiting a workflow AI Agent.
  • Persists the active AI Agent state across page reload.
  • Restores chat context and UI state automatically after reload.

AI and automation

Creatio.ai chat panel

Fixed

Fixed an issue in Creatio.ai chat panel where outgoing messages were displayed without preserved line breaks in chat conversations. This change ensures correct rendering of multi-line messages and improves readability.

AI and automation

Creatio.ai chat panel

Fixed

Fixed an issue where a system message was inserted between an AI Agent invocation and its corresponding tool message in the Creatio.ai chat panel. In some scenarios, a file-related system message was added between the assistant tool_calls message and the corresponding tool response, breaking the message order required by the LLM and causing a BadRequestError due to missing tool response messages in the sequence. The message sequencing logic was corrected to prevent system messages from interrupting the agent-to-tool call flow. This change restores the correct message order, eliminates intermittent invocation errors, and improves stability and predictability of agent behavior in the Creatio.ai chat panel.

AI and automation

Creatio.ai add-ins

Changed

Added support for running the Creatio.ai chat panel as a personal app in Microsoft Teams. The add-in can now be accessed through a dedicated Creatio.ai tab in the Teams app bar, enabling users to use the Creatio.ai interface outside the meeting context. This change improves accessibility of Creatio.ai and supports continuous workflow directly within Microsoft Teams.

More details
  • Implemented personal app configuration for the Creatio.ai add-in for Microsoft Outlook and Teams.
  • Added the "teams_outlook_personal" value to the Creatio.ai skill in page lookup to enable standalone chat access.
  • Added support for the Creatio.ai tab in Teams environment starting from version 8.3.1, with standard error handling for earlier versions.

After installation from the Microsoft Teams store, the add-in appears in the Teams app bar and loads the Creatio.ai chat panel in a dedicated personal tab without requiring an active meeting session.

AI and automation

Machine learning

Changed

Changed the data retrieval logic for batch collaborative filtering predictions to remove the 80,000 record limitation caused by EntitySchemaQuery.GetEntityCollection and EntityCollection.MaxRowCount. Previously, running a prediction with a large user filter could result in Terrasoft.Common.InvalidObjectStateException in MLDataPredictionUserTask.ReadCFData when the in-memory entity collection exceeded the limit. The implementation now retrieves user IDs directly from the database using a SQL-based streaming approach instead of loading all records into memory. This change enables processing of audiences larger than 80,000 records, ensures stable execution of collaborative filtering predictions for large datasets without exceeding memory limits.

AI and automation

Machine learning

Fixed

Fixed a cloud compilation warning caused by an incorrect strong name reference to Terrasoft.ML.Interfaces.dll. Previously, configuration compilation produced warning MSB3106 in Microsoft.Common.CurrentVersion.targets because the assembly strong name was defined as an invalid path or malformed full assembly name. Although the build completed successfully, the warning could cause confusion and potential issues during further deployments or maintenance. The assembly reference was corrected to ensure proper resolution of the Terrasoft.ML.Interfaces dependency during compilation. This change removed ML-related compilation warnings in cloud environments and reduced the risk of confusion or deployment issues, ensuring a stable and clean configuration build process.

No-code customization

Application Designer

Changed

Added a new Creatio.ai tab to the Application Designer to enable management of AI agents and Skills as app elements. Previously, AI Agents and Skills could be managed only through dedicated sections, where elements were displayed globally and not associated with specific composable apps. The new tab provides search and sort capabilities and displays agents and skills in a gallery view. It also allows users to create prompt agents and AI Skills directly from the tab, open agent or skill pages in a new browser tab, and include these elements in app packages. If an app contains both an AI Agent and its replaced version, only the latest version is displayed to prevent duplication. This change improves structured management, packaging, and delivery of Creatio.ai elements within apps and simplifies maintenance of AI-driven solutions.

No-code customization

Application Designer

Changed

Changed the icon for the "Tabbed page mobile" template in the Select template window of the Application Designer. The updated icon better reflects the tabbed structure of the template. The update affects only the visual representation in the designer and does not impact the template structure or runtime behavior. This change improves visual clarity and ensures greater UI consistency, helping users quickly identify the correct template during page creation.

No-code customization

Application Designer

Changed

Changed the "Tabbed page mobile" template to include a dedicated Feed tab that has the Feed component preconfigured. This change improves the default mobile page structure.

No-code customization,
Schema management

Application Designer,
Configuration section

Changed

Added a new "Localization" type of configuration schemas that is created automatically for packages containing localizable resources. Each "Localization" type schema consolidates all localizable values in a package for a specific language and provides centralized access to them. Localization schemas are generated automatically when localizable resources are added to a package, and existing packages are supplemented with corresponding schemas after upgrading to version 8.3.3. Selecting a "Localization" type schema opens the Localization Designer, which displays the full list of resources included in the package. This change improves visibility of translatable content, simplifies translation tracking, and enhances support for multilingual development workflows.

No-code customization,
Schema management

Application Designer,
Configuration section

Changed

Added support for filtering configuration schemas by the "Localization" type in the Package settings tab of the Application Designer and in the Configuration section. The type now has its own dedicated icon that is used in the Type drop-down list and in the section list. This change simplifies navigation when working with localizable resources and streamlines localization management in multilingual development scenarios.

No-code customization,
Schema management

Application Designer,
Configuration section

Changed

Added support for hiding configuration schemas of the "Localization" type for inactive languages in the Package settings tab of the Application Designer and in the Configuration section. The functionality is managed by the "Show localization schemas for inactive languages" (ShowLocalizationSchemasForInactiveLanguages code) system setting. Out of the box, the value is set to "false," which hides configuration schemas of the "Localization" type for inactive languages. This change reduces visual clutter, improves navigation, and helps users focus on relevant localization content in multilingual environments.

No-code customization

Freedom UI Designer

Changed

Changed the Heading level parameter for page template titles in the Freedom UI Designer from "<label>" to "<h1>" to comply with WCAG. The update is applied automatically to all existing and new pages after upgrading to version 8.3.3. This change improves screen reader compatibility and ensures a clear, accessible page structure without impacting custom implementations.

No-code customization

Freedom UI Designer

Changed

Added the ability to configure modal window size in the Freedom UI Designer using the new Modal window size parameter. No-code creators can select predefined modal sizes ranging from S to XL, and Creatio applies the selected size consistently at runtime. The functionality is managed by the EnabledAppearanceSettings additional feature. Out of the box, the feature is unregistered and disabled. Previously, modal windows had a fixed size that could not be adjusted, which limited layout flexibility for different business scenarios. This change provides greater control over modal layouts, improves screen space utilization, and simplifies configuration of modal forms without requiring custom layout adjustments.

No-code customization

Freedom UI Designer,
Freedom UI Mobile Designer

Changed

Added real-time editing notifications to inform users when another person starts editing the same page in the Freedom UI Designer and Freedom UI Mobile Designer. Previously, users could only see that a page was opened by someone else without knowing whether active editing was in progress. Creatio now detects active editing, displays a notification, and highlights the editing user with animated avatar indicators (if available). When multiple users open the same page, the user presence element collapses automatically and provides access to the full list of users in a mini page. This change improves collaboration transparency, reduces the risk of conflicting changes, and makes concurrent page editing more predictable for no-code creators.

No-code customization

Freedom UI Designer,
Freedom UI Mobile Designer

Changed

Added a hierarchical structure view for page elements in the Freedom UI Designer and Freedom UI Mobile Designer. A new Structure tab displays page elements as a nested tree using element names or codes. The structure view is synchronized with the canvas and supports search, selection, editing, deletion, copying, and moving elements. Movement is allowed only into valid containers. Non-movable elements enforce layout rules. The tree updates automatically when users select elements on the canvas. The functionality is managed by the InterfaceDesignerShowStructureTab additional feature. Out of the box, the feature is registered and enabled. Previously, the feature was under beta testing.

No-code customization

Dashboard Designer

Changed

Added automatic configuration of the page data filter on the Dynamic filter tab of the Formula element setup window in the Dashboard Designer when the same object is selected as the page data source. The filter by page data is now set automatically. This change ensures consistent data behavior and reduces manual configuration steps.

No-code customization

Business Rule Designer

Fixed

Fixed an issue where attribute names were not displayed for secured "Text" type attributes in page-level business rules due to incorrect handling of secured attribute metadata during rule rendering. Previously, these attributes were displayed without names, making it difficult to identify and configure the correct fields. This change ensures proper display of attribute names during rule configuration and review, improves usability, and reduces the risk of misconfiguration.

No-code customization

Dynamic case execution

Fixed

Fixed an issue where adding a dynamic case configuration for a Freedom UI page of the "Case" (Case code) object disabled the progress bar on the corresponding Classic UI page. Previously, when a dynamic case was configured for the case page in Classic UI, the progress bar was displayed correctly. After adding a Freedom UI page for the same object, the progress bar continued to work on the Freedom UI page but was no longer displayed on the Classic UI page. The platform logic handling dynamic case metadata and UI bindings was updated to separate processing of dynamic case configurations for Freedom UI and Classic UI pages. This change restores independent dynamic case support for both page types and ensures consistent process visualization across interfaces.

No-code customization

Translations

Changed

Enhanced the reliability of the translation application process in multi-domain environments by preventing concurrent execution after failure recovery. The platform now ensures that only a single instance of the translation application process can run at a time, even when multiple application domains are active, for example, in IIS. This change eliminates concurrency-related issues, prevents missed translation updates, and ensures consistent and reliable application of translations in complex hosting scenarios.

No-code customization

Translations

Fixed

Fixed an issue that could cause partial failure when applying a large number of translations from the Translation section. Previously, if an error occurred while applying a single translation record (for example, due to exceeding the column length limit), processing of the entire batch was stopped. The translation application logic was updated to handle errors on a per-record basis, allowing the remaining records in the same batch to continue being processed. This change improves the reliability and predictability of bulk translation application and reduces the impact of individual record errors on localization updates.

Apps and packages

App management

Changed

Added the ability to view extended app metadata directly in the Application Hub. Previously, users had to open the app page to see key details such as version and developer information. The gallery tiles now display the Version and Developer fields, improving visibility of essential metadata for no-code creators. Existing tile behavior remains unchanged. This change improves transparency and simplifies application management without altering current functionality.

Apps and packages

App management

Changed

Added the Create pages for the mobile app checkbox to the New application window in Application Hub. Out of the box, the checkbox is selected, i.e., mobile pages are created alongside web pages. When the checkbox is cleared, sections are created without mobile pages. This change provides clear control over mobile availability during section creation and simplifies configuration of cross-platform apps.

Apps and packages

App management

Changed

Added the ability to validate compilation errors before running installation commands in WorkspaceConsole and Clio utilities using the new checkCompilationErrors parameter. Previously, installation could proceed even if the target environment contained compilation errors. When the parameter is specified, the platform performs pre-installation validation and displays detailed information about detected compilation issues in the console output. This change improves deployment reliability and helps prevent installation into environments that have unresolved compilation errors.

Apps and packages

App management

Fixed

Fixed an issue where installing Marketplace apps that lacked the "app-descriptor.json" file and included Classic UI pages failed before initialization. Previously, installation attempts for such apps ended with the "Unable to retrieve files from the Marketplace" error before the installation process started. The installation logic was updated so that the Application installer microservice correctly handles Classic UI pages and proceeds with retrieving the required files. This change ensures reliable installation of Marketplace apps and proper file retrieval even for Classic UI pages.

Apps and packages

App management,
Package management

Changed

Changed outdated maintainer names for packages and apps by replacing "Terrasoft" with "Creatio." Previously, legacy maintainer values were displayed in package and app metadata. This change ensures consistent branding and up-to-date maintainer information across the system.

Apps and packages

App performance

Changed

Changed the name of the MaxMemoryUsageToGetDataViaEntityCollection code system setting from "RAM limit for data selection via OData" to "RAM limit for data selection via Entity collection" to more accurately reflect its scope. Previously, the name suggested that the setting applied only to OData requests, while it also affects other APIs, including DataService and direct Entity API usage in source code. Additionally, enhanced the setting description to clarify that it defines memory limits for data selection operations across multiple APIs. This change improves transparency for system administrators and developers and supports more accurate configuration and performance analysis.

Apps and packages

App performance

Changed

Enhanced the NLog initialization logic to handle temporary unavailability of the logging database during Creatio startup. If a database connection attempt fails, NLog now retries the connection on subsequent log write operations instead of stopping logging until a restart. This change improves platform resilience, ensures logging resumes automatically after transient database issues, and enhances observability and supportability in unstable or dynamic environments.

Apps and packages

App performance

Changed

Changed Creatio initialization logic to execute license validation requests in parallel with the main bootstrap flow. Previously, GetExplicitLicOperationStatuses and GetUnavailableLicOperations were part of the critical rendering path and could delay UI loading. These requests are now executed asynchronously during Creatio startup, and license data is applied once received without blocking initial rendering. This change improves UI responsiveness and optimizes initialization performance.

Apps and packages

Package dependencies

Fixed

Fixed high and critical security vulnerabilities identified during a security scan in backend microservices. Vulnerable third-party components and dependencies were upgraded to secure versions in the Machine learning, GenAI, Bulk duplicate search, and Global search services. API contracts, as well as authentication and authorization mechanisms, remain unchanged. This change reduces the platform attack surface, strengthens infrastructure-level security, and maintains backward compatibility and stable service integration.

Freedom UI components

Button component

Changed

Added new preset "Plain white" or "Outline white" visual options to the Style parameter of the Button component in Freedom UI Designer. The "Plain white" style includes white text color, a transparent background in the default state, and a glass-effect hover state. The "Outline white" style includes white text color with a light glass background. The previously available "Default" style was renamed to "Plain." This change expands button styling capabilities and improves flexibility when designing light or glass-based UI compositions.

Freedom UI components

Button component

Fixed

Fixed an issue in Freedom UI pages where button menu items hidden by business rules remained visible if they contained sub-menu items due to incorrect handling of nested menu structures. The logic was corrected so that when a parent menu item is hidden, its sub-menu items are hidden as well. This change ensures consistent enforcement of business rule–based visibility in button menus.

Freedom UI Mobile components

List component

Changed

Changed the List component to align numeric values to the right for all supported numeric data types. The column header layout was updated to optimize space usage and improve data readability according to common industry standards. Space is now reserved only for the action menu button, and the reserved space for the sort button in the default state has been removed. The sort icon overlaps the column caption on hover or when sorting is active. Caption behavior was updated to display more characters when sorting is inactive, with a minimum visible length of one letter followed by two dots. This change improves visual consistency and readability of numeric data in list columns.

Freedom UI Mobile components

List component

Changed

Changed icons for the type and country filters in the List component to use out-of-the-box Creatio system icons. Previously, these filters used icons that were not included out of the box and required temporary replacements. The icons were replaced with supported alternatives from the Creatio icon library. This change ensures consistent visual representation and alignment with standard UI components.

Freedom UI components

List widget component

Changed

Added the ability to export data to an Excel file directly from the list widget using the "Export to Excel" action. Previously, widget data could not be exported without custom development. The action has its own dedicated icon, consistent with other components. Out of the box, the export action is enabled. To disable it for a specific List widget component, add the "widgetToolbarItems": [] property to the source code of the component. This change improves usability and provides flexible control over data export behavior in dashboard widgets.

Freedom UI components

List widget component

Changed

Added the ability to use lazy loading instead of eager initialization in the List widget component. Previously, the component and its dependencies were loaded during initial page rendering, increasing bundle size and impacting startup performance. The component is now loaded only when it is rendered on the page, with initialization and data loading deferred until required. This change reduces the initial bundle size and improves overall page performance.

Freedom UI components

List component,
List widget component

Changed

Added the ability to use glassmorphic styling by selecting the "Glass effect" option in the Style parameter of the List and List widget components in Freedom UI Designer. Previously, lists did not support glassmorphic styling and could not be visually aligned with glass-style analytic widgets. This change enables consistent UI compositions and improves visual alignment of lists with analytic widgets.

Freedom UI components

List component,
List widget component,
Expanded list component

Changed

Changed the behavior of Freedom UI Designer to restrict automatic default object population when adding Expanded list or List components to a page that already has a primary data source. Automatic default object assignment is now preserved only for the List widget component. This change prevents unintended object binding and ensures more predictable component configuration on pages that have an existing data source.

Freedom UI components

Multiselect lookup component

Changed

Changed validation behavior of the Multiselect lookup component on pre-configured process pages to enforce required-field validation. The page now prevents saving or completion until at least one value is selected and displays the out-of-the-box required-field validation message, consistent with regular Freedom UI pages. The save request logic was updated to respect the component validation state and block saving when validation fails for both the standard Save button and custom Save or Next buttons generated by the business process page elements. Previously, required validation for the multiselect lookup was enforced only on regular Freedom UI pages, while pre-configured process pages allowed saving empty values. This change ensures data completeness in business processes, reduces the risk of saving empty multi-selection fields, and aligns validation behavior between process pages and regular Freedom UI pages.

Freedom UI components

Multiselect lookup component

Fixed

Fixed an issue in the Multiselect lookup component whose Lookup view parameter is set to "Selection window" on pre-configured process pages, where the field opened using the default list behavior instead of the configured "Selection window" lookup view. Previously, Creatio did not correctly detect crt.SaveRecordRequest within the request array, which prevented the selection window behavior from being applied. The issue was caused by incorrect handling of crt.SaveRecordRequest detection logic in the _getButtonWithSaveRecordRequestExist() method of "base-select-preprocessor.ts." Now, Creatio correctly processes request configurations when an array of requests is returned, ensures proper detection of crt.SaveRecordRequest, and prevents incorrect activation of disableManualSave when a valid Save button exists. This change restores the expected behavior in pre-configured process pages and aligns validation behavior between process pages and regular Freedom UI pages.

Freedom UI components

Approvals component

Fixed

Fixed an issue in the Approvals component where it did not get hidden automatically when all related approvals were canceled or deleted. The auto-hide logic was updated to treat canceled and deleted approvals as no data and to refresh the component state after approvals are canceled by a process, including scenarios where a record leaves a stage that triggers approval. The component now gets hidden automatically when no active approvals remain, without requiring a manual page reload. This change ensures correct auto-hide behavior and improves UI consistency.

Freedom UI components

Quick filter component

Changed

Added support for time selection in the Quick filter component whose Choose a filter type parameter is set to "Date/Time" by adding a new Enable time checkbox in the Freedom UI Designer. Out of the box, the checkbox is cleared. Time selection is available for both "Set up filter by date range" and "Set up filter by one date" values of the Choose a filtering method parameter. When the checkbox is selected, the quick filter allows users to enter date and time manually or select time using a time picker. Filter converters and handlers were updated to correctly generate and process date/time conditions, and the quick filter value updater was enhanced to support date/time values. Default time values (12:00 AM for the start time and 11:59 PM for the end time) are applied automatically for date ranges if time is not specified directly. Previously, the Quick filter component supported date values only and did not allow filtering by exact date and time. This change increases filtering precision, improves consistency of quick filter behavior, and reduces the need for additional filtering logic.

Freedom UI components

Quick filter component

Changed

Added support for fiscal periods in the Quick filter component whose Choose a filter type parameter is set to "Date/Time" by adding a new Show fiscal periods checkbox in the Freedom UI Designer. Out of the box, the checkbox is cleared. When selected, the quick filter displays a Fiscal tab with non-editable "Previous week," "Current week," "Next week," "Q1," "Q2," "Q3," "Q4," "First half year," "Second half year," "Previous year," "Current year," and "Next year" macros, and allows switching between fiscal and calendar calculation modes. Date ranges are calculated based on fiscal boundaries derived from the "Start date of the fiscal year" (FiscalYearStartDate code) system setting. Out of the box, the value is empty. The calculated ranges are applied consistently across lists, dashboards, widgets, and expanded lists. The filter automatically falls back to calendar logic if the system setting is not defined. Previously, macros used calendar periods only. This change aligns filtering with the company’s fiscal structure, improves reporting accuracy, and reduces manual date selection while keeping calendar mode as the default.

Freedom UI components

Quick filter component

Changed

Changed the width behavior of the Quick filter component whose Choose a filter type parameter is set to "Lookup" to use a dynamic width instead of a fixed width. Previously, the filter used a fixed narrow width that truncated long values with ellipsis and reduced readability. The component now expands up to a maximum width of 640 px depending on content and available screen space. Responsive behavior ensures the filter adapts to the available screen space without breaking the surrounding layout. Existing tooltip behavior is preserved, and multi-line wrapping remains disabled. This change improves usability, reduces selection errors, and ensures consistent layout behavior across different screen sizes.

Freedom UI components

Folders component,
Quick filter component

Changed

Added an option to make quick and advanced filters accent-insensitive for selected "Text" type columns in PostgreSQL. The filter behavior can be configured individually for each column where accent-insensitive matching is required. Previously, filtering was accent-sensitive and required exact matching of accented characters. Users can now find records regardless of accented or national characters in text values (for example, José, Jose, Jòsé; Łódź, Lodz; München, Munchen), while displayed values remain unchanged. This change improves filtering accuracy and usability in multilingual environments without affecting stored data.

Freedom UI components

Summaries component

Changed

Added support for business rules in the Summaries component and its individual items on Freedom UI pages. Previously, business rules did not consistently manage visibility and activity at both the component and item levels, and execution of "Show elements" and "Hide elements" rules could behave inconsistently depending on default visibility settings. The updated logic ensures correct rule execution regardless of the default visibility configuration. This change provides more granular control over summary behavior and improves consistency of business rule execution in Freedom UI.

Freedom UI components

Summaries component

Changed

Changed formatting logic in the Summaries component to preserve trailing zeroes for all supported Money data types. Previously, trailing zeroes could be trimmed for Money1, Money2, and Money3, leading to inconsistent display. This change ensures consistent formatting behavior for new Money types and aligns them with existing formatting rules.

Freedom UI components

Message composer component

Fixed

Improved attachment upload handling in the Message composer component. When an attachment is only partially uploaded (for example, due to connectivity issues), Creatio now validates file integrity during message sending. If a corrupted file is detected, the message is not sent, and Creatio displays a detailed error message identifying the problematic attachment. This change helps prevent sending incomplete files and improves the reliability of message delivery.

Freedom UI components

Message composer component

Fixed

Fixed an issue where searching for recipients in the To field of the message composer for the "Email" channel did not return users that have accented or national characters in their names (for example, José or Łukasz). This change improves recipient search accuracy and usability in multilingual environments.

Freedom UI components

Message composer component

Fixed

Fixed an issue where the message composer size was not adjusted correctly after inserting an email template. This change ensures proper layout resizing and prevents content overflow when working with templates.

Freedom UI components

Timeline component

Fixed

Fixed the display of the Read more button for long email messages that include tables in the timeline. Previously, the button was not displayed for emails containing complex HTML structures, which prevented users from viewing the full message body. The button is now shown consistently when email content exceeds the preview limit, allowing users to expand and read the full email message in the timeline.

Freedom UI components

Hierarchy component

Fixed

Fixed an issue where the Hierarchy component was not refreshed immediately after add, edit, or delete operations. Previously, structural changes to hierarchy were not always reflected on the page, resulting in outdated views. The component now emits a model change event on add, edit, and delete actions, ensuring that the hierarchy is refreshed immediately and consistently reflects all structural modifications.

Fields and inputs

"Text" type field,
"Number" type field,
"Date/Time" type field,
"Dropdown" type field

Fixed

Fixed an issue where fields whose Read-only checkbox is selected in the Freedom UI Designer could be modified by removing the readonly attribute from the HTML input element in the browser. The issue affected "Text," "Number," "Date/Time," and "Dropdown" type fields and allowed users to change and save values despite the non-editable configuration. Read-only validation is now enforced at the application level in addition to the HTML attribute, preventing client-side manipulation from bypassing restrictions. Attempts to modify such fields are blocked both on the client and server sides. This change prevents unauthorized modifications, ensures data integrity, and aligns field behavior with the configured Read-only checkbox.

Fields and inputs

"Rich text" type field

Changed

Changed the placeholder text color in "Rich text" type fields to improve contrast and comply with WCAG. This change enhances text readability and accessibility for users.

Fields and inputs

"Phone" type field

Fixed

Fixed an issue where Bulgarian phone numbers were validated incorrectly in "Phone" type fields. This change ensures accurate phone number validation and improves overall data quality.

Analytics

Dashboards

Changed

Added the ability to manage favorite dashboards at runtime. Users can add dashboards to favorites or remove them directly from the dashboard list or from a dashboard page. Previously, dashboards could not be marked or grouped as favorites. Favorite dashboards are now displayed in a dedicated "Favorites" block at the top of the list, which is visible only when at least one dashboard is marked as a favorite. Favorites are stored per user, ensuring each user has an individual set of preferred dashboards. This change improves dashboard navigation and personalization.

Analytics

Metric

Changed

Added runtime notifications for metric calculation errors. Users are now notified when a metric calculation fails due to issues such as division by zero or system errors. This change improves transparency of metric calculations and helps users identify and resolve configuration issues.

Freedom UI components,
Analytics

Dashboards component,
Metric,
Column

Changed

Added support for configuring the Dashboards component, metrics, and columns to browse related data recursively. The configuration allows defining recursive navigation rules across linked or hierarchical datasets using the new hierarchyConfig property in the Freedom UI page source code. Runtime logic resolves subsequent data levels based on the selected data point and applies the configured relationship rules during navigation. Previously, navigation was limited to a single level of related data and required switching contexts to continue analysis. This change enables multi-level drill-down exploration within a single flow, improves root-cause analysis and data exploration, reduces manual navigation steps, and ensures consistent analytics browsing while respecting configured relationships and access permissions.

Analytics

List widget

Fixed

Fixed an issue where localizable resources of list widgets in dashboards were not loaded when the schema that implements the dashboard was replaced in the environment and its localizations were modified. This change ensures that translated column captions of list widgets in dashboards are correctly applied at runtime and preserved after a page refresh.

Analytics

iFrame

Added

Added a new iFrame widget to Freedom UI Designer that enables embedding external content directly on Freedom UI pages. The widget supports configurable permission settings such as camera, microphone, fullscreen, and other browser features, defined through structured parameters in the setup area and stored as technical iFrame attributes, while preserving custom metadata-defined values. This change expands integration capabilities, simplifies embedding of external apps without requiring custom code, and provides controlled access to browser features for embedded content.

Business rules

Business rule management

Fixed

Fixed an issue where UId values in "Addon" type schemas that implement business rules were re-generated after resaving. This behavior caused unnecessary merge conflicts when working with version control systems. This change preserves existing UId values during resave operations and ensures more stable version control workflows.

Business process setup

Business process parameters

Fixed

Fixed an issue in the Select parameters window for the "Create from element" business process parameter type for composite objects, where reselecting a different source element retained the previous Select/Deselect all checkbox state. Previously, when users switched from one element, such as "Account," to another, such as "Contact", the checkbox remained selected and the Select button was disabled. Now, when the source element is changed, no fields are preselected out of the box, and the Select/Deselect all checkbox works correctly for the newly selected element. This change restores expected selection behavior and allows users to complete configuration without restrictions.

Business process setup

Read data element

Changed

Changed the "Lead distribution" business process to support manual start and accept a lead as an input parameter. The process can now be triggered manually and receive a lead directly instead of relying solely on the Read lead data process element. Internal process logic and conditions were updated to correctly handle an externally passed Lead parameter and ensure proper execution when invoked from custom dynamic case or referral scenarios. Previously, the process was triggered only by predefined events and initialized the Lead parameter using the Read lead data process element. This change enables reuse of the out-of-the-box lead distribution logic in custom referral and dynamic case scenarios and ensures consistent lead routing across both standard and custom flows.

Business process setup

Modify data element

Changed

Added detailed logging and execution tracing for the Modify data process element. Previously, execution details such as element start and completion events, input parameter values, applied data changes, and runtime exceptions were not fully recorded. The platform now logs these events to provide greater visibility into process behavior. This change improves monitoring capabilities and reduces the time required for troubleshooting and root cause analysis.

Business process setup

Change access rights element

Fixed

Hid the deprecated "Denied" record-level access right in the Read, Edit, and Delete expanded lists on the Access rights page. Although this access level has been deprecated since version 7.2.0, records with the "Denied" value could still be added via automation, which could mislead users. The update is applied automatically to existing Change access rights process elements after upgrading to version 8.3.3. This change improves clarity of access rights configuration and prevents unintended use of deprecated permission levels.

Integrations and APIs

OAuth authorization

Changed

Added the ability to use the client credentials grant for authentication of REST web services in the Web services section. The web service page now includes a new Grant type field that has "Authorization code" and "Client credentials" options. Out of the box, the field value is set to "Authorization code" to preserve backward compatibility. The page dynamically adapts to the selected grant, displaying and requiring only relevant fields. Previously, OAuth authorization supported only the authorization code grant, which required end-user interaction. This change enables secure server-to-server integrations without user credentials, simplifies integration setup for system-level scenarios, and maintains compatibility with existing configurations.

Integrations and APIs

OAuth authorization

Changed

Added the ability to configure additional provider-specific parameters for a REST web service when the Grant type field is set to "Client credentials." The web service page now includes a new Additional parameters expanded list that contains out-of-the-box "Key" and "Value" columns with lengths of 250 and 500 characters respectively. Previously, integration with providers requiring non-standard token request parameters required custom development. This change enables flexible configuration of OAuth-based integrations without backend modifications.

Integrations and APIs

OAuth authorization

Fixed

Fixed an issue where API requests made using revoked OAuth tokens returned an incorrect HTTP status code. Creatio now returns "401 Unauthorized" instead of "403 Forbidden" when a revoked token is used. This change aligns API behavior with standard HTTP authentication semantics, simplifies error handling for API consumers, and improves the reliability of integrations and security-related workflows.

Integrations and APIs

OAuth authorization

Fixed

Fixed an issue where the OAuth 2.0 authentication page for web services was displayed incorrectly when opened from the Configuration section due to improper styling initialization. Updated the page initialization logic and styles to ensure consistent rendering regardless of the access entry point. This change improves usability and prevents confusion during web service setup.

Integrations and APIs

OData

Changed

Changed the default value of the Cached checkbox for the "RAM limit for data selection via Entity collection" (MaxMemoryUsageToGetDataViaEntityCollection code) system setting from cleared to selected. Previously, the setting value was read directly each time it was accessed, which could cause unnecessary overhead and performance degradation. Now, the setting value is retrieved from the cache by default. This change reduces repeated reads, optimizes system resource usage, and improves the performance of data retrieval operations that rely on this setting.

Integrations and APIs

OData

Fixed

Fixed a memory leak in the ModelBinderFactory class used during OData request processing in .NET 8 deployments. The class now correctly releases resources during model binding and no longer retains unnecessary references. This change reduces the risk of memory overconsumption, prevents potential out-of-memory errors under high load, and improves overall platform stability and performance.

Integrations and APIs

EntitySchemaQuery class

Fixed

Fixed an issue in the EntitySchemaQuery.Filter.Clone() method affecting filters that use backreferences. Previously, cloning such filters could lead to incorrect behavior during query execution. This change ensures proper duplication of filter conditions and consistent handling of backreference filters.

Integrations and APIs

File processing

Changed

Changed attachment handling in Freedom UI to prevent users from leaving a page while a file upload is still in progress. Previously, users could close or reload the browser tab during upload, which could result in incomplete or corrupted files being saved. The platform now implements browser-level handling for tab close, tab reload, and browser close events, displaying a warning message about active uploads before the action is completed. This change helps prevent corrupted attachments and improves reliability of file upload operations.

Integrations and APIs

Emails

Fixed

Fixed an issue in email synchronization where users could not add a new mailbox because of duplicate emails in contact communication options. This change ensures successful mailbox setup and prevents conflicts caused by duplicate contact emails.

Integrations and APIs

Chats

Changed

Added support for the new SMS channel. User roles who have permission to the "Access to "Chat settings" section" (CanManageChats code) system operation can create, edit, activate, and deactivate SMS channels on the Chat settings page. Out of the box, only users that have the "System administrators" organization role and "Developer" and "Administrator" role on ALM Portal can execute the action. The SMS channel operates through the Twilio provider, similarly to the WhatsApp channel. This change expands chat channel configuration capabilities and enables centralized management of SMS connectivity.

Integrations and APIs

Chats

Changed

Added support for sending text messages (SMS) and attachments (MMS) in the Agent Inbox panel of the Contact Center app and the Chats sidebar of the communication panel via the configured SMS channel. This change enables full SMS/MMS communication within chats while ensuring compliance with channel and provider limitations.

More details

SMS messages are processed as follows:

  • UI text length validation is applied in the Agent Inbox panel only.
  • A validation notification is displayed and the btn_send_message.png button is disabled if the maximum allowed length is exceeded.
  • A tooltip is displayed if a message exceeds the single SMS length limit and will be split into multiple SMS messages.

MMS messages are processed as follows:

  • File type restrictions are managed by the "File extensions DenyList" (FileExtensionsDenyList code) system setting and Twilio file type limitations.
  • File size limits are managed by the Twilio file size limitations and the "Attachment max size" (MaxFileSize code) system setting. Out of the box, the value is set to "10," in megabytes.
  • A detailed error message is displayed if the file type is not allowed or the file size limit is exceeded.
  • Validation behavior is consistent with other chat channels.

Integrations and APIs

Chats

Changed

Added automatic creation and routing of chats in Creatio based on incoming SMS and MMS messages via the configured SMS channel. SMS conversations are processed using the chat processing mechanism and are available in the Agent Inbox panel of the Contact Center app and the Chats sidebar of the communication panel. This change integrates SMS/MMS communication into chat-based workflows and ensures consistent routing, contact identification, and conversation history handling across channels.

More details

Upon receiving an incoming SMS or MMS message, Creatio:

  • automatically creates a new chat
  • routes the chat to the configured queue according to channel settings
  • matches an existing contact to phone number or creates a new contact if no match is found
  • displays the full conversation history within the same channel

Code-based customization

Object Designer

Changed

Changed the backend data binding logic to restrict binding of object columns of the "Encrypted string" type. Encrypted columns are now automatically ignored during binding creation. This change prevents accidental exposure or processing of sensitive data, eliminates potential security gaps in data binding scenarios, and aligns backend behavior with the existing frontend restriction.

Code-based customization

Object Designer

Changed

Added the Show seconds checkbox to the Behavior property block of Object Designer for the "Date/Time" and "Time" type columns. Out of the box, the checkbox is cleared, and values are displayed in HH:MM format. When selected, the column accepts and displays time values in HH:MM:SS format. Metadata-based formatting logic ensures the selected format is applied consistently across lists, summaries, filtering, and sorting operations. Previously, time values were displayed in HH:MM format only, and time precision could not be configured at the column level. This change provides flexible metadata-level control over time precision while preserving database integrity and ensuring consistent formatting across the user interface.

Code-based customization

Quartz task scheduler

Changed

Added proactive thread pool starvation diagnostics for .NET Framework. Creatio now detects potential worker thread pool starvation conditions and automatically collects diagnostic logs and, optionally, memory dumps before a crash occurs. Administrators can configure the dump type and frequency or disable dump creation if required. Creatio validates configuration values, applies safe defaults, and prevents unsafe combinations. Previously, diagnostic data was typically available only if a memory dump was manually collected during a crash or required reproduction of the issue. This change preserves critical runtime information during starvation scenarios, accelerates root cause analysis, and improves the efficiency of stability investigations for on-site deployments.

Code-based customization

Quartz task scheduler

Changed

Changed the health check endpoint to always return a response body and include detailed thread pool metrics. The response now contains a ThreadPool object that exposes Max, Min, and CurrentBusy values for worker threads, and MaxIO, MinIO, and CurrentBusyIO values for IO threads. An aggregated IsHealthy flag was added, returning "true" when all checks pass and "false" when at least one check fails. The endpoint now returns a JSON response body for both successful and failed checks while preserving existing field names for backward compatibility. Previously, successful health checks could return no response body and did not expose thread pool state information. This change improves observability of application health, enables monitoring systems to collect thread pool utilization metrics, and helps diagnose thread starvation scenarios more effectively.

Code-based customization

Quartz task scheduler

Changed

Changed the default minimum thread pool configuration for on-site deployments to reduce thread starvation scenarios under high load. The internal default formula for the worker thread pool minimum count was updated to 20 + (CPU core count × 10), and the default formula for the IO completion port (IOCP) thread pool minimum count was updated to CPU core count × 2. Previously, lower baseline thread pool settings could lead to thread starvation, excessive thread spawning, and potential application freezes under load. This change aligns on-site deployments more closely with cloud defaults, improves runtime stability, and enhances thread pool diagnostics.

Schema management

Configuration section

Fixed

Fixed an issue where index UId values in "Object" type schemas were re-generated when modifying index properties. This behavior caused unnecessary merge conflicts when working with version control systems. This change preserves existing index UId values during index property modifications and ensures more stable version control workflows.

Schema management

Configuration section

Fixed

Fixed an issue where the CreatedInPackageId property was re-generated each time a "Client module" type schema was saved in a different environment. This behavior caused unnecessary metadata differences and merge conflicts in version control systems. This change preserves existing CreatedInPackageId values during save operations, reduces unnecessary conflicts and ensures more stable version control workflows.

Schema management

Schema inheritance

Fixed

Fixed an issue with resolving localizable resources in deep schema hierarchies where renamed values from intermediate packages were ignored when further schema replacements existed in the hierarchy. Creatio now correctly applies updated localizable resource values regardless of their position in the schema hierarchy. This change ensures consistent UI text, prevents outdated labels or captions from appearing, and improves reliability in complex package layering scenarios.

Schema management

Schema inheritance

Changed

Added support for Created on and Modified on properties for "Localization" type schemas, consistent with other configuration elements. The Created on property reflects when the first localizable value was added to a package, while Modified on shows the most recent update to any localizable value. This change improves visibility into localization metadata, simplifies auditing of multilingual content, and helps teams track and manage translation timelines more effectively.

Schema management

Schema inheritance

Fixed

Fixed a performance issue related to requests to the "Compilation errors" (VwCompilationErrors code) object that could slow down page loading in environments with a large number of compilation error records. Request handling for this view has been optimized to ensure faster response times. This change improves overall page load performance and Creatio responsiveness in environments that contain extensive compilation error data.

Schema management

"Data" type schema

Changed

Added validation to prevent creation of object columns that could result in duplicated property names in the generated "Data" type schema. A conflict could occur when an object contained a regular column (for example, ContactName) and a "Lookup" type column (for example, Contact) whose generated primary display value property produced the same name (for example, ContactName). Previously, such naming conflicts were not validated and could lead to duplicated properties in the generated schema. This change ensures data schema consistency and prevents runtime issues caused by duplicate property names.

Data models

Data model attribute

Changed

Added the crt.IsEqual converter for Freedom UI. The converter compares the equality comparison between the bound ViewModel attribute value and the first parameter passed to the converter. It supports collection comparison and returns a boolean result that can be used in UI expressions. This change enables correct evaluation of complex objects and collections in bindings and conditional logic within UI elements

Administration

System settings

Changed

Changed the default value of the Cached checkbox on system setting pages from cleared to selected. The update is applied automatically to newly created system settings after upgrading to version 8.3.3. This change enhances performance by automatically enabling caching for new system settings.

Administration

System settings

Changed

Changed the default values of the Access for reading for internal users and Access for modification for internal users parameters on system setting pages from "Allow for all" to "Restrict for all." The update is applied automatically to newly created system settings after upgrading to version 8.3.3. This change improves data protection by preventing unintended access to system settings by internal users.

Administration

System settings

Changed

Added the ability to configure the fiscal year start month and the first day of the week using system settings. Automatic maintenance of fiscal periods in the "Period" (Period code) object was implemented to generate and keep fiscal years, half-years, quarters, months, and weeks aligned with the configured fiscal calendar. An executor reacts to changes in the relevant system settings, ensures required values exist in the "Period type" (PeriodType code) object column, and generates or updates period records accordingly. For example, if the fiscal year starts in May, Creatio generates half-year periods such as 01.05.2025–31.10.2025 for the first half and 01.11.2025–30.04.2026 for the second half. Previously, fiscal periods had to be prepared and maintained manually or via custom development, which could cause misalignment across environments and inconsistencies in reporting when fiscal calendars differed. This change ensures consistent fiscal calendar segmentation for reporting and downstream logic, reduces manual maintenance, and centralizes fiscal period configuration.

More details

Added the following system settings to support fiscal calendar configuration:

  • "Fiscal Year Name Template" (FiscalPeriodYearNameTemplate code) that defines the template used to generate fiscal year names. Out of the box, the value is set to "Fiscal Year {0:yyyy}-{1:yyyy}."
  • "Fiscal years range" (FiscalYearRange code) that defines the number of fiscal years before and after the current year for which periods are generated. Out of the box, the value is empty.
  • "Start date of the fiscal year" (FiscalYearStartDate code) that defines the first day of the fiscal year for automatic creation of fiscal periods. Only the month is used, the day is treated as 1. Out of the box, the value is empty.
  • "Fiscal week start day" (FiscalWeekStartDay code) that defines the first day of the fiscal week. Out of the box, the value is empty.
  • "Fiscal Half Year Name Template" (FiscalPeriodHalfYearNameTemplate code) that defines the template used to generate fiscal half-year names. Out of the box, the value is set to "{0:0} Fiscal Half Year {1:yyyy}-{2:yyyy}."
  • "Fiscal Week Name Template" (FiscalPeriodWeekNameTemplate code) that defines the template used to generate fiscal week names. Out of the box, the value is set to "Fiscal Week {0:00} {1:yyyy}-{2:yyyy}."
  • "Fiscal Quarter Name Template" (FiscalPeriodQuarterNameTemplate code) that defines the template used to generate fiscal quarter names. Out of the box, the value is set to "Fiscal Quarter {0} {1:yyyy}-{2:yyyy}."
  • "Fiscal Month Name Template" (FiscalPeriodMonthNameTemplate code) that defines the template used to generate fiscal month names. Out of the box, the value is set to "Fiscal Month {0:00} {1:yyyy}-{2:yyyy}."

Administration

Configuration activity log

Added

Added the Configuration activity log page to provide centralized tracking of configuration changes and system-level operations across the platform. The log is available as a read-only page in the System setup section of System Designer and is accessible only to users who belong to the "System administrators" organizational role. Previously, configuration actions, compilation operations, additional feature updates, and system setting changes were not consolidated into a single structured log, limiting visibility and governance control. The log automatically records configuration operations defined in the "Configuration operation" (ConfOperation code) object and tracks changes to elements defined in the "Configuration element type" (ConfElementType code) object. Each record includes contextual details such as operation type, affected element, package, application, responsible user, timestamp, parent operation, and execution status defined in the "Configuration activity status" (ConfActivityStatus code) object. Installation operations include attached log files. The list supports filtering, folders, and search capabilities. This change improves transparency, traceability, and operational control, simplifies troubleshooting, and provides system administrators with a reliable source of configuration activity information.

Administration

Configuration activity log

Added

Added the ability to manage retention of the configuration activity log through manual and automatic cleanup to prevent accumulation of log records and related attachments over time. Users who belong to the "System administrators" organizational role can manually remove records up to a selected date and configure automatic cleanup based on a defined retention period stored in the "Configuration activity log retention period" (ConfigurationActivityLogRetentionPeriod code) system setting. Out of the box, the value is set to "90." When automatic cleanup is enabled and the retention period is specified, the platform removes records older than the defined number of days and deletes associated file attachments for both configuration activity log and compilation history records using the "Update configuration activity log retention period" business process. Confirmation messages are displayed for critical actions, including enabling or disabling the cleaner and executing manual cleanup. This change improves control over log storage, prevents excessive data accumulation, and simplifies long-term maintenance of configuration history data.

User and access management

User management

Changed

Added the ability for users who belong to the "System administrators" organizational role to manage the Time Zone and First day of the week fields directly on the user page in the Users section. Previously, these fields were available on the Basic settings tab of the user profile page, but system administrators could not modify their values for other users. This change enables centralized administration of user regional settings and allows system administrators to configure time zone and calendar preferences for selected users.

User and access management

User management

Changed

Enforced password change for the out-of-the-box "Supervisor" user in on-site deployments by setting the ForceChangePassword flag to "1" in the SysAdminUnit table. Previously, the built-in "Supervisor" account could continue using the initial password after installation. This change requires a password update upon the next successful login and reduces the risk of using default or previously compromised credentials.

User and access management

Access rights

Changed

Added support for processing large volumes of data during access right update for object records. Previously, right recalculation could encounter performance limitations when handling large datasets. This change improves scalability and ensures stable execution of access rights processing for high-volume records.

User and access management

System operations

Changed

Added the ability to control access to the "Debug mode" (IsDebug code) system setting. Previously, modification of the setting was not governed by a dedicated permission. The platform now ensures that only user roles who have permission to the "Can manage debug mode" (CanManageDebugMode code) system operation can modify the setting and displays a console notification when additional permissions are required. Out of the box, only users that have the "System administrators" organization role and "Developer" role on ALM Portal can execute the action. This change strengthens access control and improves transparency when managing debug mode configuration.

User and access management

System operations

Changed

Removed obsolete logic for updating the "Position" column on the system operation page from the access rights modification function. Previously, the function contained outdated processing related to updating the "Position" column that was no longer required. This change simplifies access rights modification logic and removes redundant processing.

Authentication

OpenID authentication

Changed

Added the ability to control automatic user provisioning during OpenID authorization when OpenID is configured via system settings instead of the Single Sign On configuration section. The functionality is managed by the "Disable OpenId user provisioning" (DisableOpenIdUserProvisioning code) system setting. Out of the box, the value is set to "false." When "true," it prevents automatic user account creation on first login and user data updates on subsequent logins. This change provides better control over OpenID authentication behavior and user provisioning in custom or simplified OpenID configurations.

UX

Page performance

Fixed

Fixed an issue where a Freedom UI page schema was incorrectly marked as changed during page load if the Tabs component was present. During initialization, unintended schema modification logic was triggered, even though no actual changes were made, resulting in unnecessary schema updates. The page initialization lifecycle was adjusted to prevent schema changes when rendering pages that contain the Tabs component and to maintain schema state stability during load. Previously, opening such pages could trigger false-positive change detection and redundant save prompts. This change ensures stable schema behavior during page initialization and eliminates unintended schema updates.

UX

Record management

Fixed

Fixed an issue where sorting did not work in the Object permissions (read-only) expanded list on the Access settings tab of the technical user page. The list can now be sorted by clicking column headers, consistent with standard list behavior across the platform. This change improves usability and makes managing object permissions for technical users more efficient and predictable.

Accessibility

Screen reader support

Changed

Added screen reader announcements for loading masks displayed during record saving via the default Save buttons to improve accessibility and comply with WCAG. The LiveAnnouncementService is integrated to announce specific messages when loading masks appear and disappear. This change provides real-time feedback to users that have visual impairments and enhances accessibility during UI transitions.

Communication

Chats

Changed

Added support for sending images and files in the WhatsApp chat channel from the Chats sidebar of the communication panel. Agents can now attach and send files using the same interface and behavior as in other supported chat channels. This change ensures a consistent agent experience across chat channels and enables seamless file and image sharing in WhatsApp conversations.

More details

File type restrictions are managed by the "File extensions DenyList" (FileExtensionsDenyList code) system setting and WhatsApp-specific rules. File size limits are managed by the "Attachment max size" (MaxFileSize code) system setting and individual messenger platform limitations. Out of the box, the value is set to "10," in megabytes. If the limit is exceeded, Creatio displays a detailed error message.

Each file or image is sent as a separate message. If both text and attachments are included, they are sent as individual messages. Attachments are previewed before sending: files display the name (with ellipsis truncation when needed) and a file-type icon; images are displayed as thumbnails. Multiple attachments support horizontal scrolling.

Communication

Chats

Fixed

Fixed the display of video messages in chats on the Chats sidebar of the communication panel. Previously, video files sent via Telegram were not displayed in chat conversations, which prevented users from viewing video content. Video files sent via Telegram are now rendered correctly. This change restores expected visibility and usability of video messages, enabling users to view and access shared video content directly from the chat interface.

Communication

Chats

Fixed

Fixed a performance issue that caused delays when agents accepted chats in high-volume queues. Previously, accepting a single chat triggered distribution logic for all pending chats in the queue, resulting in chat acceptance delays of more than 10 seconds. Distribution processing is now applied only to the chat being accepted. This change ensures immediate chat assignment and significantly faster response times for agents in high-volume environments.

Communication

Chats

Fixed

Fixed an issue that prevented chat agents from scrolling the list of active chats on the Chats sidebar of the communication panel. Previously, chat agents could not view or switch to active chats beyond the visible area, which disrupted workflows and delayed responses. Vertical scrolling is now enabled when the number of active chats exceeds the visible space and works consistently across different screen sizes. This change restores full visibility of active chat sessions and improves usability and multitasking efficiency for agents working with multiple chats.

Communication

Chats

Fixed

Fixed an issue in the chat routing mechanism where an unhandled NullReferenceException exception was thrown when operator data was missing from the cache. Previously, a missing or uninitialized operator cache record caused the routing flow to fail and prevented chats from being assigned to available chat agents. The GetOperatorState() method now validates that an operator exists in the cache before accessing its state. When an operator is not found, Creatio returns a default agent state instead of throwing an exception. The routing logic also skips faulty or uninitialized operator records and continues assigning chats to other eligible agents. This change improves the stability and fault tolerance of the chat routing engine and prevents inbound chat processing from being blocked by missing operator cache records.

Communication

Chats

Fixed

Fixed an issue where chat distribution triggered on chat acceptance was limited to the agent's currently selected queue, even when the agent was available and assigned to multiple queues. Now, the distribution logic evaluates all queues assigned to the agent and considers pending chats from any eligible queue when the agent becomes available. This change ensures balanced workload distribution, reduces idle time, and improves overall service efficiency.

Communication

Emails

Changed

Added the "Manage service providers" action to the actions on the Emails sidebar of the communications panel. The action is visible only to user roles who have permission to the "Email providers list setup" (CanManageMailServers code) system operation. Out of the box, only users that have the "System administrators" organization role and "Developer" and "Administrator" role on ALM Portal can execute the action. This change simplifies access to email provider configuration for administrators and improves navigation efficiency.

UX

Page management

Changed

Added the ability to hide the splash screen logo. The functionality is managed by the Hide splash screen logo image checkbox in the Advanced expanded list of the Appearance setup page. Out of the box, the checkbox is cleared. Previously, users could not control whether the logo was displayed on the splash screen. This change provides greater flexibility in customizing the Creatio appearance.

UX

Page management

Fixed

Fixed an issue where list and form pages could freeze after changing the code of an object referenced by a lookup and used in forward references. The page rendering logic was updated to handle such changes gracefully. Previously, modifying the referenced object code could cause page initialization failures or UI freezes. This change ensures that pages open correctly and display "Column removed" for affected controls instead of becoming unresponsive.

UX

Page management

Fixed

Fixed an issue where duplicate error and success notifications were displayed when saving a record with an empty relation column in a many-to-one relationship. The save handling logic was updated to prevent a success notification from being triggered when the primary model was not saved due to a validation failure. Previously, both success and error messages could appear simultaneously in validation failure scenarios. This change ensures that only the appropriate error message is displayed and improves the consistency of save notifications.

Creatio products and apps

Category

Feature

Status

Description

Customer 360

Accounts section,
Account page

Changed

Added the Tier field to the account profile on the account page and the "Tier" column to the Accounts list page to support territory management and account segmentation during daily account operations. Previously, the "Tier" attribute was available only in the Data model attributes group of the Freedom UI Designer element library, limiting user awareness and usage. This change improves visibility of territory segmentation, reduces confusion about missing data, and enables consistent use of Tier when managing accounts.

Customer 360

Contacts section

Changed

Added automatic duplicate validation when saving a new contact. Previously, duplicate contacts could be created in Freedom UI without automatic validation during saving. Now Creatio triggers the global search service and displays the Potential duplicates found mini page if matches are detected. The mini page displays the columns in which duplicates were identified. If you need to limit comparison to specific columns, configure them in the Favorite columns for deduplication lookup. Since the functionality relies on the global search service, register and enable the ESDeduplication and EnableDeduplicationFreedomUI additional features. This change reduces the risk of duplicate contacts, improves data quality, and provides flexible duplicate resolution options at the moment of contact creation.

More details

The mini page includes a list of potential duplicates and Edit record, Save anyway, and Merge buttons.

  • When clicking Edit record, the mini page closes and the new contact can be modified.
  • When clicking Save anyway, the new contact is saved as a duplicate.
  • When clicking Merge, the unsaved contact participates in the merge process instead of being created separately. Users can select which data to merge.

The mini page closes automatically after the selected action is completed.

  • Added the Favorite columns for deduplication lookup based on the "Favorite columns for deduplication" (DeduplicationFavoriteColumns code) object. The lookup stores configurable comparison columns and their order. If the lookup contains selected columns, the global search service searches for duplicates only by those columns.
  • Updated the ValidateDuplicatesOnSaveHandler to use the configured columns. Graceful handling is implemented when the deduplication service is unavailable, allowing the record to be saved without blocking the user.

Productivity

Calendar section

Changed

Added the Calendar settings mini page in Freedom UI. Previously, selecting the "Set up synchronization" action in the Calendar section opened the settings page in the Classic UI. The mini page is now supported for Microsoft 365 accounts. This change modernizes the calendar configuration experience, improves usability, and provides access to new automation and AI-powered capabilities within the unified interface.

More details

Calendar settings mini page includes:

  • Synchronize calendar automatically checkbox. Out of the box, the checkbox is cleared. When selected, meaning that meetings from connected external calendar systems are synchronized with Creatio, and meetings created in Creatio are sent to external calendars.
  • Synchronization period field. Defines how often Creatio synchronizes calendar data.
  • Create AI meeting summaries from MS Teams transcriptions checkbox. Out of the box, the checkbox is cleared. When the checkbox is selected and a Microsoft Teams meeting is recorded, the meeting transcript is displayed on the Meeting summary tab of the meeting page and an AI-generated summary is created. Creatio automatically sends notifications using the "Notify meeting participants with summary via email" and "Deliver meeting summary email" business processes. Email notifications are sent only to internal participants with active Creatio user accounts and only for meetings that occurred on the current day. Users can be excluded from notifications via the lookup based on the "Meeting Summary Email Mute" (MeetingSummaryEmailMute code) object. Additionally, Creatio lets you disable email notifications globally or per user. The functionality is managed by the DisableEmailNotificationAIMeetingSummary additional feature. Out of the box, the feature is unregistered and disabled.

Productivity

Calendar section

Changed

Added automatic synchronization of Microsoft Teams meeting transcripts with calendar meetings. The functionality is enabled when calendar synchronization is configured and requires OAuth authorization for Microsoft 365. This change ensures that meeting transcripts are consistently imported and available for further AI processing.

More details

The synchronization interval is defined by the "Mailbox synchronization interval" (MailboxSyncIntervalCreatio code) system setting. Out of the box, the value is set to "15." When a meeting is saved and a transcript is available, the "Generate AI meeting summary from transcript" business process is triggered automatically. The process uses the "TranscriptChunkAnalysis" and "Summary composer" AI Skills to generate a structured meeting summary. The summary is stored in the "Meeting summary" (MeetingSummary code) object and displayed on the Meeting summary tab of the meeting page.

Knowledge Management

Knowledge base section

Fixed

Fixed an issue where external users could see all historical versions of knowledge base articles due to incorrect filtering logic. Previously, the "Parent article" (ParentArticle code) column of the "Knowledge base article" (KnowledgeBase code) object was unavailable for external users, which caused outdated versions to be displayed. This change ensures that external users see only the latest published version of an article, improving content accuracy and relevance.

Creatio.ai Knowledge Library

Creatio.ai knowledge library section

Added

Added a new Creatio.ai Knowledge Library composable app to enable configuration and management of knowledge sources used in retrieval-augmented generation (RAG) scenarios. The app is available on the Creatio Marketplace and includes a dedicated Creatio.ai knowledge library section, displayed in the "AI command center" workplace. It supports knowledge sources based on uploaded text-based files and *.pdf files, as well as structured data from Creatio sections. Transfer-layer chunking is applied to large knowledge items before sending them to the RAG microservice. Role-based access control filtering ensures that only records accessible to the current user are included in responses. Citation metadata is attached to results, enabling display of source references in Creatio.ai responses. This change enables secure and transparent RAG-based knowledge retrieval, improves governance and traceability of Creatio.ai responses, enhances microservice communication stability, and expands usage scenarios by supporting both structured and unstructured knowledge sources.

More details

The Creatio.ai knowledge library page includes the General information tab. Its content depends on the value of the Provider field:

  • If Provider is set to "File Provider," the tab includes the Attachments expanded list to upload files that are indexed and used as unstructured knowledge sources for retrieval.
  • If Provider is set to "Section Provider," the tab includes the Section field to select a Creatio section whose records are used as a structured knowledge source, and the Included columns expanded list to define which columns participate in knowledge indexing and retrieval.

After saving the knowledge source:

  • The Indexing tab becomes available on the Creatio.ai knowledge library page.
  • The Knowledge sources tab becomes available on agent and skill pages to allow linking configured knowledge sources to agents and skills.

Added the following system settings:

  • "Knowledge Service URL" (KnowledgeServiceUrl code) that specifies the base URL of the external microservice used for document retrieval and RAG processing. Out of the box, the value is empty.
  • "Knowledge Indexing Batch Size" (KnowledgeIndexingBatchSize code) that specifies the number of records processed per batch during knowledge source indexing. Out of the box, the value is set to "250."

Creatio Marketing

Campaign Designer

Changed

Added support for saving campaign workflows as reusable templates in the Campaign Designer. Users can save any existing campaign workflow as a named template and apply it when creating or editing campaigns whose "Status" column is set to "Planned." Applying a template adds all elements, connections, branches, and settings exactly as saved, except for links to related records such as bulk emails, events, and Facebook forms. If a campaign already contains a configured flow, Creatio displays a confirmation message before replacing it. If the replacement is confirmed, the existing campaign elements in the schema are removed, and the applied template is displayed instead. This change reduces manual setup, ensures consistency across marketing automation scenarios, and enables faster campaign creation.

Creatio Marketing

Campaign Designer

Changed

Added grouping of campaign elements in the Campaign Designer to organize the Elements area by functional intent. Elements are now displayed in logical groups that contain icons and titles, such as "Triggered entry," "Data management," "Flow logic," and "Outcomes," instead of a flat list. Additionally, implemented a dedicated API to define custom element groups, control group and element order, and assign elements to multiple groups, while custom elements remain ungrouped by default. This change improves navigation and element discovery, reduces time spent searching for elements, and increases efficiency when designing and updating campaign flows.

Creatio Marketing

Campaign Designer

Changed

Hidden the deprecated Add from landing and Landing page elements in the Elements area of the Campaign Designer to prevent using legacy web-to-object landing pages in new campaigns. These elements are replaced by the Add from web page and Web page elements for webhook-based landing page integration, including Creatio landing pages. Visibility of the Add from landing element is managed by the CampaignStartLandingElement additional feature, and visibility of the Landing page element is managed by the EnableOldCampaignLandingElement additional feature. Out of the box, both features are registered and disabled. The update affects only newly created campaign flows, while existing flows remain unchanged after upgrading to version 8.3.3. This change reduces the risk of using deprecated functionality, improves clarity of the Campaign Designer interface, and supports a smooth transition to the current landing page integration model without breaking existing campaigns.

Creatio Marketing

Campaign Designer

Fixed

Fixed the campaign schema copy behavior in the Campaign Designer. Previously, when copying a campaign that contained parallel or overlapping flows with custom positioning, all flows in the copied schema were placed on the same horizontal line, which distorted the original layout on the Campaign flow tab of the campaign page. The platform now preserves the relative positioning of campaign sequence flows when duplicating a campaign. This change ensures that the copied campaign schema matches the source layout and maintains visual consistency and correct campaign design after duplication.

Lead Generation

Landing Page Designer

Changed

Added configurable conditional rules for Form elements in the Landing Page Designer. Previously, form behavior could only be configured statically and could not respond dynamically to user input. Conditional rules are saved as part of the form configuration and injected into the landing page during publish or download. This change enables more flexible and advanced form behavior, reduces manual configuration effort, and allows marketers to implement more precise and dynamic landing page scenarios.

More details

Conditional rules support defining "IF" conditions and "THEN" actions, including:

  • logical "AND" and "OR" operators
  • grouping conditions in the "IF" block
  • applying actions in the "THEN" block. Out of the box, fields targeted by a "Show fields" action are hidden, while fields targeted by a "Hide fields" action are visible. "Set values" actions allow assigning static values compatible with the target field type to one or multiple fields. Default field values are replaced only after rule execution. When conditions change from "true" to "false," previously set values are preserved. "Set values" actions can be combined with visibility rules without conflict
  • operators such as "is filled in," "is not filled in," "equals," and "not equals"

Rules are evaluated in real time as visitors interact with a published landing page, either on the Creatio pre-configured URL or when using downloaded HTML. Conditional rules do not apply in the preview mode in the Landing Page Designer. Rules are executed in a top-to-bottom priority order and are stored as part of the form configuration, then copied together with the landing page to simplify reuse and duplication of forms across different scenarios.

Conditional rules cannot be configured for fields marked as hidden in the form field settings. Such fields are intended for contextual data storage such as source, channel, or UTM parameters, and are excluded from dynamic behavior.

When conditional rules are modified after a landing page is published, the landing page requires an explicit update initiated by a user to apply changes.

Lead Generation

Landing Page Designer

Changed

Added a placeholder option for "Dropdown" type fields in Form elements of the Landing Page Designer. Previously, "Dropdown" type fields always contained a selected value, which made it difficult to distinguish between values intentionally selected by users and fields left with a default value. "Dropdown" type fields now display an explicit "Select a value" placeholder to indicate that no value has been selected. When any other value is chosen, the field is treated as intentionally filled out by the user. The placeholder text can be localized in the Edit field mini page and is hidden when a default value is configured or when the field is required. This change improves the accuracy of form logic and reduces ambiguity in form submissions.

Lead Generation

Landing Page Designer

Fixed

Fixed an issue where field-level settings in Form elements were reset after adding a new field in the Landing Page Designer. Previously, when users configured field properties such as Required or Read-only in the Edit field mini page, these settings were lost after reopening the Form settings mini page and adding another field. The platform now preserves existing field configurations when forms are modified, preventing unintended resets and ensuring consistent form behavior for end users.

Lead Generation

Landing Page Designer

Fixed

Fixed an issue where removed default field values in forms were still displayed on the published landing page after republishing. Changes to default field values are now applied correctly after republishing a landing page, preventing outdated data from being submitted and ensuring predictable form behavior for users.

Lead Generation

Landing Page Designer

Fixed

Fixed an issue where default field values in forms were not copied when duplicating a landing page. Previously, duplicated landing pages did not retain default values configured in the original form. Default field values are now copied correctly together with the landing page, ensuring consistent form configuration and reducing the need to reconfigure forms manually after duplication.

Lead Generation

Landing page

Changed

Changed the logic of the Update button visibility for landing pages. The Update button is now always displayed on published landing pages and no longer depends on detecting changes in page HTML or scripts. This lets users reliably publish updates related to form configuration, conditional rules, scripts, and settings even when no markup changes are present. The change improves consistency of the landing page lifecycle, prevents missed updates, and reduces operational friction when managing landing page configurations.

Lead Generation

Landing page

Changed

Added the Add script tab for managing custom scripts directly from the landing page in Creatio. The tab lets users inject, edit, preview, and remove scripts without manual markup changes, define a script name and content, select the execution position ("Body bottom," "Body top," "Head bottom," "Head top"), and use a visual code editor for script injection. Script changes are applied after page publishing or download and support safe removal with a confirmation step. Using custom scripts, users can implement advanced landing page customization scenarios, including analytics and tracking integration (for example, Google Tag Manager), cookie consent solutions (for example, Cookiebot), Google reCAPTCHA v2/v3 for form protection, and custom form submission behavior such as adding additional parameters, validations, redirects, or tracking logic. This change allows customizing success and error messages and fully overriding post-submit behavior through custom success and error handlers.

Email marketing

Email Designer

Changed

Added validation for the Sender email address field on the Design content tab in the Email Designer. A warning message is displayed when the sender domain is not validated. This change enables users to identify unapproved domains before saving and helps ensure that only validated domains are used for outgoing emails.

Email marketing

Email Designer

Changed

Added the ability to duplicate a configured condition using the new Copy action in the list of row actions in the Display conditions mini page of the Email Designer. Previously, users could only create a condition from scratch. This change reduces manual configuration effort and ensures consistency when similar conditions are required.

Email marketing

Email Designer (Classic UI)

Changed

Added content alignment options to the Email Designer in Classic UI. Previously, email template content could not be aligned, which limited layout customization and visual consistency. Users can now align template content to the left, center, or right when designing message templates, emails used in business processes, and bulk emails. This change improves layout control, simplifies the email design process, and enhances the visual presentation of email content.

Email marketing

Sender domains section

Changed

Added the ability to remove configured sender domains using the new Delete action in the list of row actions in the Sender domains section. Previously, users could not remove outdated or incorrect domains directly from the list. This change enhances sender domain management and ensures the list of approved domains remains accurate and up to date.

Event management

Event page

Fixed

Fixed an issue where widgets on the event page did not filter data based on the current page context. Previously, the "Confirmed," "Participated," and "Not participated" widgets could display incorrect data because the Apply filter by page data parameter was not configured in the Freedom UI Designer and was therefore not applied during filtering. Widgets now correctly use the page context for filtering, ensuring accurate data display and improving the reliability of event participation insights.

Creatio Sales

Sales home page

Changed

Replaced the existing Sales homepage with a new Sales home page that includes structured analytics views and a unified period filter. Previously, the Sales homepage did not provide tab-based analytics with a unified period filter applied across all tabs. This change consolidates sales analytics into organized views to improve performance monitoring and operational control.

More details

The Sales home page includes the following elements:

  • Sales performance tab
  • Lead management tab
  • Team productivity tab
  • period filter that supports "Yearly," "Quarterly," "Monthly," and "Weekly" views. Out of the box, the value is set to "Quarterly." To configure custom period views in the Freedom UI Designer, modify the tab list and use the Chart settings parameter to apply filtering to widgets based on the selected tab. The selected period applies to all tabs across the page.

Creatio Sales

Sales home page

Changed

Changed the data selection logic of the Team productivity tab on the Sales home page to display activity metrics only for owners who have at least one opportunity or lead that matches the tab context. Previously, owners without opportunities or leads were included in activity aggregation, which could distort totals and comparisons. Owners without related sales records are now excluded from aggregation and from all widgets on the tab. This change improves consistency of team activity analytics.

Creatio Sales

Workplaces

Changed

Added the Territory management section to the "Sales" workplace when the Territory Management composable app is installed. Previously, this section was available only in the "Territory management" workplace and was not included in existing workplaces out of the box, even after installing the app. This change simplifies setup and reduces the risk of configuration inconsistencies.

More details
  • Added the CrtTerritoryMgmtInSales smart activation package to the Territory Management composable app. The package depends on CrtTerritoryManagementApp and SalesEnterprise packages.
  • Added the CrtTerritoryMgmtInSales dependent package to the SalesEnterprise package.

Lead and Opportunity Management

Lead page

Changed

Added a new "Sales motion" (SalesMotion code) column of the "Lookup" type to the "Lead" (Lead code) object to classify leads by sales motion type. The "Sales motion" attribute is available in the Data model attributes group of the Freedom UI Designer element library for the Leads form page and Leads mini page. The "Sales motion" column includes initial "B2B" and "B2C" values from the new Sales motion lookup. Previously, there was no dedicated field to classify leads by sales motion. This change improves lead classification consistency and enables filtering, segmentation, business rules, analytics, and process automation based on sales motion type.

Freedom UI components

Next steps component

Changed

Added the ability to filter task types in the Next steps component. Previously, tasks were displayed without type-based filtering, which could make task management less structured and increase interface clutter. Users can now filter tasks by type to better organize their workload. The functionality is managed by the NextStepTypeFilter additional feature. Out of the box, the feature is unregistered and disabled. When enabled, available filter categories can be configured in the Next step types lookup. This change improves task visibility and enhances usability of the Next steps component.

Territory Management

Territory management section

Changed

Added search functionality to the Hierarchy component in the Territory management section. Users can search for territories by full or partial name using a search field at the top of the hierarchy. The search is executed when the user presses Enter and displays matching territories along with their full hierarchical path. Child nodes are included in the results only if their names match the search query. If a parent territory matches but its children do not, the search stops at the parent level and the full subtree becomes visible only after clearing the search query. The search follows the same logic as the folder search mechanism. This change improves navigation in complex territory structures, reduces manual scrolling, and helps users quickly locate relevant territories while preserving performance and visual clarity.

Territory Management

Territory management section

Changed

Changed the out-of-the-box territory hierarchy in the Territory management section after initial installation. The default set of territories and hierarchy structure were revised to better demonstrate territory segmentation and configuration capabilities. Previously, the out-of-the-box setup did not fully reflect typical business scenarios or showcase application functionality. This change improves the initial user experience and makes the default configuration more representative of real-world territory management structures.

Territory Management

Territory management section

Changed

Changed the Territory management section to align visibility and action menu configuration with expected UX standards. This change improves data visibility and usability of import and export actions.

More details
  • Fixed the behavior of the Data import action.
  • Replaced the Actions button with the btn_actions_in_freedom_ui_designer.png button that includes separate Export to Excel and Data import actions with icons.

Territory Management

Territory management section

Fixed

Fixed the action menu behavior of the List component in the Territory management section and on the Accounts & connections tab of the territory page. Previously, the action menu was displayed at the bottom of the page and was not sticky, limiting access to bulk actions while scrolling. It is now displayed as a sticky element on the screen, consistent with the behavior in the Accounts & connections section. This change ensures consistent list behavior and improves usability when performing bulk actions.

Territory Management

Territory management section

Fixed

Fixed the calculation logic of the "Rep territories," "Open opportunities," and "Open pipeline" columns in the Territory management section. The aggregation logic now traverses the full territory hierarchy and includes data from all descendant territories. Previously, nested territories were not fully included in the aggregation, which could result in incomplete totals. This change ensures accurate territory-level reporting and consistent aggregation of pipeline and opportunity data across hierarchical structures.

More details
  • The "Rep territories" column counts descendant "Territory" type territories across the hierarchy.
  • The "Open opportunities" column counts open opportunities assigned to the territory and all descendant territories.
  • The "Open pipeline" column sums "Opportunity amount" values from the Opportunities expanded list on the Accounts & connections tab of the territory page for accounts in the territory and its descendant territories.

Territory Management

Territory page

Changed

Changed the territory page to align visibility, labels, layout order, and expanded list behavior with expected UX standards. This change improves layout consistency and data visibility.

More details
  • Hid the Regional info compact profile.
  • Renamed the Contact info profile to Owner info.
  • Reordered expanded lists on the Accounts & connections tab so that Opportunities are displayed before Leads.
  • Limited the Accounts expanded list capacity on the Accounts & connections tab to 10 rows before scrolling.

Territory Management

Territory page

Changed

Changed the Accounts, Opportunities, and Leads expanded lists on the Accounts & connections tab of the territory page to support hierarchical browsing of related records in the expanded lists. Users can now browse related records by parent directly within the territory page. Previously, hierarchical navigation was not available in these lists and required manual filtering to explore related records. This change simplifies navigation across territory-related hierarchies and reduces manual steps when working with parent-child relationships.

Customer 360,
Lead and Opportunity Management,
Territory Management

Accounts section,
Leads section,
Opportunities section,
Territory page

Changed

Added the "Territory" column to the record selection windows used when adding or selecting related records in the Accounts, Opportunities, and Leads sections, as well as on the Connections tab of the territory page. Previously, users selected records without visibility of territory information, which could lead to incorrect assignment or reassignment decisions. This change improves assignment accuracy, reduces reassignment errors, and enables faster territory-aware selection.

Creatio Service

Contact Center

Added

Added a new Contact Center composable app that enables agents to manage real-time chat communications, including chats and calls as well as queued tasks such as cases, orders, or custom entities, from centralized workplaces. The app is available on the Creatio Marketplace. Telephony and chat functionality remains available at no additional cost within Creatio Service and Creatio Financial Services CRM under the existing licensing model. This change clarifies product boundaries and aligns communication capabilities with operational usage.

Contact Center

Agent Inbox panel

Added

Added support for real-time chat items in the Agent Inbox panel. The panel displays queued chat communications using the new crt.MultiList component and organizes them into New items (chats in the "Waiting for response" status) and In progress (chats currently handled by the agent in the "In progress" status) lists with item counters. The component is not available in the Freedom UI Designer element library and can be configured using low-code tools only. The lists are independently scrollable, dynamically respond to available panel space, and are limited to a maximum of 50% of the panel height each. Chat visibility and distribution follow standard queue routing rules and are managed by the "Simultaneous Chats" (SimultaneousChats code) system setting. Out of the box, the value is set to "5." This change improves visibility of incoming chat workload and helps agents manage active and queued conversations more efficiently.

Contact Center

Agent Inbox panel

Added

Added an unread message indicator in the Agent Inbox panel. Previously, this functionality was available in Classic UI only. This change ensures consistent agent workflows in Freedom UI, improves visibility of unread conversations, and helps agents prioritize active chats without losing context.

More details

The unread counter is displayed for chats that have new messages, updates in real time as new messages arrive, and decreases automatically as messages become visible while the agent scrolls through the conversation. When the unread count exceeds 9 messages, the indicator is displayed as "9+."

Contact Center

Agent Inbox panel

Added

Added a real-time overdue timer indicator to chat tiles in the Agent Inbox panel. The timer appears when configured response time thresholds are exceeded and updates live to show how long a chat has been overdue since the last incoming customer message. The functionality supports both first response and ongoing response scenarios, displays only the relevant timer based on the chat state, and resets once the agent replies. Queue-specific response time limits are configured on the Chat queues expanded list on the Chat settings page. This change helps agents prioritize overdue conversations, improves response-time visibility, and supports consistent service-level management across chat queues.

Contact Center

Agent Inbox panel

Added

Added the ability to view key contact and chat details directly from the chat header in the Agent Inbox panel. Previously, this functionality was available in Classic UI only. This change ensures consistent agent workflows in Freedom UI, helps agents quickly access relevant customer information during conversations, and provides greater flexibility for adapting the contact profile to specific business needs.

More details

The header displays the contact icon and name along with the associated channel, and provides a collapsible contact profile panel that shows populated contact fields such as Email and Business phone, and chat fields such as Chat channel. Selecting the contact name opens the contact page in the workspace. The contact profile can be extended with additional fields using low-code tools.

Contact Center

Agent Inbox panel

Added

Added the ability to link an active chat to an existing contact directly from the contact profile panel in the Agent Inbox panel. This change improves data accuracy, ensures correct customer identity association for chat history, and helps eliminate duplicate or temporary contact records.

More details

Agents can use the Link to another contact button to select a different contact from the Select: Contact mini page and confirm the reassignment. After confirmation, the chat is linked to the selected contact, the previous contact record is removed, and changes are applied immediately in the contact profile and chat messages without page reload.

Contact Center

Agent Inbox panel

Added

Added support for composing and sending text messages in active chat sessions directly from the Agent Inbox panel. Agents can send messages using the btn_send_message.png button or by pressing Enter. Typed messages are saved as drafts until they are sent, preventing content loss between interactions. This change enables agents to communicate with customers directly from the inbox while preserving message content during navigation and interaction.

Contact Center

Agent Inbox panel

Added

Added the ability to attach and send images and files in active chat sessions from the Agent Inbox panel. This change enables agents to share documents and images directly in chat conversations while enforcing file security rules and platform limitations.

More details

Agents can upload attachments using the btn_upload_file.png button, dragging, or paste images via Ctrl+V. Attachments can be removed before sending using the btn_delete.png button.

Attachments are previewed before sending: files display the name (with ellipsis truncation when needed) and a file-type icon, while images are shown as thumbnails. Multiple attachments support horizontal scrolling. Each file or image is sent as a separate message. If both text and attachments are included, they are sent as individual messages.

File type restrictions are managed by the "File extensions DenyList" (FileExtensionsDenyList code) system setting and messenger-specific rules, including Telegram, WhatsApp, and Facebook. File size limits are managed by the "Attachment max size" (MaxFileSize code) system setting and individual messenger platform limitations. Out of the box, the value is set to "10," in megabytes. If the limit is exceeded, Creatio displays a detailed error message.

Contact Center

Agent Inbox panel

Added

Added support for selecting and inserting predefined message templates in active chat sessions from the Agent Inbox panel. Previously, this functionality was available in Classic UI only. This change ensures consistent agent workflows in Freedom UI, helps agents respond faster with consistent, localized messages and reduces manual input during live chat conversations.

More details

Agents can open the template list using btn_open_templates.png button in the chat input or by typing the "//." The list displays templates from the Message templates section and supports search by name or body text. Inserted template content is localized based on the language specified in the Preferred language field on the Contact info tab of the contact page or the chat language, and macros are populated automatically using data from the current chat context and related records. Missing macro values are inserted as plain text.

Contact Center

Agent Inbox panel

Added

Added grouping of message templates by usage in the Agent Inbox panel. This change helps agents quickly access frequently used responses, reduces time spent searching for templates, and improves efficiency when handling high chat volumes.

More details

Message templates are grouped as follows:

  • Recently used that displays up to five templates based on recent usage, sorted by frequency
  • Others that includes all remaining templates, sorted alphabetically

Contact Center

Agent Inbox panel

Added

Added support for inserting emojis into chat messages from the Agent Inbox panel. This change enables more expressive and natural communication with customers while maintaining a professional tone during chat interactions.

More details

Agents can open the emoji picker using btn_add_emoji.png button in the chat input, search emojis by name or shortcut, preview emojis with their names and shortcuts, and insert selected emojis directly into the message text.

Contact Center

Agent Inbox panel

Added

Added support for transferring active chat sessions to another agent or queue in the Agent Inbox panel. Previously, this functionality was available in Classic UI only. This change ensures consistent agent workflows in Freedom UI and enables seamless reassignment of conversations without losing context.

More details

Agents can initiate chat transfer from the chat header using btn_transfer_chat.png button and select a target queue or agent using corresponding tabs.

  • When transferring to a queue, Creatio displays available queues along with the number of available agents, and reassigns the chat according to standard queue routing rules.
  • When transferring to an agent, Creatio displays a deduplicated list of available agents with their current statuses and assigns the chat directly to the selected agent.

After transfer, the chat becomes read-only for the sending agent and is removed from the In progress list once deselected. The receiving agent or queue sees the chat with a detailed transfer message and unread message counter, while full conversation history and attachments remain available.

Contact Center

Agent Inbox panel

Added

Added support for running quick actions directly from active chat sessions in the Agent Inbox panel. Previously, this functionality was available in Classic UI only. This change ensures consistent agent workflows in Freedom UI, reduces context switching and enables agents to trigger relevant automation directly from conversations.

More details

Agents can use btn_run_action.png button in the chat header to launch predefined business processes configured on the Chat actions expanded list on the Chat settings page. When an action is selected, the linked process is started with contextual parameters from the current chat.

Contact Center

Agent Inbox panel

Added

Added support for real-time chat translation in the Agent Inbox panel. Previously, this functionality was available in Classic UI only. The functionality is managed by the "Enable chat translation" (EnableChatTranslation code) system setting. Out of the box, the value is set to "false." The functionality relies on Creatio.ai and uses AI Actions. This change enables seamless multilingual communication, improves agent experience, and helps agents handle chats across language barriers more efficiently.

More details

When the system setting value is set to "true":

  • The customer language is detected automatically at the start of a chat.
  • Incoming messages can be translated into the agent language.
  • Outgoing messages are translated into the customer language out of the box.
  • A detailed error message is displayed if language detection or translation fails.

Agents can:

  • Switch between original and translated versions of messages.
  • Control the visibility of the translation panel in the chat header using the btn_translate.png button. The tooltip changes between Hide translation panel and Show translation panel, depending on the current state of the translation panel.
  • Control automatic translation of outgoing messages using the btn_translate.png button. The tooltip changes between Disable auto-translation and Enable auto-translation, depending on the current state of the automatic translation.
  • Continue working with translated content when switching between chats.

Contact Center

Agent Inbox panel

Added

Added support for manual and automatic chat completion in the Agent Inbox panel. Previously, this functionality was available in Classic UI only. This change ensures consistent agent workflows in Freedom UI and allows resolved chats to be closed explicitly while preserving full conversation history.

More details

Agents can complete chat sessions using the Complete button, after which chats become read-only and are removed from the In progress list. Conversation history and attachments remain available in the panel until the chat is deselected, and system messages confirm chat completion. Automatic chat completion by timeout follows the same behavior.

Creatio Service

Feedback page

Fixed

Fixed an issue on PostgreSQL where opening a feedback page that includes a customer satisfaction score from an email caused the page to fail during the GetSatisfactionLevel request, preventing the EstimationWithIcons component from loading. This change restores reliable feedback page loading and enables customers to submit and view their satisfaction estimation directly from the feedback page.

Case Management

Cases section

Fixed

Fixed an issue where the required EntityConnection data binding was missing in the Case Management app, causing email linking based on a thread to fail. Previously, this dependency was available only in Creatio Service, and environments with only the Case Management app installed could not link cases by ConversationId, resulting in inconsistent behavior. Now, the required data binding is included and the configuration is aligned with the Creatio Service implementation. This change restores end-to-end email thread linking functionality and ensures consistent behavior across apps.

Case Management

Cases section

Fixed

Fixed an issue where cases in the "Waiting for response" or "Resolved" stage were not automatically reopened when a follow-up email was received in the Case Management app. Previously, the required reopen logic was missing, which prevented incoming emails referencing a resolved case from triggering the transition to "Reopened." The issue occurred environments without the Creatio Service product. The functionality is now managed by the "Run process: Reopen case and notify assignee on receiving an answer regarding the case V2" business process. The previous "Run process: Reopen case and notify assignee on receiving an answer regarding the case" process was deactivated. This change restores automatic case reopening on follow-up emails and ensures continuity of customer communication workflows.

Case Management

Message templates

Fixed

Fixed an issue where message templates from Creatio Service were not available in the message composer after installing the Case Management app in Creatio Studio. Although the templates existed in the platform, they were not returned in the selector due to missing TemplateTypeId values. The data bindings were updated to populate the TemplateTypeId field, and Creatio now detects and corrects templates with empty TemplateTypeId values so they appear in the template list. Previously, templates that have an empty TemplateTypeId were filtered out and unavailable for selection. This change restores expected template visibility and ensures consistent template behavior in the Case Management app.

Creatio Mobile

Category

Feature

Status

Description

No-code customization

Freedom UI Mobile Designer

Changed

Added the ability to switch the canvas between phone, tablet landscape, and tablet portrait views directly in the Freedom UI Mobile Designer. The view switcher is displayed near the page title. When a mode is selected, the corresponding canvas configuration is applied immediately without a page reload, updating canvas proportions and styling to match the selected device type. Previously, no-code creators could work with only a single canvas setup and could not quickly validate or adjust layout behavior for different device form factors. This change simplifies responsive layout validation, improves cross-device consistency, reduces rework, and increases efficiency when designing pages for mobile and tablet experiences.

Freedom UI Mobile components

Button component

Changed

Added the "Open NFC reader" action for the Button component in the Freedom UI Mobile Designer. At runtime, tapping the configured button opens the device NFC reader. This change simplifies implementation of NFC-based scenarios and enables hardware interaction in mobile apps without requiring custom code.

Freedom UI Mobile components

Folder management component

Changed

Added support for the Folder management component in the Freedom UI Mobile Designer. The component now provides canvas preview rendering and a limited set of configuration parameters in the setup area. The configuration behavior is aligned with mobile runtime capabilities. This change extends mobile page design capabilities and ensures consistent folder configuration behavior without requiring custom code.

Freedom UI Mobile components

List component

Changed

Changed vertical paddings for List component items in Creatio Mobile. This change affects all Freedom UI sections and provides consistent vertical spacing across list views. Full-screen lists remain unchanged.

Freedom UI Mobile components

List component

Changed

Added the Sort by column parameter to the setup area of the List component in the Freedom UI Mobile Designer. Users can now select a default object column for sorting and specify the sorting direction using the btn_sort_direction_asc.png / btn_sort_direction_desc.png buttons. The button changes depending on the current sorting state. The sorting configuration is stored in the list metadata and applied automatically when the list is opened in the Creatio Mobile app. This change ensures consistent data ordering and improves usability of mobile lists.

Freedom UI Mobile components

List component

Changed

Added support for record management actions in embedded list on mobile pages. The List component now enables users to edit and delete records directly within the mobile app. This change reduces the number of steps required to maintain list data and improves usability of mobile pages that use embedded lists.

Freedom UI Mobile components

Feed component

Changed

Added support for the Feed component in the Freedom UI Mobile Designer. The component now provides canvas preview rendering and a limited set of configuration parameters in the setup area. This change extends mobile page design capabilities and ensures consistent activity tracking.

Freedom UI components

Attachments component,
Feed component

Changed

Added file preview support in the Attachments and Feed components, allowing users to preview files directly without downloading them. Files now open in a mini page that allows interaction with the document content. Users can zoom in and out, navigate between pages with visual indicators, and perform key actions such as downloading the file as a PDF, printing it, or switching to full-screen mode. A navigation pane in the top left displays all document pages, while a search tool in the top right enables in-document search. The preview supports the following file types: *.pdf, *.xlsx, *.docx, *.pptx, *.jpeg, *.png, *.gif. Files in other formats remain available for download only. Additionally, a dedicated download button was added to file tiles in the Attachments and Feed components to simplify file management and make download actions more accessible. This change eliminates the need to download files for viewing, improving efficiency and user experience by enabling faster access to file content directly within the UI.

Freedom UI Mobile components

Communication options component

Changed

Added support for the Communication options component in the Freedom UI Mobile Designer. The component provides canvas preview rendering and a limited set of configuration parameters in the setup area. Out of the box, it includes Phone number, Email address, and Web link fields, as well as a predefined btn_add.png button. At runtime, users can add and edit communication options, selecting types such as "Email," "Phone," "Social network," "Web," or "Skype," with immediate validation and data persistence. This change extends mobile page design capabilities and ensures consistent communication data handling.

Freedom UI Mobile components

Account compact profile component,
Contact compact profile component

Fixed

Fixed an issue where fields in the Account compact profile and Contact compact profile components could not be edited correctly in Creatio Mobile. Previously, changes made in the compact profiles were not applied as expected. This change restores proper editing behavior and ensures changes are saved correctly.

Freedom UI Mobile components

Timeline component

Changed

Added support for the Timeline component in the Freedom UI Mobile Designer. The component now provides canvas preview rendering, including object or skeleton display depending on data source selection, and a limited set of configuration parameters in the setup area that vary based on the selected timeline object. The configuration behavior is aligned with mobile runtime capabilities. This change extends mobile page design capabilities and ensures consistent timeline behavior while preserving supported mobile functionality.

Freedom UI Mobile components

Sort component

Changed

Added support for the Sort component in the Freedom UI Mobile Designer. The component now provides canvas preview rendering and a limited set of configuration parameters in the setup area. The configuration behavior is aligned with mobile runtime capabilities. This change extends mobile page design capabilities and ensures consistent sorting behavior without requiring custom code.

Freedom UI Mobile components

Embedded list component

Changed

Removed default horizontal paddings for Embedded list component items in Creatio Mobile. This change affects only newly created Freedom UI sections and provides consistent horizontal spacing across list views.

Freedom UI Mobile components

Progress bar component

Changed

Added support for the Progress bar component that displays dynamic case stages in Creatio Mobile apps. The component visualizes the process flow using labeled, color-coded stages, highlights the current stage and status, supports grouped stages, role-based restrictions, and horizontal scrolling for scenarios that have multiple stages, and adapts to different dynamic case configurations. The component reflects dynamic case stage changes dynamically and handles missing stage or filter configuration gracefully. The functionality is managed by the UseMobileProgressBarComponent additional feature. Out of the box, the feature is registered and enabled. Previously, the feature was under beta testing.

Freedom UI Mobile components

Progress bar component

Changed

Added versioning of "Case" type schemas that implement dynamic cases in the Progress bar component for records of the same object. The platform now determines the applicable dynamic case version based on the ModifiedOn property value and caches the resolved version per record. This prevents unexpected changes in the progress bar when the ModifiedOn value is updated and ensures consistent case lifecycle behavior when multiple schema versions exist.

Freedom UI Mobile components

IFrame component

Fixed

Fixed an issue where file uploads were not supported for external apps embedded in a Creatio Mobile page using the IFrame component. Previously, when an embedded page used a standard HTML <input type="file" /> element, tapping it did not open the file selector dialog, even though the same page worked correctly when opened directly in a browser. File selection is now handled via the androidController.setOnShowFileSelector() method. This change enables file uploads from embedded apps within Creatio Mobile.

Freedom UI Mobile layout elements

Area element,
1 column element

Changed

Added support for structured row and column layout configuration in the setup area of the Freedom UI Mobile Designer. It provides canvas preview render as well as structured row and column configuration, enabling responsive layout composition. The layout responds to supported phone and tablet views to ensure proper alignment and content distribution. This change extends mobile page design capabilities and enables consistent, structured layout design in mobile apps.

Fields and inputs

"Image" type field

Fixed

Fixed an issue where the "Image" type field at runtime expanded to fill all available space within a Flex row layout element in Creatio Mobile, preventing other components from appearing in the same row. Now, the layout configuration has been updated so that the field no longer reserves the remaining horizontal space out of the box. This change enables placing additional components in the same row and improves mobile page layout flexibility.

Data models

Database management

Changed

Added support for Microsoft SQL Server in the .NET 8-based version of Creatio Studio. This change expands database compatibility options.

UX

Page management

Fixed

Fixed an issue where dynamic links to sections not available in the Creatio Mobile app did not open correctly. The platform now checks module availability and opens the link in a browser if the target section is not supported in the mobile app. This change ensures consistent navigation behavior and prevents broken links in mobile scenarios.

UX

User profile

Fixed

Fixed an issue with applying the Date & time format parameter from the Basic settings tab of the user profile page in the Creatio Mobile app. Previously, dates were formatted based on the Language parameter on the same tab, so date values followed the language format even when a different date format was selected in the user profile page. Creatio Mobile now formats dates according to the selected parameter, allowing users to see dates in the expected format, for example, "DD/MM/YYYY" for "en-GB," and ensuring consistent date formatting across the app.

Communication

Notifications

Changed

Changed the Notifications section in Creatio Mobile. Previously, notification tiles displayed only the main message content. Now, notification tiles display the date and time of creation, and their visual style is aligned with current mobile UI standards. The interaction model and navigation remain unchanged. This change improves readability, provides clearer context for received notifications, and ensures consistent mobile interface design.

Beta testing of new features

Category

Feature

Status

Description

AI and automation

Workflow AI Agents

Added

Added the ability to build Workflow AI Agents. Previously, AI Agents were implemented primarily as prompt-based agents, where execution logic was embedded in a single large prompt, limiting deterministic orchestration of mandatory steps. Workflow AI Agents run as orchestrated workflows that combine AI Skills with standard business process elements. This approach enables more structured, step-by-step execution to improve response correctness and reduce hallucinations, ensure reliable and predictable behavior (including enforcement of mandatory steps), and support multi-step workflows with deep integration into the Creatio.ai chat experience. Deterministic logic is handled directly within the workflow, which can reduce action consumption compared to prompt-based agents by moving predictable steps out of prompts and into workflow elements. The functionality is managed by the GenAIFeatures.UseAgenticProcesses additional feature. Out of the box, the feature is registered and disabled. This change expands agent-building capabilities and provides greater control, transparency, and efficiency for complex AI-driven scenarios.

More details

When the feature is enabled, the skill page includes additional expanded lists and checkboxes that provide explicit control over execution context and available tools:

  • Capabilities enable selection of configurable mix-ins that enrich AI Skill execution by adding structured prompt context and instructions, execution guidance, and a related set of bundled tools. Unlike prompt agents, where built-in behavior is implicitly available, workflow AI Skills require explicit capability selection. If a capability is not added, the skill cannot access the associated context or tools. Capabilities also support enabling user messaging, allowing a workflow step to request clarification and continue execution in a human-in-the-loop scenario.
  • Action list defines the explicit set of tools available to the skill during execution. The lists of capabilities and actions complement each other: capabilities can provide bundled tools and contextual guidance, while additional standalone actions can be configured independently.
  • Use page context determines whether to inject the current page context when the agent starts. Out of the box, the checkbox is cleared for existing workflow AI Skills and selected for new workflow AI Skills.
  • Use chat history determines whether to inject prior conversation messages into the skill execution context. Out of the box, the checkbox is cleared for existing workflow AI Skills and selected for new workflow AI Skills.

These parameters enable granular and transparent control over AI Skill behavior for Workflow AI Agents.

No-code customization

Translations

Changed

Added the ability to store data localizations in a package and view them in read-only mode for "Localization" type schemas using the Localization Designer. The functionality is managed by the PackageDataLocalizationManagement additional feature. Out of the box, the feature is registered and disabled. When enabled, the Localization Designer includes the Localizable data tab that displays data-level localizations included in a package. These localizations are installed into the target environment as part of the package installation. This change improves visibility of translated data and helps teams work more efficiently with multilingual packages.

No-code customization

Translations

Changed

Added support for automatic creation of "Localization" type schemas for data that includes translations in a package. When data localization is applied, for example, via the Translation section, the platform now generates corresponding "Localization" type schemas to ensure translated data is properly tracked and stored in the package, even if the data record itself is not bound to this package. The functionality is managed by the PackageDataLocalizationManagement additional feature. Out of the box, the feature is registered and disabled. This change enables consistent packaging and delivery of data-level translations, improves visibility and control over translated content, and enhances support for multilingual deployments alongside configuration-level localization.

No-code customization

Translations

Changed

Added the ability to control the target package for saving translations from the Translation section. The functionality is managed by the "Package to store translations" (PackageToStoreTranslations) system setting. Out of the box, the value is empty, and translations are saved to the current package. When a package is specified, translations for localizable values of configuration schemas and localizable data are saved to the defined package. The functionality availability is managed by the UsePackageForLocalizationsInApplyTranslation additional feature. Out of the box, the feature is registered and disabled. This change provides better control over localization storage and supports structured translation management in multi-package environments.

No-code customization

Translations

Changed

Added support for configuring Creatio behavior when data translation values exceed the database column length during package installation. The functionality is managed by the PackageFeatures.ApplyLocalizationAfterSchemaDataInstall additional feature. Out of the box, the feature is registered and disabled. When the feature is enabled, the behavior is managed by the "Translation exceeds the column length behavior" (TranslationLengthExceedBehavior code) system setting. Out of the box, the value is set to "Fail installation (strict)." In this case, the installation process is completed but ends with an error screen if such validation issues occur, and log files are available for download. Otherwise, if the value is set to "Ignore error (warn only)," the installation finishes successfully, and details about the ignored localization value length errors are recorded in the log files. This change provides administrators with flexible control over localization validation during deployments while preserving visibility into potential data integrity issues.

No-code customization

Sidebars

Changed

Added the ability to control the position of sidebars on the screen. The functionality is managed by the SidebarPanelPositionEnabled additional feature. Out of the box, the feature is unregistered and disabled, and all sidebars open on the right side of the screen. This change helps better utilize available space and improve usability when working with complex layouts. Some scenarios might not be fully supported yet.

More details

When the feature is enabled, Creatio lets you configure where sidebars open using the Panel position parameter in the Sidebar parameters mini page in the Freedom UI Designer. Available values: "Left side of the screen," "Right side of the screen."

Apps and packages

Package management

Changed

Enhanced the handling of custom data localizations during package installation and manual data binding installation or reinstallation. This allows delivering translations for data as part of packages using standard Creatio delivery processes. Custom localized values defined in the "Localization" type schema now take precedence over default localization values from original data bindings. The functionality is managed by the PackageFeatures.ApplyLocalizationAfterSchemaDataInstall additional feature. Out of the box, the feature is registered and disabled. This change prevents unintended overwriting of custom translations, improves control over multilingual deployments, and enhances the reliability of localization during package delivery and updates.

Freedom UI components

Hierarchy component

Changed

Added search functionality to the Hierarchy component. Users can search for items by full or partial name using the Search field at the top of the hierarchy. The search is executed when the user presses Enter and displays matching nodes along with their full hierarchical path. Child nodes are included in the results only if their names match the search query. If a parent node matches but its children do not, the search stops at the parent level, and the full subtree becomes visible only after clearing the search query. The search follows the same logic as the folder search mechanism. This change improves navigation in complex hierarchical structures, reduces manual scrolling, and helps users quickly locate relevant items while preserving performance and visual clarity. The functionality is managed by the ShowParentHierarchySearch additional feature. Out of the box, the feature is unregistered and disabled.

Analytics

Metric

Changed

Added the ability to configure custom formulas for metrics using the "Formula" option in the Function parameter of the Freedom UI Designer. Users can define calculated metrics using aggregation functions, arithmetic operations, and filters in the Formula Designer. The feature supports aggregation functions COUNT, SUM, AVG, MIN, and MAX for selected objects and columns, including both static filters and filters applied by page data. The configured formula is validated, calculated, and displayed at runtime. The functionality is managed by the EnableFormulaAggregationInDesigner additional feature. Out of the box, the feature is unregistered and disabled. This change extends metric configuration capabilities and enables flexible formula-based aggregation in dashboards without custom development.

Code-based customization

Module Designer

Changed

Added support for handwritten signature capture in Creatio Mobile. The functionality is implemented via the crt.OpenSignatureServiceRequest request that opens a dedicated signature screen and saves the captured signature as an image file attached to the specified record. The request supports configurable properties such as entityName, columnName, and recordId to define storage and binding behavior, and can be triggered from a page action configured in metadata. This change simplifies the implementation of signature collection in mobile scenarios and ensures signatures are stored as standard attachment files for further processing and audit.

Lead and Opportunity Management

Opportunities section

Changed

Added the Pipeline analytics filter to the Opportunities section. The Pipeline analytics include the Sales waterfall pipeline, implemented using a new sales waterfall widget that provides sales-specific pipeline visualization logic. The widget supports common interactions and visual behavior, including interactive drilldown by stage, fullscreen view, header interaction support, aggregated value labels on stages, and disabled legend, tooltip on hover, and Y-axis visibility. The widget includes Start and End metrics retrieved from the configured data source and displays them as the first and last values of the waterfall, with intermediate pipeline stages positioned between these metrics. This change introduces waterfall-based pipeline visualization in the Opportunities section and establishes consistent rendering and interaction behavior for sales pipeline analysis.