cfe-init

A 1C configuration extension scaffold requires Configuration.xml, an adopted Russian language file, and an optional main role. This structure enables safe patching and customization workflows without modifying the base configuration directly.

ConfigurationExtensionPurpose in a 1C configuration extension defines the modification intent, supporting Patch, Customization, or AddOn workflows. This setting controls how the extension adjusts the base configuration safely.

When generating a 1C configuration extension, you set the ConfigurationExtensionCompatibilityMode parameter. The scaffold applies a default compatibility setting of Version8_3_24 to ensure correct platform integration.

Yes, you can generate a 1C configuration extension without a main role by using the NoRole parameter. This creates the Configuration.xml and Russian language files without an optional role file for simpler patching workflows.

No, generating a configuration extension will not overwrite an existing Configuration.xml file. The scaffold generation process explicitly refuses to overwrite existing files in the target directory to prevent data loss.

The best way to validate a 1C configuration extension after scaffolding is to run a dedicated validation check on the resulting extension directory. This ensures the generated Configuration.xml and role files are correctly structured.