Understand the absence of status management UI
Know that the 19 statuses are seeded in installation but no settings screen edits them.
Exact navigationAdmin Area → Licence Applications
Before you begin
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Confirm module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What this guide covers
Know that the 19 statuses are seeded in installation but no settings screen edits them. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open the exact workspace stated above.
- Confirm activation, permission, ownership, field validation and supporting service configuration.
- Apply only the corrective action supported by the supplied code.
- Retest with a controlled case.
Fields, choices and supported possibilities
Status settings UINot implemented
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-troubleshooting-limitations/
Code-backed validations and workflow rules
- The supplied module implements or omits the function exactly as described.
Expected result and verification
- Understand the absence of status management UI completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the least-privilege account that has the stated permission.
- Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.