Skip to main content

8.3.4 Twin changelog

Release date:

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

For a comprehensive overview of the new features, refer to the 8.3.4 Twin release notes.

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

Creatio platform

AI and automation

Category

Feature

Description

Creatio.ai

AI Agents

Added a new Campaign Generation Agent that creates campaign workflows from natural language descriptions in the Creatio.ai chat panel. Based on the user's input, the agent analyzes the campaign goal, target audience, and expected engagement flow, selects suitable elements from the available library, suggests the campaign structure for user confirmation, and creates the campaign after approval. The agent also generates a campaign name, adds a campaign goal, forms the campaign flow, and returns a direct link to the created campaign. The agent is available in the Digital Ads, Lead Generation, Email Marketing, and Event management apps. This change reduces manual configuration effort, improves consistency of campaign setup, and accelerates time from idea to execution.

More details

The following limitations apply:

  • Campaign element parameters such as conditional flows in delays, filters, linked bulk emails, and landing pages are not configured by the agent and require manual adjustment.
  • The agent does not support complex branching flows with two or more parallel sequences.

Creatio.ai

AI Agents

Added a new Customer Support Agent that handles AI-driven conversations in customer SMS, WhatsApp, Telegram, Web chat, and Facebook Messenger chat channels. It is delivered as part of the Customer communication hub app available on the Creatio Marketplace and includes a predefined AI assistant personality. This change enables immediate AI-driven conversation handling in chat channels without the need to configure a custom AI Agent.

More details
  • "Customer Support Agent knowledge source" was added to the Knowledge sources expanded list on the Knowledge sources tab of the agent page. It was built based on the Knowledge base section.
  • The "ExternalChatAiUser" technical user was added to the Technical users section to control which AI capabilities are available in customer chat channels. The name and avatar of this technical user are displayed in the Chat info profile of the chat page in the Chats section. To enable an agent or sub-agent in a chat channel, add "ExternalChatAiUser" to the Permissions to execute expanded list on the General information tab of the agent or sub-agent page. Out of the box, the "ExternalChatAiUser" technical user is added to the Customer Support Agent page.

Creatio.ai

AI Agents

Added conversion of LLM-generated responses from Markdown to plain text for customer SMS, WhatsApp, Telegram, Web chat, and Facebook Messenger chat channels. It is delivered as part of the Customer communication hub app available on the Creatio Marketplace. This change ensures AI-generated messages are rendered in plain text across all supported customer chat channels, preventing formatting inconsistencies caused by Markdown syntax. The logic does not affect internal chat channels.

Creatio.ai

AI Agents

Added a standardized greeting behavior for the AI assistant's first message in SMS, WhatsApp, Telegram, Web chat, and Facebook Messenger chat channels. It is delivered as part of the Customer communication hub app available on the Creatio Marketplace. Previously, the AI assistant did not introduce itself at the start of a conversation, which could cause confusion about the identity of the responder. The logic applies only to customer SMS, WhatsApp, Telegram, Web chat, and Facebook Messenger chat channels and does not affect internal chat channels or non-AI messages. The greeting behavior is managed by the "AiChatPromptTemplate" (AiChatPromptTemplate code) object. This change ensures users receive a clear AI introduction at the start of every conversation, making it immediately apparent they are interacting with an AI assistant.

Creatio.ai

AI Agents

Changed the Productivity Agent instructions to define a structured instruction set for request handling and sub-agent selection. This change ensures more predictable and stable Productivity Agent behavior, reducing the risk of incorrect sub-agent selection when processing user requests.

Creatio.ai

AI Sub-agents

Renamed skills to sub-agents in Creatio, including all corresponding UI elements. Previously, the term "Skills" was used to describe AI sub-components, which did not fully reflect their role in the AI Agent architecture and differed from widely used industry terminology. This change improves clarity for users who configure and maintain AI-related logic and aligns Creatio.ai interfaces with industry-standard terminology.

Creatio.ai

AI Sub-agents

Fixed an issue where input parameters could not be added to workflow sub-agents. Previously, when a newly created sub-agent contained only basic metadata, for example, name, code, description, and prompt, adding an input parameter incorrectly enabled the Save button and failed on save with the error "Cannot read properties of undefined (reading 'InputParameters')." The parameter handling logic for the workflow-type sub-agents was updated. This change ensures that input parameters can be added and saved correctly regardless of the sub-agent's initial configuration state.

Creatio.ai

AI Agents,
AI Sub-agents

Added support for GPT-5.2 LLM in the Creatio.ai models section. This change gives users access to GPT-5.2 for selection in the Model field on agent and sub-agent pages, enabling more capable and up-to-date AI-driven experiences.

Creatio.ai

AI Agents,
AI Sub-agents

Changed the behavior of SourceCode type action on agent and sub-agent pages to prevent opening an empty Process Designer. Previously, SourceCode type actions used the default form page because no dedicated page was configured for this action type, causing a blank designer page to open. This change keeps SourceCode type actions visible in the list on agent and sub-agent pages while preventing them from being opened through an unsupported link.

Creatio.ai

AI Tools

Renamed AI Actions to AI Tools in Creatio, including all corresponding UI elements. This change reflects the updated terminology across the platform and ensures consistency in how AI-driven automation capabilities are referenced in the UI.

Creatio.ai

AI Tools

Changed the default value of the Use system security context for script tasks checkbox from selected to cleared on the tool page when creating new AI Tools. Out of the box, script tasks now run under the context of the user who executes the tool. The checkbox can still be selected manually when system context is required. Existing AI Tool behavior remains unchanged. This change improves security by ensuring AI Tool script tasks respect user-level permissions by default, reducing the risk of unintended privileged execution.

Creatio.ai

AI Tools

Fixed an issue where custom objects could not be found in the Process Designer on the Tool schema tab of the tool page when configuring AI Tool elements, for example, Read data. Previously, object selection worked correctly in the Process Designer, but custom objects were unavailable in the Process Designer used for AI Tool configuration, preventing their use in element setup. This change allows developers to select custom objects in the Process Designer when configuring AI Tool elements, the same way as in the standard Process Designer.

Creatio.ai

Creatio.ai chat panel

Fixed a crash in CopilotParametrizedActionResponseProvider caused by collection or composite parameters that do not contain nested parameters. This change prevents a NullReferenceException during action execution when collection-type or composite parameters with a flat structure are present, ensuring uninterrupted tool invocation in the Creatio.ai chat panel.

Creatio.ai

Creatio.ai chat panel

Fixed an issue where the confirmation message text was not displayed in long chats when an AI Tool requiring confirmation was invoked in the Creatio.ai chat panel. This change ensures that confirmation messages are rendered correctly regardless of chat length, improving the reliability and transparency of the tool confirmation flow.

No-code customization

Category

Feature

Description

No-code tools

Freedom UI Designer

Changed the layout and visual design of the action panel in the Freedom UI Designer. Previously, the action panel had a less structured layout with limited visual grouping, which made it harder to navigate and locate relevant actions. This change gives no-code creators a more structured and consistent view of actions in the designer, with related actions organized into clearer groups and updated button styles.

No-code tools

Freedom UI Designer

Fixed an issue in the Freedom UI Designer where changes to parameters of default timeline objects, such as "Feed channel" (SocialChannel code) and "File" (File code), were not saved when switching between objects. Previously, parameter changes were silently discarded due to form validation issues, leading to inconsistent configuration behavior in the designer. This change ensures that parameter changes to default timeline objects are saved correctly when switching between objects in the designer.

No-code tools

Freedom UI Designer

Fixed an issue where deleting the Timeline component in the Freedom UI Designer triggered duplicate deletion logic due to overlapping handling between parent and nested items.

More details
  • The redundant timeline deletion call triggered when the last object is removed was eliminated.
  • The interaction between RemoveViewItemCommand and the timeline internal logic was adjusted.
  • The timeline now retains other child components such as Message composer and Quick filter when the last object is deleted.

UI Design

Freedom UI components

Fixed an issue where the quantity counter in section lists showed a different value than the number of records displayed for the same filters. Previously, the list and count queries were generated using different SQL logic for filters on joined tables, so the counter could return an incorrect total, even though the list displayed the correct records.

Localization

Localization Designer

Fixed an issue where the btn_back.png and Close button in the Localization Designer did not move the user back to the Configuration section. The issue was introduced when the Localization Designer was integrated into the "/shell."

Localization

Translations

Fixed an issue in the Translation section where a filter for untranslated values was applied automatically and silently at page load without being reflected in the UI. Previously, the section appeared to show all records although actually applying a hidden filter, causing confusion about the actual record count. This change removes the automatic hidden filter on page load and ensures any active filter is correctly displayed in the Translation section, giving users an accurate view of the actual record count.

