Complete the Expected due date field
Use this date for the Overdue KPI when the case remains open.
Exact navigationAdmin Area → Licence Applications → New/Edit Application → Expected due date
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
Use this date for the Overdue KPI when the case remains open. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open the new or edit case form.
- Locate Expected due date.
- Enter or select the value described in this guide.
- Save the case.
- Reopen the case and verify the stored value.
Fields, choices and supported possibilities
FieldExpected due date
Payload keyexpected_due_date
Supported valueOptional date
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-create-edit/
Code-backed validations and workflow rules
- Use this date for the Overdue KPI when the case remains open.
- Case editing writes this field to the application record unless a dedicated workflow rule is stated.
Expected result and verification
- Complete the Expected due date field 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.