role-compile

To generate 1C role metadata and rights XML, provide a structured JSON role description and the target 1C configuration directory. The compiler validates object and right names, applies RLS conditions, and emits deployable metadata files into the configuration tree.

Yes, you can use Russian aliases for 1C object and right names during role file generation. The compiler accepts Russian object and right names and automatically converts them to canonical 1C metadata names within the output XML files.

You can model 1C permissions for catalogs, documents, registers, services, configuration rights, and nested metadata objects. The JSON DSL also supports using presets and applying RLS restrictions to define granular access control.

Generating 1C roles with a JSON DSL respects existing configurations by applying support-state guardrails. The compiler safely validates object and right compatibility, warns on invalid combinations, and prevents unauthorized modifications to protected configuration metadata.

The best way to define RLS conditions and presets for 1C access roles is through a compact JSON DSL. This approach translates structured permission definitions directly into ready-to-use rights XML files, eliminating the need to handcraft XML blocks.

1C role compilation fails when invalid object and right combinations are detected within the JSON DSL. The compiler validates object and right compatibility for nested metadata objects and issues warnings to prevent generating incompatible role metadata and rights XML files.