Localization

Translations

Fixed an error that occurred during translation update when a previously folder-linked translation record had its source lookup record deleted. Previously, Creatio attempted to delete the orphaned translation record but failed due to a database constraint related to the folder reference, causing the update process to stop with an error. This change allows the translation update process to complete without errors in environments where lookup records linked to translation folders have been deleted.

Apps and packages

App management

Added backward dependency validation to the Application installation window for single-app, bundle, and Marketplace installation scenarios. Previously, installing an application version that conflicted with version constraints required by other already-installed applications was not prevented. No validation checked whether the version being installed can break existing dependencies. This change blocks installation when a version conflict is detected and displays the "Conflicting application versions" message with a detailed list of affected applications showing the version being installed and the required version constraints, giving administrators the information needed to resolve conflicts before proceeding.

Apps and packages

App management

Added downgrade warnings to the Application update and Application installation windows for single-app and bundle scenarios. Previously, when a user installed an older version of an application over a newer one already present in the environment, no warning was shown. This change displays a warning when a downgrade is detected during installation — provided no compatibility restrictions are in effect — giving users visibility into the potential version impact before proceeding.

Apps and packages

App management

Added automatic backup of previously installed package versions modified during installation to the install app operation. The backup is attached to the corresponding configuration activity log record. Previously, the install app operation did not create backups of modified packages, making it difficult to roll back individual package changes after installation. This change ensures that package backups are always available in the configuration activity log after installation, simplifying rollback and recovery scenarios.

More details

At the end of the installation flow, Creatio identifies changed packages using the core backup/restore logic, collects their generated *.gz backups from the backup directory, and attaches them to the installation log record. When multiple package backups are produced, they are additionally packed into a single *.zip archive ready for reinstallation. For the WorkspaceConsole utility, the installation flow was aligned with this behavior using the -saveBackup parameter of the InstallApp operation to control whether to generate package backups during installation.

Apps and packages

App management

Fixed an issue where uploading large archive files failed when compressed files of a few hundred MB expanded to more than 2 GB during processing. This change ensures large archives are processed correctly regardless of their decompressed size, improving reliability of file uploads.

Apps and packages

Package management

Fixed an issue where parallel static content generation processes could affect each other and cause errors in the generated static content when multiple threads or application domains ran concurrently. This change isolates parallel static content generation processes to prevent interference between concurrent execution contexts, eliminating errors caused by concurrent processing.

WCAG compliance

Screen reader support

Fixed multiple WCAG accessibility violations in the crt.MultiList component used in the Agent Inbox panel. This change applies proper aria semantics to the component, ensuring compatibility with assistive technologies.

UI Design

Freedom UI components

Added a new Hierarchical list component that enables users to view and interact with structured data organized in a multi-level hierarchy. The component supports key features of the standard List component, including sorting, inline editing and adding, and multi-select. The Hierarchical list component is designed for small data sets. The maximum number of records is managed by the "Maximum number of records in hierarchical list" (HierarchicalListMaxRecordsCount code) system setting. Out of the box, the value is set to "5,000." To further limit the data scope, use the Apply filter by page data parameter in the Freedom UI Designer setup area. This change enables no-code creators to build pages with hierarchically structured data without custom development, improving the ability to present and manage parent-child relationships directly in Freedom UI.

UI Design

Freedom UI components

Fixed an issue where the Timeline component jumped to the top while loading additional records during scrolling in Freedom UI. This change preserves the scroll position during incremental loading of the Timeline component, ensuring continuous scrolling without jumps.

UI Design

Freedom UI components

Fixed multiple layout issues in the Timeline component affecting "Case" (Case code) objects and other timeline objects, including title overlapping, inconsistent column alignment, and incorrect wrapping behavior for "Dropdown" type fields under constrained layouts. Previously, long titles and values of "Dropdown" type fields could overlap or break layout alignment, especially when the screen size was reduced, for example, with the Feed tab open. This change ensures consistent layout behavior across all timeline object types and screen sizes.

More details

The following layout fixes were applied:

  • Long case titles (Number field value together with Subject field value) are now wrapped correctly and do not overlap the "Date/Time" type field in the "Case" (Case code) object.
  • Consistent alignment of the description column in the "Case" (Case code) object was restored.
  • Left padding for "Lookup" type columns was added to align them with "Date" type columns.
  • Proper wrapping for "Dropdown" type fields displayed as links was enabled.
  • Wrapping behavior for color-coded lookup values was fixed, and truncation was applied where necessary.

UI Design

Freedom UI components

Fixed an issue in the Timeline component where not all emails were displayed when filters were applied. This change ensures all emails are included in timeline results consistently when date filters and sorting are applied, by correctly handling duplicate records from the EmailMetadata database table.

UI Design

Freedom UI layout elements

Added the Spacing parameter to the setup area of the Tabs and Toggle panel layout elements in the Freedom UI Designer. The parameter is configured individually for each tab, so different tabs within the same element can have different spacing values. Spacing includes the Top, Bottom, Left, and Right sub-parameters, each with the following values: "None," "Extra small," "Small," "Medium," "Large." Previously, spacing for these elements was not configurable in the designer. This change streamlines layout management and makes spacing adjustments more accessible and maintainable without additional coding.

UI Design

Fields and inputs

Fixed a Regular Expression Denial of Service (ReDoS) vulnerability in the link validation logic within the "Rich text" type field. Previously, inserting certain valid URLs containing parentheses in the fragment part could freeze the UI due to inefficient regex processing causing exponential backtracking. This change updates the link validation regex to handle URLs with complex fragments correctly, preventing UI hangs caused by exponential backtracking while maintaining secure input validation.

UI Design

Widgets

Added the ability to configure filtering for calculated metrics in Formula designer in the Freedom UI Designer when the new Function parameter is set to "Formula." Previously, filtering for calculated metrics could not be configured at design time, which meant configured conditions were not applied correctly at runtime. This change allows users to define quick filters and preconfigured filters for formula variables directly in the designer, with the configured conditions applied correctly when the metric is evaluated.

UI Design

Widgets

Added support for selecting columns from related objects using forward references in the Formula designer in Freedom UI. Previously, users could not navigate object relationships in the Formula designer and had to enter reference paths manually when building formulas based on related data. This change allows users to navigate object relationships directly in the Formula designer and select the required columns without manual input, reducing the risk of errors caused by manually entered reference paths.

UI Design

Widgets

Changed the setup area for metrics in the Freedom UI Designer and Dashboard Designer. Previously, chart settings were placed in the Chart setup window, which blocked visibility of the chart canvas and prevented users from previewing changes in real time. To use this functionality, register and enable the ShowLegacyWidgetSetup additional feature. This change allows users to adjust chart configuration settings in the setup area while continuously previewing the result on the canvas.

More details
  • Object, Function, and Column parameters were moved to the setup area.
  • The How to filter expanded list was moved to the setup area and replaced by the Set up filter button.
  • The Format, Text position, and Number of digits after decimal point parameters of the How to display expanded list were moved to the setup area as separate parameters.

Business processes

Parameters

Added support for record collections as input in the "Create from element" type parameter in the business processes. The element now accepts single parameters, a single record collection, multiple record collections, and mixed input combining single parameters and collections together with composite object. When a collection is passed, the element creates one record for each collection item. Empty collections are handled correctly — no records are created and no errors occur. Field mapping in the "Create from element" type parameter also supports binding to attributes of a collection item. To stop using this functionality, disable the ProcessFeatures.DisableCreateRecordCollectionFromElement additional feature. This change improves scalability of process design by reducing the need to duplicate logic for each created record, especially in agent and sub-agent scenarios.

Business processes

Elements

Added a new Send chat message element to the "User actions" group in the Elements area of Process Designer. The element enables sending automated chat messages from business processes without custom development. The element supports sending messages through configured chat channels using either chat templates or custom text and allows configuration of chat record column values so that the created chat is linked to related records correctly and displayed in their timelines. This change enables organizations to automate customer communication in chat channels using standard business process tools, simplifying setup of proactive notifications for scenarios, for example, case updates, reminders, or scheduling.

More details
  • The sender channel, recipient, and message content can be configured directly in the element setup area.
  • The message can be set as either a template-based message or a custom message.
  • Chat record column values can be configured to link the created chat to selected records, display it in their timelines, and use it as a macro source for message templates.
  • Error handling is supported through the Ignore sending errors checkbox. When the checkbox is selected, the process continues even if message sending fails, and the element returns execution status and error details as output parameters. When disabled, the process ends with an error and the failure details are recorded in the process log.

Business processes

Elements

