Interface Constructor
The constructor allows you to restructure the table for your tasks: hide unnecessary columns, change their order, rename headers, and add a column with a value that is not originally in the table. The table configuration can be assembled with clicks or described in words — the request will be processed by an AI model. On the record editing pages and in the section tabs, the constructor hides and rearranges tabs, blocks, and fields of the attribute set.
The configuration is tied to a specific screen and does not affect others. The finished configuration can be saved as a preset — then it will be visible to all project administrators, and an administrator with assignment rights can make it the default screen view for colleagues (see Assigning settings to other administrators).
The word request is executed by the model, and the model is taken from accounts on the Settings → AI Agents tab. In the constructor panel, it is selected using the AI Account and AI Model fields. If there are no accounts, the request cannot be sent — only manual assembly with clicks remains.
Access Rights
The constructor is managed by two rights from the administrator group on the Setting up rights to modules tab of the administrator card (see Editing an administrator):
| Right | What it provides |
|---|---|
uiComponentConfigs.edit — configuring screens for oneself | column gear, constructor panel, presets, page settings for records and section tabs |
uiComponentConfigs.assign — assigning screen settings to others | settings assignment tab in the administrator card, modifying and deleting presets saved by other administrators |
Without the uiComponentConfigs.edit right, the constructor shows nothing on the screens — no gears, no buttons, no panel, even when the mode is enabled. The same rights are checked by the server: the interface only hides what is inaccessible.
How to Enable
The constructor mode is enabled by the button with the equalizer icon in the application header. This is a toggle: when the mode is enabled, the icon is highlighted. The mode is needed for the constructor panel, presets, and record page settings. The column gear above the tables is visible even when the mode is off — see Column Gear.
After enabling, buttons appear above the table:
| Button | Purpose |
|---|---|
| Gear | selecting table columns — the same as outside the mode |
| Builder | opens the settings panel for this table |
| Presets | list of saved screen settings |
| Undo icon | undoes the last change in settings; appears when there is something to undo |
| Reset icon | returns the table to its default view |
The constructor is connected to tables and forms in all sections of the application. How it looks on record editing pages is described in the section Record Pages and Section Tabs.
Column Gear
Above each table connected to the constructor, there is a button with a gear icon. It is visible to administrators with the uiComponentConfigs.edit right at all times, even when the constructor mode is off: to show or hide a column, the panel with the AI model is not needed.
The gear opens a list of table columns divided into three groups of checkboxes:
| Group | What it contains | What the checkbox does |
|---|---|---|
| default columns | the table's own columns | an unchecked checkbox hides the column |
| additional fields | built-in fields of records that the table does not show by default | a checked checkbox adds a column with this field |
| attributes | attributes from sets that records on this screen may have | a checked checkbox adds a column with the attribute value |
An attribute that is not present in any record on the screen is shown faintly with a tooltip: its column will be empty. A field already displayed in one of the default columns may also appear among additional fields — if checked, a second column with the same data will appear in the table.
Hiding a column does not remove control elements from the rows: dragging, row selection checkbox, and expand buttons move to the first visible column.
Long attribute values in a cell are shown in a shortened form: HTML text — the beginning of the text without markup, JSON — in one line, images — as thumbnails. Next to such a value is an eye icon: clicking on the value opens it fully in a separate window — HTML text rendered, JSON in a viewer, images in full size.
At the bottom of the list is a button to reset the table settings. It removes all settings for this table in your browser, including changes made through the constructor panel. The gear and the panel write to the same settings: a column added by request and a column marked by a checkbox coexist together.
Record Pages and Section Tabs
When the constructor mode is enabled, it also works on record editing pages: administrator, content page, product, collection, template, block, block slide, form, event, discount, order storage, user, user group, authorization provider, and user permissions. Tabs that are shown in the menu sections can also be configured.
What can be configured:
- tabs — each tab gets an eye icon (to hide or show) and can be dragged to another location. The last visible tab cannot be hidden;
- blocks of the editing page — eye icon and dragging, where blocks are connected to the constructor;
- attribute set fields — eye icon and dragging for each field.
Hidden elements in constructor mode remain on the screen dimmed, so they can be restored; after turning off the mode, they disappear. The configuration only changes the view: a hidden field still participates in form validations.
Tabs and blocks are configured for the entire screen, while fields are configured separately for each attribute set: it is not known in advance which set will be present in the opened record. Therefore, each area has its own toolbar — above the tabs and above the attribute set fields:
| Button | Purpose |
|---|---|
| configurations | list of saved settings for this area (in the Russian interface — "Конфигурации") |
| saving the current setting | saves the area setting under the specified name (in the Russian interface — "Сохранить текущую") |
| Undo icon | undoes the last change in this area |
| Reset icon | returns tabs and blocks or fields to their default view |
The Builder button is not present on record pages — tabs, blocks, and fields are configured only with the eye icon and dragging.
Constructor Panel
The panel opens with the Builder button and is titled Table Constructor.
Model Selection. The AI Account and AI Model fields determine which account and which model will process the request. The selection is common for the entire constructor, not for a separate table — it does not need to be set again on each screen.
Word Request. In the What to change? field, the desired result is described in plain language, for example, "remove the URL column and show the number of products." Below, under the heading Or start with a ready one, there are ready-made examples — they can be inserted with one click: hide a column, compact rows, custom text for empty state, number of products in a category, and others. The request is sent with the Apply button.
Preview. The model's response is shown as a list of understandable changes, and the settings are applied only after confirmation — until you agree, the table does not change.
Currently set. This section shows what is currently configured: "changes to this table, each can be deleted separately." Here is also the Column visibility block — clicking on the eye icon hides the column or brings it back.
Compile manually. Manual assembly without a model: step by step, you select what to show, the source of the value, and the required field. Convenient when it is easier to choose from a list than to formulate in words.
What else can be configured. A collapsed help section about what else the constructor can do on this screen — useful when it is unclear how to formulate a request.
Calculated Columns and Data Sources
A column can show a value that is not present in the row — for example, the number of products in a category. Where to get it from is described by the source: a predefined path to the API with parameters. Arbitrary addresses are not accepted, only records from the sources catalog.
The catalog consists of built-in sources and those created by administrators. If there is no suitable one, the constructor will suggest searching in the API: the agent will find candidates, perform a test request on a real row, and show the returned values — the field is selected based on actual data, not description.
The agent can also create a source for the request. Such a source is initially not saved: the column with it already shows live data — this is the verification, and a card for the new source appears above the preview. It names the source, the API operation called, and the response fields from which the values are taken. One button on the card saves the source to the catalog, and another discards it — then all columns referencing it are removed from the settings and the yet-to-be-applied proposal. An unsaved source lives only until the page is reloaded; when saving a preset, the sources used by its column are saved automatically.
Searching for a source takes more time than other operations.
Saving and Reusing
While the settings are not saved, they are stored only in your browser. Saving sends them to the server under the specified name — after that, the preset is available to all administrators of the project in the Presets list (on record pages — in the configurations list of their area), from where it can be applied to their own.
The author can delete or modify their preset. A preset saved by another administrator cannot be changed or deleted without the uiComponentConfigs.assign right. A preset assigned to at least one administrator cannot be deleted by anyone: the server will refuse and inform how many administrators it is assigned to — first, remove the assignment.
The reset button removes the settings stored in your browser and returns the table to its original view. Saved presets remain.
Assigning Settings to Other Administrators
An administrator with the uiComponentConfigs.assign right can set how screens look for colleagues by default. For this, in the administrator card (the Administrators section), there is a separate tab for assigning screen settings (in the Russian interface — "Настройки экранов"). Without this right, the tab is not available.
The tab lists only screens for which there are saved presets, in three groups:
- record pages — one row per screen: a separate row for tabs and blocks and one row for each attribute set for which there are presets, with a counter of assigned rows;
- section tabs — which tabs are visible in the menu section itself and in what order;
- tables and forms — one row per screen.
In each row, a preset is selected from a dropdown list; clearing the list removes the assignment. A notification informs about success or error.
The assigned view is applied the next time the administrator logs into the admin panel — if the assignment is newer than what has already been applied in their browser. An assignment made after the administrator's own edits replaces them; a regular page reload does not affect their own view. The administrator can then change their view — until the next assignment. If the assignment is removed, the screen returns to the default view unless the administrator has already changed it themselves.