Understand the default task-report state
This guide explains that which status is applied when no status selection is submitted. 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 → Task Filters → Task Filters
Before you start
- Verify 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 you’ll accomplish
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.
Follow these steps
- Go to the report without loading a saved template.
- Leave Task Status unchanged.
- Apply the filter.
- Check the selected status and returned rows.
Fields and options to review
Default statusIn Progress when the request contains no status value.
Other criteriaRemain at their displayed default or All option until changed.
Rules the system enforces
- 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.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.