Task report criteria

Combine multiple task-filter criteria

Build a narrow report by applying supported conditions together. 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.

Audience: CRM staff and administratorsPermission: Advanced Task Filters: ViewModule v1.0.4
Jump to steps
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

Build a narrow report by applying supported conditions together. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Start with the broadest required scope: staff member or related type.
  2. Add status and billable conditions.
  3. Add a related record, customer group or tags where applicable.
  4. Select the reporting period and date basis.
  5. Select grouping and hidden/export columns.
  6. Apply the filter and remove one condition at a time if the result is unexpectedly empty.

Fields and options to review

Criteria relationshipDifferent filter families are combined together, narrowing the result.
Multi-select fieldsSelected values inside status or tags act as allowed alternatives.

Rules the system enforces

  • A result must satisfy every applicable filter family.
  • Related record and customer-group filters depend on a compatible Related Type selection.

How to confirm it worked

  • The combined report 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.