Complete the Expected due date field
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use this date for the Overdue KPI when the case remains open.
Where to goAdmin Area → Licence Applications → New/Edit Application → Expected due date
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 this guide helps you do
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.
Follow these steps
- Go to the new or edit case form.
- Find Expected due date.
- Enter or select the value described in this guide.
- Save the case.
- Reopen the case and verify the stored value.
Fields and options
FieldExpected due date
Payload keyexpected_due_date
Supported valueOptional date
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-create-edit/
Rules and limits
- 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.
Check it worked
- 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.
Related guides
Was this guide useful?Your response is stored only in this browser.