Removed "Denied" option from the Which access rights to add? block on the setup area for the Change access rights element. The business logic is aligned with the current core access rights model and now works as "Not set" permissions on the object permission page. To stop using this functionality, disable the ChangeAdminRightsUserTask.DisableDenyRights additional feature. Existing business processes remain unchanged. This change ensures that access right configuration in business processes reflects the current platform model and prevents unintended use of the deprecated "Denied" permission level.

Business processes

Elements

Renamed the Call Creatio.ai element to the Sub-agent element in the Process Designer, including all corresponding UI elements. Previously, the term "Skills" was used to describe AI sub-components, which did not fully reflect their role in the AI Agent architecture and differed from widely used industry terminology.

Business processes

Elements

Added detailed logging to the "Delete data" (DeleteDataUserTask code) schema of the "User task" type for entity deletion diagnostics. Previously, entity deletions performed by the "Delete data" user task could not be traced to a specific process or logic easily without deep investigation, which made troubleshooting difficult and increased resolution time. This change logs each deletion operation with the entity ID, "Object" type schema code, element code, and "Business-process" type schema code in the unified log format without affecting execution performance, enabling faster identification of deletion sources and simplifying support analysis for process-driven entity deletions. To stop using this functionality, disable the DeleteDataUserTask.UseSpecificSchemaLogging additional feature.

Business processes

Execution

Changed the Is enabled checkbox status of the ProcessFeatures.UseRemovingSubProcessDataInFinalState additional feature from disabled to enabled. This change removes subprocess data automatically once a process reaches its final state, preventing unnecessary data accumulation in the environment.

Business processes

Tracing

Fixed an issue where process tracing failed if a process parameter used a formula, for example, Guid.Parse. Previously, tracing did not capture data for such processes, and the Show trace data button on the General information tab of the business process page in the process log was not available for elements like Read data that used formulas in parameters.

Business processes

Tracing

Fixed an issue where the tracing window did not display values passed from the Read data element with SUM aggregation functions to the Modify data element. Existing business processes remain unchanged. This change makes aggregated data from the Read data element with SUM functions visible in the tracing window.

Integrations and APIs

OAuth authorization

Changed the authorization code grant to allow authorization requests without the ApplicationAccess scope. Previously, integrations had to explicitly include this scope in the authorization request, which increased configuration effort and complicated integration logic, especially for solutions that work with multiple Creatio environments. This change removes the requirement to explicitly include the ApplicationAccess scope in authorization requests — Creatio adds it to the issued token by default after authorization, simplifying integration setup and making logic easier to implement across multiple Creatio environments.

Integrations and APIs

OAuth authorization

Changed the layout and responsiveness of the OAuth consent page to be displayed correctly on mobile devices. This change makes the OAuth consent page responsive on small screens, allowing users to review consent information and complete authorization more reliably in mobile device browsers and Creatio Mobile.

Integrations and APIs

OAuth authorization

Fixed an error that occurred when creating an OAuth client credentials grant integration with the selected Create separate technical user for this integration checkbox when the "Contact" (Contact code) object had additional required fields. Previously, Creatio blocked saving the integration because it attempted to validate required contact fields that were not relevant to the OAuth integration setup. This change skips validation of contact fields unrelated to the integration during save, so OAuth client credentials grant integrations and their associated technical users are saved correctly regardless of additional required fields on the "Contact" (Contact code) object.

Integrations and APIs

OAuth authorization

Fixed an error that occurred when creating an OAuth client if the Identity Service URL field value in the Connection settings window was entered without a trailing slash. Previously, the connection test passed successfully in this case, but the actual client creation failed for both client credentials and authorization code grants. This change normalizes the Identity Service URL field value before API calls, so a trailing slash is no longer required for OAuth client creation to succeed.

Integrations and APIs

OData

Changed the OData entity materialization logic to reduce memory consumption during read requests. This change has the highest impact on requests with multiple "Lookup" type columns.

Integrations and APIs

OData

Fixed an issue where OData returned outdated metadata after a new field was added, so new fields did not appear in OData responses until Creatio was restarted.

Integrations and APIs

@creatio/interface-designer library

Changed the SchemaModelEditor API of the @creatio/interface-designer library to expose data source management methods. Previously, addDataSource(), removeDataSource(), addDataSourceAttribute(), and removeDataSourceAttribute() methods were not accessible through the supported API. This change exposes these methods as public async methods, so data sources and attributes can be managed programmatically in Freedom UI page schemas.

Integrations and APIs

File processing

Changed attachment handling in Freedom UI to validate file integrity during download. Previously, users could attempt to download incomplete files if the upload process had not finished, which could result in corrupted or partially uploaded attachments being downloaded. This change blocks download of incomplete files by verifying that the current file size matches the total file size, displaying a detailed error message when the file is identified as incomplete.

Integrations and APIs

Email Listener

Added support for RabbitMQ quorum queues in the Email Listener for message processing. This change enables quorum queue configuration, with quorum queues recommended for production deployments, improving reliability and fault tolerance in cloud and distributed environments.

Integrations and APIs

Chats

Added the ability to manage the state of AI-driven conversation handling per chat channel on the Chat settings page. It is delivered as part of the Customer communication hub app available on the Creatio Marketplace. The "Supervisor" user can use the new AI handles conversation first checkbox in channel settings to control whether incoming conversations in a selected channel are processed by the Customer Support Agent or routed directly to chat agents. Out of the box, the checkbox is cleared for all existing chat channels, meaning that conversations bypass AI and follow standard routing to agents. When selected, all new incoming conversations in the selected channel are processed by an AI assistant personality selected in the channel settings and, when the Enable handoff checkbox is cleared, are not created in the Agent Inbox panel of the Contact Center app unless a handoff occurs. This change allows "Supervisor" users to control AI automation at the channel level, improving flexibility and transparency of conversation routing.

More details
  • AI responses are generated using a predefined configuration that includes the name, role and tone of voice of AI assistant personality, connected agents and sub-agents, and handoff settings.
  • Access control inherits existing section-level permissions.

Integrations and APIs

Chats

Added the ability to manually change a conversation status from "Bot processing" to "Completed by bot" using the progress bar on the chat page in the Chats section. Out of the box, only users that have the "System administrators" organizational role can execute the action. This change gives administrators direct control over the AI chat lifecycle when manual intervention is needed.

Integrations and APIs

Chats

Added the ability to configure an AI assistant personality to control AI communication style and identity in customer SMS, WhatsApp, Telegram, Web chat, and Facebook Messenger chat channels. The personality defines the AI assistant's name, role, and tone of voice, and is applied to all AI-generated messages in conversations. It is delivered as part of the Customer communication hub app available on the Creatio Marketplace. This change enables administrators to customize how the AI assistant presents itself in customer chat channels, improving brand consistency and communication quality.

More details
  • The AI assistant personality is configured in the AI assistant personality field in the channel settings.
  • The list of AI assistant personalities is managed by the AI personality for chats lookup. Out of the box, the lookup includes "Sofia, AI assistant" with a friendly tone of voice.
  • The list of tone of voice is managed by the AI tone of voice for chats lookup. Out of the box, the lookup includes friendly and formal tones of voice.
  • All AI-generated messages within a channel use the personality's name and role as AI identity and follow the defined tone of voice guidelines.
  • The personality configuration does not affect internal chat channels or existing AI behavior outside configured chat channels.
  • If the system prompt is customized, personality changes are not applied after upgrading to version 8.3.4.
  • Access control inherits existing section-level permissions.

Integrations and APIs

Chats

Added automatic closure of conversations in the "Bot processing" status on the chat page in the Chats section after a period of user inactivity. The timeout value is managed by the "AI chat inactivity timeout" (AiChatInactivityTimeoutMinutes code) system setting. Out of the box, the value is set to "15," in minutes. It is delivered as part of the Customer communication hub app available on the Creatio Marketplace. This change ensures that inactive bot-handled conversations are closed in a timely manner, reducing the number of stale open conversations and improving contact center operational efficiency.

Integrations and APIs

Chats

Added support for Business Scoped User IDs (BSUIDs) in WhatsApp communication through the Twilio provider. BSUIDs are part of WhatsApp's new privacy-first identification model, where users interact with businesses without exposing their phone numbers. Contacts can now be identified and mapped using BSUIDs (ExternalUserId) in addition to phone numbers, and inbound message handling was updated to process BSUID-based sender IDs correctly. This change ensures reliable message delivery, accurate contact identification, and uninterrupted chat workflows in both phone number and BSUID-based scenarios.

Integrations and APIs

Chats

