Settings Management — Управление бизнес-настройками

Export and import Directum RX settings archives (.datx) via DeploymentToolCore.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill settings-management-dunaevdmitriys-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Settings Management — Управление бизнес-настройками
Source: https://github.com/dunaevdmitriys-dev/directum-mcp-server/tree/main/skills/settings-management
Command: npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill settings-management-dunaevdmitriys-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Directum RX business-process configurations must be transferred consistently between environments, otherwise deployments become incomplete or require manual rework.

Core Features & Use Cases

  • Export settings to .datx: package business settings (roles/rights, module parameters, NoCode process variants, defaults, and org templates) from a source environment into a portable .datx archive.
  • Import settings from .datx: restore the packaged configuration on a target environment with optional credentials.
  • Apply during deployment: attach settings to deployment so they take effect at the right stage, including optional settings localization via XLSX.

Quick Start

Export all business settings as a portable file by running dt export_settings with the path /output/all-settings.datx from your DeploymentToolCore launcher.

Frequently Asked Questions about Settings Management — Управление бизнес-настройками

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export Directum RX business settings to a .datx file for deployment?

Export Directum RX business settings to a portable .datx archive by running the dt export_settings command with a target path from your DeploymentToolCore launcher. This packages roles, module parameters, NoCode variants, defaults, and organizational templates into one file.

Can I import settings into a target Directum RX environment using a .datx archive?

You can import settings into a target Directum RX environment by running the dt import_settings command with the .datx archive. It restores packaged business-process configuration and supports optional folder scoping and credential parameters for secure deployment.

What business-process configurations are included when exporting Directum RX settings?

Exporting Directum RX settings captures roles, rights, module parameters, NoCode process variants, defaults, and organizational templates. This ensures business-process configurations remain synchronized across deployment environments without requiring manual rework.

Does DeploymentToolCore support settings localization during Directum RX deployment?

DeploymentToolCore supports settings localization during Directum RX deployment via XLSX files. You can attach settings to deployment workflows with apply and exit-code handling so localized configurations take effect at the correct deployment stage.

Do I need credentials to import Directum RX settings from a .datx file?

Credentials are optional when importing Directum RX settings from a .datx file using the dt import_settings command. You can include credential parameters alongside optional folder scoping to control how the configuration is restored on the target environment.

Why do Directum RX deployments fail when transferring business settings between environments?

Directum RX deployments fail when business-process configurations are not transferred consistently, leading to incomplete setups. Using dt export_settings and dt import_settings with .datx archives automates this synchronization, preventing deployment errors and manual rework.