Skip to main content

Creatio AI app development toolkit updates 2026

This article contains a description of changes to Creatio AI app development toolkit that affect no-code creators who build apps using coding agents. Learn more about the toolkit: Creatio AI app development toolkit.

October 2026​

App management​

Sections in workplaces. The agent now adds a section to an existing or new workplace and grants access to the workplace for the roles you specify in one step. For a new workplace, the agent sets the workplace type: general, portal, or self-service. If an existing workplace has a different type, the agent stops before changing anything.

Packages created by the agent. The agent now creates packages, either standalone or in an app. The agent adds the schema name prefix of the environment to the package name and checks the name, dependencies, and app before creating the package.

Data model design​

Connections of an object. The agent now shows and changes which lookup columns of an object appear on the Connections tab of the object's pages. This functionality is available for Creatio 10.2 and later.

Pages setup​

Web-to-mobile page conversion out of the box. Web-to-mobile page conversion is available out of the box and no longer requires a Clio experimental command. If the installed Clio does not support the conversion, the agent asks you to update Clio and retry. The conversion supports the following:

  • Mobile layout. The agent converts pages for phones. Tablet layouts are experimental: the agent generates them and asks you to check the page on a tablet before you rely on it. Full-width lists of a web page keep their width on tablets.
  • Missing pages report. The report separates buttons whose page binding was cleared from objects that have no default mobile page, so you can see which buttons need a page registered.

The conversion requires Clio 8.1.0.137 or later. Learn more: Convert web pages to mobile pages.

Automated check of form pages. After building a Freedom UI form page, the agent now opens it in a browser in the background and reports what the page displays, so you can see that the page works without opening it yourself. Before the agent uses or downloads a browser for this check, it asks for your consent and remembers your choice.

Appearance customization​

Branding previews and target package. The agent describes logo and background previews in text and renders them only when you ask. Before applying a theme, the agent names the package that receives the branding, and the final summary confirms the package that received the theme.

Business processes​

Files in business processes. The agent now configures the Process file element and file parameters in business processes. The agent supports the following:

  • Element variants. The Process file element takes files from record attachments, generates a printable report for a record, or takes files from a process parameter.
  • File storage. For objects that do not have their own attachments object, such as "Account address" or "City," the element stores files linked to the record in the shared file storage.
  • Parameters. Business processes get parameters of the "File," "File collection," and "Collection" types, including the properties of collection items.

These capabilities require a recent version of the CrtProcessBuilder package in the environment. If the package is outdated, the agent offers to update it.

Business process runs and checks. The agent now waits until a business process run finishes and reports its final status and the first error, including errors from sub-processes. The agent lists the records that the run created and can delete them after the check. If a run waits for a user task, the agent says what the run waits for. To check a business process that starts when a record is added, the agent creates the record and reports what the business process created.

Process tracing and versions. The agent turns on tracing for the business processes it creates or modifies. When you ask the agent to run a specific version of a business process, the agent runs that version rather than the active one.

Diagram layout. When the agent changes only parameters, mappings, or element properties, the business process diagram keeps the layout you arranged.

Classic UI to Freedom UI migration​

Migration plans for complex sections and construction based on your decisions. Classic UI sections with multiple customization layers now reach an approvable migration plan, and construction starts from the decisions you made during planning. The migration includes the following improvements:

  • Existing Freedom UI sections. If a Freedom UI counterpart of the Classic UI section already exists, the agent asks whether to extend its pages or build a separate section. By default, the agent extends the existing pages.
  • Details. Details that add records by selecting them from a lookup migrate as expanded lists that add records the same way. Row actions removed from a Classic UI detail stay removed in the expanded list.
  • Planning decisions. The agent applies your decisions before construction starts and skips items that you dropped or that have nothing to build in the environment.
  • Construction session. After you approve the migration plan, the agent asks whether to run construction in a new session, in the current session, or in a compressed session.
  • Child pages. The agent binds each rebuilt child page to the expanded list that opens it and verifies the binding in the environment.
  • UI text in all cultures. The agent carries captions, expanded list titles, and detail messages from Classic UI in every culture and verifies them. This requires Clio 8.1.0.137 or later. With an earlier Clio version, the migration plan notes that translations are not migrated.
  • Verification. The verification summary table marks a card action as done only when a page element performs that action, and matches built elements by name and type.

Learn more: Migrate a section from Classic UI to Freedom UI.

Administration​

Object operation permissions and default record permissions. You can now ask the agent to set up object operation permissions for roles: create, read, edit, and delete. The agent also turns record permissions on or off for an object and sets default record permissions. Learn more: Object operation permissions.

Toolkit setup and updates​