Fixed an issue on the chat page in the Chats section where all messages from the parent chat were incorrectly displayed as authored by the last assigned agent after a chat transfer. The issue affected only the Chats section, although the "Chats" sidebar of the communication panel displayed message authors correctly. Previously, this caused loss of conversation context and produced incorrect audit history. This change preserves the original sender for each message in the Chats section after a chat transfer, including messages sent before and after the transfer, ensuring accurate conversation history and audit trail.

Integrations and APIs

Chats

Fixed a layout distortion in the "Chats" sidebar of the communication panel that occurred when inserting large screenshots into the chat sender. This change keeps the communication panel layout stable regardless of image size, preventing layout breaking when pasting images wider than the panel.

Integrations and APIs

Chats

Fixed an issue where live update did not work for the "Chat" (OmniChat code) object after replacing it in a custom package and enabling live updates. Previously, socket events from LiveEditingNotifier were not received and errors appeared in the logs. This change restores real-time update behavior and improves reliability of live editing scenarios in custom packages.

Integrations and APIs

Chats

Fixed an issue where cancelling the deletion of a WhatsApp chat channel with existing related records could leave the channel in a non-functional state. This change makes the deletion process atomic, preventing cases where cancelling deletion leaves a WhatsApp channel without its configuration and microservice linkage.

Integrations and APIs

Chats

Fixed an issue where WhatsApp and SMS chat channels could be created using invalid Twilio credentials. Previously, channels could be created with incorrect credentials, leading to configuration issues and failed message delivery. Validation of the Twilio account SID and token during channel creation was added to prevent saving channels when connection to the provider cannot be established. This change displays a validation error when invalid credentials are entered, preventing channels from being saved when connection to the provider cannot be established.

Integrations and APIs

Chats

Fixed an issue where chat distribution could fail in the "Chats" sidebar of the communication panel when the agent cache contained references to deleted chats. Previously, if a chat was removed before acceptance, stale references in the cache could break the distribution process entirely, preventing new chats from being routed to available agents. Added validation to exclude deleted chats from the agent cache during distribution and improved cache consistency handling when chats are removed outside of standard workflows. This change prevents chat distribution failures caused by stale references to deleted chats in the agent cache, ensuring new chats continue to be routed to available agents.

Integrations and APIs

Chats

Fixed an issue in the message sender in the "Chats" sidebar of the communication panel and the Agent Inbox panel of the Contact Center app where inserting a link disrupted typing behavior and triggered template selection. This change ensures that typing behavior remains consistent after inserting a link in the message sender, preventing unintentional template selection from interrupting the user flow.

Integrations and APIs

Emails

Added a migration tool for moving mailboxes between EWS and Microsoft Graph API in both directions. Previously, switching between EWS and Microsoft Graph API for existing mailboxes required manual reconfiguration without a guided migration flow. Contact Creatio support to request the migration tool. This change provides a structured and reliable way to migrate mailboxes between mail service providers, reducing the risk of errors during the transition and improving manageability of email integration configurations.

More details

The migration tool supports the following capabilities:

  • Selecting one or more mailboxes for migration.
  • Switching the mail service provider between EWS and Microsoft Graph API for existing mailboxes in both directions.
  • A confirmation step before the migration is executed.
  • Both impersonation-enabled and non-impersonation configurations.

Integrations and APIs

Emails

Added application-level impersonation support for Microsoft Graph API email integration using the ApplicationAsServiceAccount scenario. The email integration configuration was extended to support the application-based authentication model. Logging was also improved to provide detailed diagnostics when mailbox access fails due to Azure RBAC restrictions. Previously, Microsoft Graph API email integration did not support application-level impersonation, which limited the available authentication options for enterprise configurations. This change expands the supported authentication models for Microsoft Graph API email integration, improves troubleshooting of access-related issues, and provides better compatibility with enterprise Azure RBAC configurations.

Integrations and APIs

Emails

Fixed an issue where error messages related to invalid mail server credentials, for example, an incorrect client secret, were not cleared after correcting the mailbox configuration. Previously, even after providing correct credentials and successfully synchronizing emails, the error state persisted and continued to display outdated error messages. This change refreshes the error state after updating mailbox settings and clears it upon successful email synchronization, preventing stale error messages from persisting after a successful fix.

Advanced customization

Category

Feature

Description

Schema design and management

Module Designer

Added AI assistance instructions that work across all agent types to support custom Freedom UI component creation across the full development flow. The instructions cover both runtime and design-time implementation, including setup area configuration, and are aligned with existing baseline materials, for example, product guidelines, base component creation practices, runtime and design-time guidelines, technical guidelines for visual component development, icon creation guidance, and WCAG accessibility requirements. This change gives developers consistent and comprehensive AI guidance throughout the full custom component creation flow, covering runtime, design-time, accessibility, and visual development.

Schema design and management

Module Designer

Changed the remote entry loading mechanism from eager initialization to lazy loading. Previously, all remote entries were loaded during application startup, which increased the initial bundle size and slowed down page load. This change fetches remote entries on demand instead of at startup and excludes design-time functionality from runtime bundles, reducing application startup time and optimizing bundle size. New remote entries can be created with lazy loading configuration, and existing remote entries can be updated to use the new approach without breaking compatibility.

Data and database

Database management

Confirmed support for deploying Creatio on AWS RDS PostgreSQL 16.11. Starting from version 16.11, AWS resolved the backward compatibility issue with custom casts for some data types.

Data and database

Database management

Fixed an issue in PostgreSQL where updating the database structure failed when an altered column was referenced by a view that itself had dependent views.

Data and database

Data models

Fixed an issue where empty Name values in the Feature database table caused errors when updating additional feature states. This change automatically populates missing Name values with the corresponding Code values.

Feature management

Feature toggling

Changed the FeatureToggling mechanism to reduce memory consumption when additional feature statuses are checked with high frequency. Previously, delegate and closure objects were allocated on every feature state check, even when the result was already cached.

Performance

System performance

Changed the portal user creation mechanism to avoid triggering a full system-wide cache refresh of users and roles on every user creation. Previously, each portal user creation caused a full cache refresh, which under high creation volumes could freeze Creatio for up to 30 seconds.

Administration

Category

Feature

Description

Performance

System performance

Improved the performance of chat acceptance and status update operations in the "Chats" sidebar of the communication panel when processing large volumes of chats in distribution queues. Previously, these operations could become slow under high queue load due to synchronous processing and inefficient queries. This change reduces latency and improves scalability of the distribution logic.

More details
  • Queue distribution logic was moved to asynchronous processing to reduce response time for status updates.
  • Chat distribution on accept was made asynchronous and skipped when no agents are available.
  • Optimistic locking was added for agent assignment to prevent race conditions during concurrent distribution.
  • Unread message count notifications were batched to minimize database calls.
  • Deduplication of distribution processes was implemented during concurrent state changes.
  • Chat retrieval for agents was optimized using batching and short-term caching.
  • Database indexes were added to improve query performance for queue-based and unread chat selection.
  • WebSocket notifications were made asynchronous to reduce per-agent calls.
  • Reverse cache indexing was introduced to speed up cleanup and chat-to-agent mapping.

Security settings

Secure file upload

Fixed an issue where the TotalLength file metadata attribute was not copied during File.CopyAsync and File.MoveAsync operations. Previously, after file size validation was introduced, the missing TotalLength value caused validation failures and exceptions during attachment processing in file upload and email attachment scenarios. This change ensures TotalLength is correctly copied, preventing validation failures and exceptions during attachment processing. To stop using this functionality, disable the DisableFileSizeValidationOnDownload additional feature. When the feature is registered and disabled, file size validation remains active and TotalLength is always required during attachment processing.

Logging and monitoring

Change log

Fixed an issue where record changes were not logged when the modification was made by a user without read access to the object.

Logging and monitoring

Configuration activity log

Added tracking of create, update, and delete operations for apps, and create and update operations for sections, to the configuration activity log. This change logs create, update, and delete operations for apps and sections from Application Hub, Application Designer, Creatio UI, WorkspaceConsole, and Clio utilities, with each action recorded as a normalized log record containing the affected element, operation type, author, and execution status.

Logging and monitoring

Configuration activity log

Added tracking of create, update, delete, activate, and deactivate operations for packages to the configuration activity log. This change logs create, update, delete, activate, and deactivate operations for packages from the Configuration section, designers, WorkspaceConsole, and Clio utilities, including automatic actions, for example, dependency creation and package creation by designers, with each action recorded as a unified log record containing operation details, author, application, package, and execution status.

Logging and monitoring

Configuration activity log

Added logging of environment restart operations to the configuration activity log. This change records environment restart actions as audit records containing the operation name, author, execution time, and status — including UnloadAppDomain-based scenarios used by Clio utility — enabling administrators to audit restarts and simplify investigation of restart-related incidents.

Logging and monitoring

Configuration activity log

