Understand generated licence references
Follow this guide to use the immutable-looking case identifier created at submission. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Licence Applications → New Application → Save
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify 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 you’ll accomplish
Use the immutable-looking case identifier created at submission. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Save a new case.
- Go to the case.
- Record the generated reference for correspondence and search.
Fields and options to review
FormatLIC-YYYYMMDD-XXXXXX
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-create-edit/
Rules the system enforces
- The supplied case form and model apply this behaviour.
How to confirm it worked
- Understand generated licence references 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.