1c-cf-add-object

You can automate adding a 1C:Enterprise metadata object by chaining meta-compile, cf-edit, form-add, and form-compile workflows into a single end-to-end creation process. This orchestration generates scaffolds and ensures configuration consistency automatically.

Creating a 1C metadata object with subsystem integration involves executing a multi-step workflow: cf-edit updates Configuration.xml, subsystem-edit integrates the object, and a final validate step ensures consistency across all generated forms and attributes.

No, the workflow orchestrates these steps together. It automatically handles Configuration.xml updates alongside form generation and subsystem integration, ensuring that scaffolding and final validation are executed as a unified chain without manual intervention.

To initialize the full metadata object workflow for your 1C configuration, you need to provide the object type, object name, and required attributes. These inputs satisfy the requirements for generating the forms and subsystem entries automatically.

Form generation may fail without validation because the workflow enforces consistency between Configuration.xml updates and generated forms. The final validate step checks integration across subsystems and attributes, preventing errors from manual configuration edits.

Yes, the workflow is designed for reuse when adding new metadata objects to an existing 1C:Enterprise configuration. It repeats the scaffold generation, form compilation, and validation steps to maintain consistency across each new object added.