Classify a document as Requested
Save the uploaded document with status requested. 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 → Case → Upload Document → Document status
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
Save the uploaded document with status requested. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the case upload form.
- Select Requested from Document status.
- Select the correct file and complete type/notes/expiry.
- Upload.
- Check the status beside the document.
Fields and options to review
Stored valuerequested
Status labelRequested
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-admin-documents/
Rules the system enforces
- The status is assigned at upload time.
- The supplied controller has no later document-status edit action.
How to confirm it worked
- Classify a document as Requested 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.