Added logging of the restore configuration operation to the configuration activity log. Previously, the restore configuration operation was not captured in the configuration activity log, making it difficult to audit and trace restore actions and their downstream effects. This change records the restore action as a parent operation with all downstream steps, for example, schema updates, database structure changes, source code generation, and SQL script execution, linked as child operations, with status tracking and restore log attachment supported across Creatio UI, WorkspaceConsole, and Clio utilities.

Logging and monitoring

Configuration activity log

Added tracking of localization create, update, and delete operations to the configuration activity log. This change logs localization changes across the installation flow, Translation section, and designers — covering both schema and data localizations, grouped by {SchemaName}_Localization_{CultureName} for active cultures only — with each record containing the operation type, element, author, application, package, and status.

Creatio maintenance

Creatio version update

Changed the Angular framework version used by the Creatio platform to version 19. This change aligns the platform with Angular 19 standards, ensuring continued compatibility with the latest framework capabilities.

User and access management

Licensing

Fixed an issue in .NET 8 and .NET Core builds where the License manager page opened from the Creatio login page became inaccessible for users without an active license. Previously, such users could not open the License manager page at all, which prevented them from managing licenses even when administrative access was intended. This change restores access to the License manager page in .NET 8 and .NET Core environments by loading the page correctly regardless of the current user's license status, ensuring administrators can manage licenses without requiring an active license themselves.

User and access management

Licensing

Fixed an issue where the License manager page failed to load for licenses distributed to more than 20,000 users. This change restores correct loading of the License manager page regardless of the number of users holding the license.

User and access management

Licensing

Fixed an issue where license expiration was checked against the server's local date instead of UTC, so on a UTC+2 server a license with a UTC midnight expiration appeared expired at 22:00 UTC the previous day.

User and access management

Technical users

Fixed an issue where a technical user could not be saved when the "Contact" (Contact code) object contained newly added required fields. This change skips contact validation for fields unrelated to the technical user during save, ensuring technical user records are saved correctly regardless of additional required fields configured in the "Contact" (Contact code) object.

User and access management

Access rights

Added the ability to override the default record-level access rights mechanism and implement custom access rights checking logic. This change ensures custom access rules are applied automatically whenever Creatio builds requests to the entity or filters based on its attributes.

User and access management

2FA

Fixed an issue where resetting a user password had no effect when two-factor authentication was enabled, so the user could not sign in using the new password.

User and access management

OpenID authentication

Changed the OpenIDSessionManager component that manages manages token-based authentication. Previously, each request required a full session lookup, which made session operations significantly slower under JWT authentication compared to cookie-based authentication. This change reduces authentication-related latency for environments using token-based authentication.

User and access management

Single Sign-On

Added support for Single Sign-On authentication in the Creatio plugin for Microsoft Word. This change ensures the plugin remains compatible with current Microsoft tooling and supported third-party library versions.

End user experience

Category

Feature

Description

Communications

Notifications

Fixed an issue where the notification mark was displayed for the "Business process tasks" sidebar of the notification panel even when the user did not have permissions to access the underlying SysProcessElementToDo records. Previously, this caused inconsistent UI behavior where the sidebar appeared empty although still showing a pending notification counter. This change ensures the notification mark in the "Business process tasks" sidebar is shown only when the user has access to the underlying process elements, preventing misleading pending indicators for users without the required permissions.

Communications

Message templates

Fixed an issue in the "Creating new case from chat" message template where macros were inserted using unsupported tags, causing incorrect text in the chat message sender. Previously, macros were displayed incorrectly due to unsupported formatting, reducing message clarity. This change ensures case registration macros are rendered with valid syntax and proper line breaks in the chat message sender.

Creatio products and apps

Creatio Marketing

Category

Feature

Description

Marketing campaigns

Campaign Designer

Added support for custom action types in the Campaign Designer. Custom campaign elements can now write specific action records to the campaign progress check instead of using generic actions. This functionality is managed by the "Campaign log item type" (CampaignLogItemType code) object that stores custom campaign action types. To use this functionality, add a lookup based on the "Campaign log item type" (CampaignLogItemType code) object, add a lookup record for the required action type, bind it to the package, and reference its ID as a custom action ID in the campaign element code. Data binding of lookup records in packages is supported to ensure consistent delivery across environments. When the campaign runs, the element writes logs using this custom action type instead of a generic one. This change improves clarity of campaign logs, enables better tracking of custom element behavior, and provides more accurate diagnostics and reporting for custom campaign activities.

Marketing campaigns

Campaign Designer

Added the Select template window that is displayed when initiating campaign flow design from the campaign page. Users can select a template to open it in the Campaign Designer, save existing campaign flows as custom templates, and create campaigns from templates.

More details

The window includes the following tabs:

  • Recommended templates. The tab contains predefined best-practice templates available for selection with a name, description, and thumbnail preview. Predefined templates are read-only and cannot be deleted.
  • Saved templates. The tab contains custom campaign flow templates saved by users. Users can store, preview, and reuse their own templates when creating campaigns.

Marketing campaigns

Campaign Designer

Added a new Add from Creatio landing page element to the "Triggered entry" group in the Elements area of the Campaign Designer. The element adds records to the campaign audience automatically when a visitor submits a form on a selected Creatio landing page, removing the need for manual data import or additional segmentation. Previously, users relied on manual imports or additional segmentation logic to include such contacts in campaigns. This change improves automation of lead generation processes, reduces manual effort, and ensures faster engagement with new leads by eliminating delays between form submission and campaign record.

More details
  • A landing page can be selected in the Landing page field and the type of record created after form submission can be selected in the Records created after form submission field in the element setup area.
  • The element displays the landing page name, direct record access link, and URL when the page is published.
  • Saving the element without a selected landing page is prevented by validation.
  • "Submission" (FormSubmit code) and "Lead" (Lead code) objects are available out of the box through the LandingPageId column for triggering a campaign based on landing page registrations. The list of supported objects cannot be extended. The campaign engine listens for form submission events and automatically adds associated contact records into the campaign flow in real time.

Marketing campaigns

Campaign Designer

Added a new Form submitted on Creatio landing page? element to the "Flow logic" group in the Elements area of the Campaign Designer. The element enables checking whether a campaign participant submitted a form on a selected Creatio landing page and routing them to the corresponding branch of the campaign flow. Previously, users had to rely on more manual logic or indirect setup to distribute participants based on landing page form activity. This change improves campaign automation, makes flow logic more transparent, and helps marketing teams react faster to participant actions.

More details
  • A landing page can be selected in the Landing page field and the object created after form submission can be selected in the Records created after form submission field in the element setup area.
  • The element displays the landing page name, direct record access link, and URL when the page is published.
  • Saving the element without a selected landing page is prevented by validation.
  • "Submission" (FormSubmit code) and "Lead" (Lead code) objects are available out of the box through the LandingPageId column for checking landing page form submissions. The list of supported objects cannot be extended.
  • The following output conditions are available for the campaign flow: "Form is submitted," "Form is not submitted," and "Regardless of the result."

Marketing campaigns

Campaign Designer

Renamed the Add from web page campaign element to Add from external landing page, the Audience object field in the element setup area to Records created after form submission, the "Insert a link to web page" placeholder for the Landing page URL field in the element setup area to "Insert a link to the landing page", and Landing page URL field description in the Campaign Designer.

Marketing campaigns

Campaign Designer

Renamed the Web page campaign element to Form submitted on external landing page?, the Audience object field in the element setup area to Records created after form submission, added the "Insert a link to the landing page" placeholder for the Landing page URL field in the element setup area, and changed the Landing page URL field description in the Campaign Designer.

Digital Ads

Ad campaigns section

Fixed an issue where audience name conflicts during export to Google Ads in the Digital Ads app caused the synchronization to fail or require manual input. This change automatically resolves audience name conflicts by appending the current date and time to the audience name, removing the need for manual intervention, and ensuring uninterrupted synchronization with Google Ads.

Lead Generation

Landing Page Designer

Fixed an issue where the Default value dropdown for "Dropdown" type fields in the Field settings expanded list on the Form settings tab of the Form settings mini page opened from the Landing Page Designer displayed only the first 30 values and did not allow searching for other available values. Previously, users could only select from the limited visible list, which restricted available options when configuring default values. This change restores the ability to search across the full dataset when selecting default values for "Dropdown" type fields and does not affect the number of displayed records.

Lead Generation

Landing Page Designer

Fixed an issue for grid form layouts where the Submit button width in the Form element in the Landing Page Designer was reduced to 50% after saving form settings. Previously, the fullwidth property for the Submit button was missing from the data model used in the form settings save handler, which caused the button width to reset to 50% on save. This change ensures the Submit button retains its full width (100%) after saving form settings in the Landing Page Designer, eliminating the need for manual adjustments.

