Govern the case-classification tree

#Page purpose

Maintain the bilingual, hierarchical dispute taxonomy used by the case register.

#Before you start

• Sign in as case-classification administrators and confirm WatheeqTech shows /lex/admin/classifications; hidden controls indicate that your account lacks the required permission.
• Prepare the approved bilingual values, policy decision or connector details before opening a form; do not use production records as test data.
• Collect the reason, authority and supporting evidence required for any governed decision or state transition.

#How to use this page

1. 1
   Assess the current configuration

   Search or quick-jump to the branch you need, then inspect its usage count, system status and child classifications before changing it.

2. 2
   Make the governed change

   Create, translate, reorder, merge or import classifications with the page’s cascade and impact warnings in view.

3. 3
   Validate the configuration

   Run localization and usage checks, then confirm the revised tree appears on the case-classifications page without orphaned children.

#Governance and expected result

• Operate only within the tenant, role and record visibility granted to you.
• Record the decision, reason and supporting evidence before completing a governed action.
• Check dependent services, roles, records and policies before deleting, deactivating or changing precedence.
• Use preview, evaluator, conflict-check or test controls when the page provides them, and verify the audit result after saving.