Understand date and overdue logic
Use Expected due date for operational overdue reporting and Renewal due date for future renewal planning.
Exact navigationAdmin Area → Full Compliance Applications → New Application or Edit
Before you begin
- Confirm the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide covers
Use Expected due date for operational overdue reporting and Renewal due date for future renewal planning. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Admin Area → Full Compliance Applications → New Application or Edit.
- Locate the record, setting or action used to understand date and overdue logic.
- Complete the displayed fields or controls exactly as described in this guide.
- Select the available save, submit, update, call, sign, upload or confirm action.
- Return to the related register, portal, dashboard or call panel and verify the recorded result.
Fields, choices and supported possibilities
Expected due dateUsed to calculate the Overdue KPI.
Renewal due dateStored for future renewal action.
Code-backed validations and workflow rules
- A case is overdue only when the expected date is before today and its status is not in the completed or renewal group.
Expected result and verification
- The understand date and overdue logic workflow completes without a validation, permission or availability error.
- The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
- Any client-visible or public result appears only where the code explicitly allows it.
Security, privacy and operational checks
- Use a controlled test case, contact, extension or website origin before production rollout.
- Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.