Lead Generation

Facebook forms section

Fixed an issue where the Search process settings button in the Form submission settings profile on the Facebook form page was displayed even when the Contact search process field was not populated. The button is now displayed only when a contact search process is selected. This change prevents runtime errors when clicking the button without a configured process and ensures that users can access process settings only when a valid process is configured.

More details

Added the "Hide elements: Search process settings" page-level business rule to the "Facebook forms form page: Submission" (FacebookForms_FormPage code) and "Facebook forms form page: Leads" (FacebookFormLeads_FormPage code) schemas. The rule evaluates the Contact search process field value and dynamically shows or hides the Search process settings button based on its state.

Email Marketing

Bulk emails section

Changed the logic of the Send on field on the bulk email page. This change reflects the actual start of email delivery more accurately. Before sending starts, the field displays the date and time when the bulk email was submitted to the Creatio Email Service (CES). Once the first email in the mailing is sent successfully, the field is updated to the exact date and time of that first sent email. Additionally, copying a bulk email no longer populates the Send on field for the new record — the field remains empty until actual sending begins.

Email Marketing

Email Designer

Changed the default value of the rowsConfiguration.maxRowsDisplayed parameter from 30 to 60. The parameter defines the number of reusable rows displayed in the Email Designer.

Creatio Service

Category

Feature

Description

Contact Center

UI and navigation

Added the "Contact Center Agent" and "Contact Center Supervisor" workspaces to Creatio Sales and Creatio Service products. Creatio displays both workspaces when the Contact Center composable app is installed. Previously, the app was available only through the "Contact Center" workplace. This workplace is hidden from the navigation panel after upgrading to version 8.3.4 but remains in Creatio to preserve backward compatibility. Creatio continues to route chats and calls to the "Chats" and "Calls" sidebars of the communication panel. Out of the box, only users that have the "System administrators," "CC agents," or "All employees" organizational roles can access the "Contact Center Agent" workspace. Out of the box, only users that have the "System administrators" or "CC agents" organizational roles can access the "Contact Center Supervisor" workspace.

Contact Center

Agent Inbox panel

Added support for displaying "Sending," "Sent," and "Failed" delivery statuses of outgoing messages in the chat conversation of the Agent Inbox panel for the Telegram channel. Status indicators are displayed for each outgoing message and updated based on provider responses. Tooltips show the status name for successful states and failure details for failed messages. The message status and failure reason are stored in Creatio. This change gives agents visibility into whether messages were successfully sent or failed to reach the recipient, helping identify delivery issues and ensuring consistent monitoring of the message lifecycle across the Telegram channel.

Contact Center

Agent Inbox panel

Added support for displaying "Sending," "Sent," "Delivered," "Read," and "Failed" delivery statuses of outgoing messages in the chat conversation of the Agent Inbox panel for WhatsApp and SMS channels. Status indicators are displayed for each outgoing message and updated in real time based on provider callbacks. Tooltips show the status name for successful states and failure details for failed messages. The message status and failure reason are stored in Creatio. This change gives agents clear visibility into message delivery, enables tracking of the message lifecycle, and helps quickly identify delivery issues in WhatsApp and SMS interactions.

Contact Center

Agent Inbox panel

Added the ability to initiate outbound chat conversations across SMS, WhatsApp, Telegram, and Facebook Messenger chat channels directly from the message composer in the Agent Inbox panel of the Contact Center app. The supported channels can be added, removed, and configured in the Freedom UI Designer when the Contact Center app is installed. Out of the box, chat channels are available in the message composer on the case page. After sending a message, the chat opens in the Agent Inbox panel for further communication. This change enables agents to contact customers across supported chat channels proactively from a single interface, ensuring communication follows channel rules and integrates seamlessly with the Agent Inbox workflow.

More details
  • At runtime, users can select a chat channel and specify the sender and recipient using the From and To fields. The sender is selected from the list of active chat channels. The recipient list is filtered based on channel rules:

    • For SMS — contacts with phone numbers.
    • For WhatsApp, Telegram, and Facebook Messenger — only contacts who have previously interacted with the company through that channel.
  • Users can compose messages using out-of-the-box chat capabilities, including attachments, emojis, and templates.

  • After sending, a new chat is created or an existing active chat assigned to the current agent is reused. If the chat is already assigned to another agent, sending is not allowed and the user is notified.

  • Channel-specific messaging policies apply:

    • For WhatsApp and Facebook Messenger — messages can be sent only within the 24-hour messaging window.
    • For Telegram — only to users who have previously initiated interaction with the bot.

Contact Center

Agent Inbox panel

Changed the default visibility of queue-related actions in the Freedom UI Designer for Contact Center app. Previously, the Re-queue and Postpone till buttons were visible in the Freedom UI Designer out of the box, which could expose queue-related actions in contexts where they were not needed. This change hides the Re-queue and Postpone till buttons in the Freedom UI Designer by default, giving no-code creators explicit control over queue-related action visibility and preventing unintended exposure of queue management actions on pages. To use this functionality, register and enable the CCQueueDesignerButtons additional feature.

Contact Center

Agent Inbox panel

Fixed an issue where the btn_open_templates.png and btn_translate.png buttons in the message sender of the Agent Inbox panel were not aligned with other buttons in the same row.

Contact Center

Agent Inbox panel

Fixed an issue where chat distribution could fail in the Agent Inbox panel of the Contact Center app when the agent cache contained references to deleted chats. Previously, if a chat was removed before acceptance, stale references in the cache could break the distribution process entirely, preventing new chats from being routed to available agents. Added validation to exclude deleted chats from the agent cache during distribution and improved cache consistency handling when chats are removed outside of standard workflows. The distribution process now continues correctly even when invalid chat references are present in the cache. This change ensures robust handling of cache inconsistencies and maintains reliable chat routing under all conditions.

Contact Center

Agent Inbox panel

Fixed an issue where a translation error occurred when sending files in the Agent Inbox panel with outgoing translation enabled. Previously, Creatio attempted to process file messages through the translation flow, causing errors and blocking file sending. This change updates the message sending logic to exclude file attachments from translation processing, ensuring reliable file delivery while maintaining translation functionality for text messages.

Contact Center

Agent Inbox panel

Fixed an issue where previously assigned chats disappeared from the Agent Inbox panel after adding an agent to a different chat queue and refreshing the page. Previously, adding an agent to one queue cleared the agent cache globally, although redistribution ran only for the changed queue, causing chats assigned in other queues to disappear from the agent's view after refresh. This change prevents assigned chats from disappearing from the Agent Inbox panel after an agent is added to a different queue, by preserving chat visibility for agents in unaffected queues during cache refresh.

Contact Center

Agent Inbox panel

Fixed an issue in the message sender in the Agent Inbox panel of the Contact Center app where inserting a link disrupted typing behavior and triggered template selection. This change ensures that typing behavior remains consistent after inserting a link in the message sender, preventing unintentional template selection from interrupting the user flow.

Contact Center

Agent Inbox panel

Fixed an issue where draft messages were not always fully removed from the chat tile preview in the Agent Inbox panel after clearing the message sender. This change ensures draft messages are fully cleared from the chat tile preview in the Agent Inbox panel when the message sender input becomes empty.

Industry cases

Category

Feature

Description

Field sales

UI and navigation

Added Freedom UI counterparts for the Knowledge base, Orders, Contacts, and Accounts sections in the "Field workplace" workplace of the Field sales products. Previously, this functionality was available in Classic UI only. This change enables users to interact with unified Freedom UI pages while existing visibility rules and business logic remain unchanged.

More details
  • The Knowledge base section is displayed only if the Knowledge Management app is installed.
  • The Orders, Contacts and Accounts sections remain available in "Field workplace" workplace.
  • The Dashboards section was removed from the "Field workplace" workplace.

Field sales

UI and navigation

Added the Activities section to the "Field workplace" workplace of the Field sales product. Previously, users accessed activities outside of the workplace, which required additional navigation steps. This change enables users to view and manage activities directly within the workplace without changing the underlying functionality.

Field Management

UI and navigation

Added Freedom UI counterparts for the Knowledge base, Contacts, and Accounts sections in the "Field workplace" workplace of the Field Management product. Previously, this functionality was available in Classic UI only. This change enables users to interact with unified Freedom UI pages while existing visibility rules and business logic remain unchanged.

More details
  • The Knowledge base section is displayed only if the Knowledge Management app is installed.
  • The Contacts and Accounts sections remain available in "Field workplace" workplace.
  • The Dashboards section was removed from the "Field workplace" workplace.

Field Management

UI and navigation