Messages about failed updates. When a toolkit update fails, the agent shows a message that matches the cause, for example, a locked file.

September 2026​

Data model design​

Multiple object columns in one step. The agent now adds multiple columns to an object in one step. Default values of columns show readable values instead of IDs.

Schema name prefix. The agent now adds the schema name prefix of the environment to the schemas it creates in a package.

Section setup and management​

Sections based on existing objects. The agent now creates a section based on an existing object and adds a section description.

Pages setup​

Web-to-mobile page conversion (beta). You can now ask the agent to convert a Freedom UI page into a Freedom UI mobile page. Before converting a page, the agent checks whether the target mobile page exists. If the page is missing, the agent reports it and can create it. Each conversion plan starts with a beta notice. To take advantage of this functionality, update Clio to version 8.1.0.118 or later and enable the mobile page converter using the clio experimental --name mobile-page-converter --enable command.

note

Since October 2, 2026, web-to-mobile page conversion is no longer in beta and is available out of the box in Clio 8.1.0.137 and later. Learn more: Convert web pages to mobile pages.

UI localization​

Page captions in other cultures. The agent now translates page captions into another culture and keeps the English (en-US) captions unchanged. If a page inherits its title from a template, the agent notifies you.

Business processes​

Approvals, data operations, branching, and versions in business processes. The agent now creates and modifies business processes with more process elements, branching, and versions. The agent supports the following:

  • Process elements. The agent configures the Approval, Open edit page, Change access rights, Sub-process, Add data, Read data, Delete data, and Formula elements. A Sub-process element can run in the multi-instance mode.
  • Template-based emails. The agent configures the Send email element to send messages based on email templates.
  • Branching. The agent adds gateways and conditional flows to a business process.
  • Versions. The agent creates a new version of a business process and makes the version you choose active. A new version stays inactive until you activate it, so you can roll back to a previous version.
  • Lookup values. Business processes display the names of lookup records instead of their IDs.

Some of these capabilities require the latest version of the CrtProcessBuilder package in the environment. If the agent reports that the package is outdated, ask the agent to reinstall it.

Classic UI to Freedom UI migration​

Dashboards and resumable construction in Classic UI to Freedom UI migration. Classic UI sections now migrate to Freedom UI with fewer manual checks, because the agent analyzes sections in more detail, includes dashboards in the migration, and saves progress after each construction task. The migration includes the following improvements:

  • Classic UI analysis. Ask the agent what a Classic UI section, form page, mini page, or detail does, and the agent describes every customization along with the source that contains it. If the agent can analyze only part of a section, it stops and tells you which part it could not analyze.
  • Migration plan. The agent checks the plan against the Creatio environment before construction starts. The plan includes elements added to the Classic UI section itself, Classic UI card widgets, and a list of elements the agent could not place in Freedom UI. The plan describes custom methods in business terms, in the "What it does" and "Use case" columns.
  • Dashboards. The plan includes the dashboards of the Classic UI section. After you approve the plan, the agent installs the Dashboards migrator app if the environment does not have it, migrates the dashboards, and verifies the result.
  • Construction. The agent splits the approved plan into separate tasks and builds them one by one. The agent saves progress after each task, so the migration continues from where it stopped if the session ends. The chat shows which task is running, how long it has been running, and how long the remaining work takes.
  • Scope decisions. Items you mark as postponed or out of scope are recorded in the plan, and the agent does not build them.
  • Result report. The migration ends with one migration result report that compares the approved plan with the pages the agent built. A page gets the "done" status only if it renders correctly.
  • Coding agents. The migration works the same way in Claude Code, Codex, and GitHub Copilot.

Learn more: Migrate a section from Classic UI to Freedom UI, Migrate dashboards from Classic UI to Freedom UI.

Administration​

User and role management. The agent now manages users, roles, manager groups, licenses, delegation, IP restrictions, and access permissions in the Creatio environment.

Email template content. The agent now reads and updates the content of email templates, including bulk email templates and their language versions. When the agent copies a template, the copy keeps the format of the original.

Toolkit setup and updates​

Connection to environments. The agent now connects to a Creatio environment using a support access grant or OAuth authorization code sign-in.

Control over toolkit updates. Automatic updates of Clio and the toolkit are now turned off by default. Updates of the toolkit guidance stay on, and the agent receives updated guidance without a restart. To turn on automatic Clio updates, run the clio autoupdate --enable command. The clio ver command shows the installed toolkit version for each coding agent.

Toolkit installation in Codex. The toolkit now installs and updates in Codex CLI, and all toolkit skills are available in Codex sessions. The toolkit also detects Clio installed in the "C:\Program Files" directory.