role-validate

Validating a 1C role Rights.xml file involves checking XML well-formedness, root namespace, and global flags to catch structural mistakes. It verifies object types, allowed right names, and right values against schema expectations.

RLS condition validation for 1C access control detects empty RLS conditions and verifies restriction templates by checking their names and conditions. This ensures row-level security rules are structurally sound and correctly defined.

Yes, you can check if a 1C role Name is registered in Configuration.xml. The validation process optionally verifies this registration and warns you if the role is missing from the configuration file.

Yes, role validation supports checking Role metadata UUID and Synonym. It optionally validates inferred Role metadata including UUID, Name, and Synonym to ensure role properties are correctly defined.

The best way to audit 1C access control rights before publishing is running a comprehensive Rights.xml validation across role directories. This checks XML correctness, rights names, values, and RLS conditions to catch semantic mistakes early.