Ready-Made Solution Versions

A version defines the ready-made solution's resources, first-installation steps, and actions required when an existing installation moves to that release. The author explicitly selects automations, agents, segments, landings, and triggers, while the cabinet adds their required MCP servers, knowledge base content, custom metrics, and variables as dependencies. New installations and upgrades use the highest-numbered published version.

Open Ready-made solution in the application menu. The versions page shows every release and its state. Select the required version to open its contents and available actions.

Ready-made solution versions. Highlighted elements: 1. versions page; 2. required version — 1. versions page · 2. required version

Prepare a Release

Creating a version: source project and draft.
Version resources: contents, dependencies, and replacements.
Publishing a version: update mode, release, and catalog availability.

Version statuses

Draft. The version can be configured and edited, but cannot be installed in another project.
Published. The version participates in selecting the current release for installation and upgrade.

A draft can be deleted without affecting published versions or existing installations. A published version cannot be deleted individually: it remains an immutable part of the ready-made solution history, including for projects that already installed it.

Deleting the ready-made solution itself is a separate action. The ready-made solution disappears from the cabinet and catalog, and all of its installations are removed together with the resources they created in user projects.