Added the Activities section to the "Field workplace" workplace of the Field Management product. Previously, users accessed activities outside of the workplace, which required additional navigation steps. This change enables users to view and manage activities directly within the workplace without changing the underlying functionality.

Pharma

UI and navigation

Added Freedom UI counterparts for the Knowledge base, Orders, Contacts, and Accounts sections in the "Pharma" workplace of the Pharma product. Previously, this functionality was available in Classic UI only. This change enables users to interact with unified Freedom UI pages while existing visibility rules and business logic remain unchanged.

More details
  • The Knowledge base section is displayed only if the Knowledge Management app is installed.
  • The Orders, Contacts and Accounts sections remain available in the "Pharma" workplace.
  • The Dashboards section was removed from the "Pharma" workplace.

Pharma

UI and navigation

Added the Activities section to the "Pharma" workplace of the Pharma product. Previously, users accessed activities outside of the workplace, which required additional navigation steps. This change enables users to view and manage activities directly within the workplace without changing the underlying functionality.

Creatio Mobile

Category

Feature

Description

Mobile UI Design

Freedom UI Mobile components

Added the Style, Size, and Position parameters to the setup area of the Folder management menu and Sort components in the Freedom UI Mobile Designer. If an invalid or empty value is set, Creatio applies the default configuration automatically to maintain visual consistency. This change enables flexible appearance customization of these components across mobile pages without developer involvement.

More details

Available parameter values:

  • Style: "Primary," "Focus," "Warning," "Plain," "Secondary." Out of the box, "Secondary."
  • Size: from S to 3XL. Out of the box, "M."
  • Position: "Icon left," "Only icon," "Icon right." Out of the box, "Icon left."

Mobile UI Design

Freedom UI Mobile components

Added support for the Visibility expanded list for the Quick filter component in the Freedom UI Mobile Designer. This list allows you to configure business rules that control the component visibility at runtime. Previously, the component was always visible. This change provides more flexible and context-aware mobile page configurations.

Mobile UI Design

Fields and inputs

Fixed an issue where the number of digits after the decimal separator was not restricted at runtime for the "Number" type field when its Format parameter in the Freedom UI Mobile Designer was set to "Currency (0)," "Currency (0.1)," "Currency (0.001)," or "Decimal (0)." The mobile app now correctly validates and restricts input according to the configured format. This change ensures that values entered on mobile pages are saved and synchronized with web pages consistently and without loss of precision.

Mobile UI Design

Fields and inputs

Changed the behavior of "Dropdown" type fields on mobile pages created in the Freedom UI Mobile Designer. This change prevents "Dropdown" type fields on mobile pages from displaying deactivated lookup records, ensuring consistent behavior with web pages. The "Inactive" column is available only for lookups whose object has the Allow records deactivation checkbox selected in the Behavior section of the Object Designer.

Mobile UI Design

Dashboards

Fixed an inconsistency in decimal formatting of dashboards where Creatio Mobile truncated decimal values instead of rounding them. To stop using this functionality, register and disable the UseMobileOldUIDecimalRoundFormatting additional feature.

Performance

System performance

Fixed an issue where business rules on mobile pages were executed redundantly, causing excessive service calls and degraded performance of the List component at runtime.

Beta testing of new features

Category

Feature

Description

No-code tools

Freedom UI Designer

Added support for right-to-left (RTL) view in the Freedom UI Designer when RTL mode is enabled. No-code creators can now work with page layouts in RTL view with full support for drag and drop, element reordering, resizing, and operations with tabs of the Tabs and Toggle panel layout elements. Previously, the designer did not reflect RTL runtime behavior, which made layout validation less accurate for RTL scenarios. This change improves preview accuracy and reduces layout design errors for RTL pages. To stop using this functionality, disable the DesignerRtlSupport additional feature.

No-code tools

Freedom UI Designer

Added the ability to preview a configured page directly in the Freedom UI Designer without publishing changes. To use this functionality, register and enable the InterfaceDesignerPreviewButton additional feature. When the feature is enabled, the action panel in the Freedom UI Designer includes the Preview button that lets no-code creators switch between edit and preview modes at any time without losing current page changes. Previously, users could not validate the final appearance of a page before publishing. This change reduces the need to publish changes just to validate the result.

Localization

Localization Designer

Added automated procedures to keep object and column codes in the SysDataLocalizableValue database table synchronized with current metadata. Previously, renaming an object or column did not update the corresponding codes stored in the SysDataLocalizableValue table, which caused the Localization Designer to display incorrect codes and produced poor search results. This change provides two update procedures for the SysDataLocalizableValue table — a global one for all records and a per-object one for targeted updates — both idempotent and safe for translation values, with unresolved references logged rather than corrupting data, improving navigation accuracy in the Localization Designer and removing the need for manual data cleanup after schema changes. A new "Actualize Localization Codes" business process was created to run both procedures. The per-object update procedure can also be triggered automatically on object schema save using the ActualizeLocalizationCodesOnSchemaSave additional feature. Orphaned localization records can be removed using the DeleteOrphanedLocalizationRecords additional feature. Out of the box, both the features are registered and disabled.

UI Design

Freedom UI components

Added support for the Advanced filters menu and Advanced filters components in the Freedom UI Designer that enable users build complex filter conditions using object columns and related object columns. To use this functionality, register and enable the ShowDesignerDemoItems additional feature. End users can apply filters to records that match all conditions (AND) or any condition (OR). The list of operators depends on the column type to which the advanced filter is applied. This change enables flexible data filtering without additional coding.

UI Design

Widgets

Added the ability to configure comparison logic for metrics in the Freedom UI Designer. Previously, analyzing performance changes over time required custom implementation, as comparison logic could not be configured using no-code tools. This change allows users to define the comparison period and comparison value for metrics directly in the designer without custom development, enabling no-code analysis of performance changes over time. To use this functionality, register and enable the ShowMetricWithComparison additional feature. When the feature is enabled, the Compare with another value toggle is displayed in the setup area for metrics. Out of the box, the toggle is disabled. When enabled, the Setup comparison button is displayed, which opens the comparison configuration.

UI Design

Widgets

Added support for dynamic filters for non-formula metrics with comparison values in the Freedom UI Designer when the Function parameter is set to a non-formula aggregation value. Previously, page-data and preconfigured filters could not be configured for such widgets, which could lead to inconsistent data representation at runtime. To use this functionality, register and enable the ShowMetricWithComparison additional feature. When the feature is enabled and comparison is configured, the Setup filter button is displayed in the setup area, allowing users to configure filters for the comparison value. This change allows users to configure page-data and preconfigured filters for both the main value and the comparison value of non-formula metric widgets directly in the designer, with the configured conditions applied correctly at runtime.

UI Design

Widgets

Added a trend indicator to the metrics to display the change of a key metric compared to a selected comparison period. Previously, users had to analyze underlying data manually to understand metric dynamics, as no visual indication of change was available. To use this functionality, register and enable the ShowMetricWithComparison additional feature. When the feature is enabled, the Freedom UI Designer element library includes a new comparison metric and the trend indicator provides a quick visual representation of metric dynamics and reflects increase, decrease, or no change states based on percentage and absolute difference calculations. The update is applied automatically to existing metrics after upgrading to version 8.3.4. This change allows users to assess metric performance quickly without analyzing underlying data.

Integrations and APIs

OAuth authorization

Added support for the authorization code grant using Proof Key for Code Exchange (PKCE) for public clients, for example, mobile apps and single-page apps. When an integration is registered as a public client, Creatio requires PKCE parameters during authorization and token exchange and does not expose a client secret in the registration UI. For confidential clients, PKCE can also be enforced as an additional requirement alongside the client secret. Previously, the authorization code grant supported only confidential clients that used a client secret, so public clients could not be integrated securely without storing a secret. This change enables secure integration for browser-based and mobile apps without a client secret.

Integrations and APIs

Chats

Added a new Web chat channel that allows administrators to configure a web chat on their website. Previously, Creatio did not support a native web chat for website visitor engagement. Contact Creatio support to request access. This change enables organizations to add a native web chat to their websites and manage conversations directly in Creatio, expanding omnichannel capabilities and providing a seamless way to engage website visitors in real time.

Creatio Sales

Sales Engagement

Added a new Sales Engagement composable app that enables sales representatives to execute sequence-generated activities across "Call," "Email," and "Task" activity types from a unified Activity execution panel. The app includes the Sequences and Email templates sections, displayed in the "Sales engagement" workplace. Contact Creatio support to request access.

More details

