Saved task-filter templates

Save a new task-filter template

Store the current report parameters under a personal template name.

Audience: CRM staff and administratorsPermission: Advanced Task Filters: View (the current code does not separately enforce Create)Module v1.0.4
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

Store the current report parameters under a personal template name. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Configure every report criterion, grouping and hidden/export column required.
  2. Select the checkbox labelled Select Checked to Save Filter Template.
  3. Enter a clear name in Save as Filter Template.
  4. Select Apply Filter.
  5. Open Task Filter Templates and confirm the new template appears.

Fields, choices and supported possibilities

Save checkboxEnables template persistence for this request.
Template nameRequired by the browser script; the form limits input to 100 characters while the database column allows up to 200.

Code-backed validations and workflow rules

  • The submitted filter parameters are serialised and stored with the current staff ID.
  • Use names that identify purpose and period rather than personal data.

Expected result and verification

  • Saving the template 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.
  • Do not include secrets or sensitive customer details in the template name.