Understand the default task-report state
Know which status is applied when no status selection is submitted.
Exact navigationAdmin Area → Task Filters → Task Filters
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
Know which status is applied when no status selection is submitted. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open the report without loading a saved template.
- Leave Task Status unchanged.
- Apply the filter.
- Review the selected status and returned rows.
Fields, choices and supported possibilities
Default statusIn Progress when the request contains no status value.
Other criteriaRemain at their displayed default or All option until changed.
Code-backed validations and workflow rules
- The default status prevents an unbounded all-status result on the first report request.
- Select the required statuses explicitly when historical or completed work must be included.
Expected result and verification
- The default-state check completes without a validation or permission error.
- The refreshed report, menu or saved-template page shows the expected state.
- A second authorised user sees only the records and navigation allowed by their core CRM permissions.
Security, privacy and operational checks
- Test changes with a non-production record or a controlled administrator account before wider rollout.
- Do not use navigation visibility as a substitute for core CRM record permissions.