The Sequences section includes the following capabilities:

  • Create sequences for BDR workflows using the New button in the Sequences section.
  • Configure sequences as pipelines of "Call," "Email," and "Task" activity types for BDR workflows using the Add step button on the Steps tab of the sequence page. Fill out the activity fields such as Name, Priority, Description, Postpone, Measurement, Subject, Body. The list of fields depends on the activity type.
  • Copy, edit, or delete a step using row actions on the Steps tab of the sequence page.
  • Add the sequence audience using the Add audience button in the Sequence audience expanded list on the Audience tab of the sequence page. If you attempt to add a user without an owner, Creatio displays a warning.
  • Add a new ruleset or edit an existing ruleset using the Ruleset field of the sequence page. Creatio lets you configure safety settings, opt-out settings, prospect stage transitions, out of the office settings, call task settings, actions outside of a sequence on the ruleset page.
  • Add a new delivery schedule or edit an existing delivery schedule using the Delivery schedule field of the sequence page. Creatio lets you configure default time zone and delivery schedule slot on the delivery schedule page.

The Email templates section includes the following capabilities:

  • Create and edit templates using Create template button in the Email templates section. Tags become available after the template is saved.
  • Search templates by name, subject, or body, and filter by folder, tag, or owner Email templates section.
  • Preview template content, including unsaved changes and resolved macros, using the Preview button of the email template page.
  • Send a test email after selecting a contact in the Choose contact field and entering email in the Send to field using the Send a test button in the Email preview window. The test email uses the current template content, including unsaved changes, and returns a success or error notification.

Creatio Sales

Sales Engagement

Added the Sales Engagement Desktop as a centralized workspace for BDR users who work with the Sales Engagement app. The desktop combines the Upcoming tasks widget, Open tasks for today, Completed tasks, Completed Tasks (Success), and Completed Tasks (Failure) metrics, and the Daily activities expanded list on a single page. The activity list displays sequence-generated activities assigned to the current user and supports search, filtering by type, refresh, and direct activity execution. It is delivered as part of the Sales Engagement app. Contact Creatio support to request access. This change provides BDR users with a unified workspace to monitor performance and manage daily sequence activities.

Creatio Sales

Sales Engagement

Added sequence participant status synchronization in the "Status" column in the Sequence audience expanded list on the Audience tab of the sequence page to keep participant statuses consistent with the current sequence status. It is delivered as part of the Sales Engagement app.

More details
  • When a sequence status is set to "Active," participants in "Active," "Paused," and "Pending" statuses are changed to "Active," while participants in "Bounced," "Failed," and "Finished" statuses remain unchanged.
  • When a sequence status is changed from "Active" to "Paused," only participants in "Active" status are changed to "Paused."
  • New participants added to an active sequence receive "Active" status automatically.

Creatio Sales

Sales Engagement

Added support for reassigning sequence participants in "Active" and "Paused" statuses and their open, non-canceled activities to the new owner when the contact owner changes. Participants in "Finished" and "Failed" statuses remain unchanged during reassignment. Sequence execution continues without restart and no duplicate activities are created. It is delivered as part of the Sales Engagement app. This change ensures correct ownership for ongoing sequence execution and prevents loss of responsibility for follow-ups.

Creatio Sales

Sales Engagement

Added a daily enrollment limit for sequence participants per sequencer. When a user initiates bulk enrollment, Creatio groups selected contacts by owner, calculates how many participants each sequencer has already enrolled during the current day using a UTC-based start of day adjusted by the schedule time zone, and creates records only for sequencers within the configured limit. If the limit is exceeded for a sequencer, Creatio skips enrollment for that group and returns an error. Contacts without an owner cannot be enrolled. When participants are deleted, the daily limit is recalculated dynamically without reserving historical slots. It is delivered as part of the Sales Engagement app. This change prevents over-assignment and controls sequencer workload in real time.

Creatio Sales

Sales Engagement

Added the ability to configure a delivery schedule for sequences to control when sequence activities are generated. Users can configure a schedule name, default time zone, and delivery slots defined by weekday, start time, and end time. During activity generation, Creatio evaluates the current time in the configured time zone and creates activities only within the defined delivery slots. If no valid slot is active, generation is skipped until the next valid window. Sequences without a configured schedule retain their existing behavior. It is delivered as part of the Sales Engagement app. This change improves compliance with communication policies and reduces off-hours engagement.

Creatio Sales

Sales Engagement

Added the crt.ActivityExecutionPanelActionRequest request to open the Activity execution panel from any Creatio page. It is delivered as part of the Sales Engagement app.

More details
  • When the request passes the ActivityId parameter, Creatio opens the panel with the specified activity loaded immediately.
  • When the request passes null as the ActivityId, Creatio opens the panel with the activity list so users can select an activity manually.

Creatio Sales

Sales Engagement

Added the ability to hide and show the activity list in the Activity execution panel using the btn_activity_list.png button. Creatio displays the button when the panel is in expanded or fullscreen modes only. It is delivered as part of the Sales Engagement app. This change provides more screen space for activity details when working with the panel. Hiding the list does not affect the current activity selection or execution state.

Creatio Sales

Sales Engagement

Added support for "Call," "Email," and "Task" activity types in the Activity execution panel with dynamic page rendering based on schema configuration. It is delivered as part of the Sales Engagement app.

Creatio Sales

Sales Engagement

Added support for managing activities directly in the Activity execution panel that provides shared layout, activity context loading, and execution actions for sequence-generated activities. It is delivered as part of the Sales Engagement app. This change ensures consistent execution behavior across activity types and simplifies development of new execution scenarios.

More details

The Activity execution panel supports the following actions:

  • Displays activity details such as contact profile, activity name, priority, and description in read-only mode, and editable Result and Result details fields.
  • Marks the activity as completed and advances the sequence using the Complete button for "Call" and "Task" type activities.
  • Sends the email and marks the activity as completed using the Send and Complete button for "Email" type activities.
  • Initiates a call through telephony integration using the Call button for "Call" type activities.
  • Sets a date and time to postpone the activity using the Snooze button for all activity types. When postponing a "Task" type activity, Creatio recalculates the due date automatically based on the original task duration.
  • Saves changes without completing the activity using the Save changes action for all activity types.
  • Opens the activity page using the Open activity action for all activity types.
  • Opens the related contact page using the Open contact action for all activity types.

Creatio Sales

Sales Engagement

Added support for filtering activities by type and priority in the Activity execution panel. It is delivered as part of the Sales Engagement app.

More details
  • Available activity types: "Call," "Email," and "Task."
  • Available activity priorities: "High," "Low," "Medium."

Creatio Sales

Sales Engagement

Added the ability to open the related contact page by clicking an activity in the Activity execution panel. If no related contact is available or access is restricted, navigation is not performed. It is delivered as part of the Sales Engagement app. This change reduces the time needed to access contact information related to an activity.

Creatio Sales

Sales Engagement

Added the btn_back.png button to the Activity execution panel. Creatio displays the button when an activity is open in the panel and the panel is in default mode only. It is delivered as part of the Sales Engagement app. This change lets users navigate directly to the activity list without reopening the panel.

Creatio Sales

Sales Engagement

Added support for executing "Call" type activities through telephony integration directly in the Activity execution panel without opening additional call interfaces. Creatio retrieves available phone numbers from the contact communication options and presents them for selection. The call lifecycle is tracked to update the activity state accordingly. The Complete button becomes available only after the required result is specified. It is delivered as part of the Sales Engagement app. This change improves execution speed and reduces context switching for call activities.

More details

Available call results: "Bad number," "Call later," "Canceled," "Completed," "Information received," "Issue invoice," "Meeting scheduled," "Need discovered," "No answer," "Not interested," "Wrong contact."

Creatio Sales

Sales Engagement

Added the ability to send emails directly from the Activity execution panel for "Email" type activities. Users can review sender and recipient information, edit the email subject and body where configuration allows, and send the email through the configured mailbox using the Send and Complete button. After successful sending, Creatio marks the activity as completed and continues sequence processing. If sending fails, Creatio displays an error and keeps the activity available for correction and retry. It is delivered as part of the Sales Engagement app. This change improves execution speed and reduces context switching for sequence-driven email activities.

Creatio Sales

Sales Engagement

Added the ability to compose and edit emails directly in the Activity execution panel for "Email" type activities. The HTML editor supports read-only mode when the activity state does not allow editing. It is delivered as part of the Sales Engagement app. This change reduces context switching and improves the quality of sequence emails during activity execution.

More details

The HTML editor supports the following actions:

  • Insert macros that are resolved against the current activity or participant context on the server side using the btn_select_macro.png button. Available macros: "Select field macro," "User Name," "User Email," "User Phone." The list of supported macros cannot be extended.
  • Open a list of pre-configured email templates using the btn_open_templates.png button.
  • Format email body content using the btn_formatting_options.png button or by pressing Alt+F10.