Setup, access and permission scope

Install and activate Advanced Task Filters

Activate version 1.0.4 and create the personal saved-filter table.

Audience: CRM staff and administratorsPermission: AdministratorModule v1.0.4
Exact navigationAdmin Area → Setup → Modules → Advanced Task Filters → Activate
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

Activate version 1.0.4 and create the personal saved-filter table. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Upload the complete module directory through the approved CRM module deployment process.
  2. Open Setup → Modules and locate Advanced Task Filters.
  3. Select Activate.
  4. Confirm the Task Filters sidebar menu appears.
  5. Open Task Filter Templates and verify the page loads without a database-table error.

Fields, choices and supported possibilities

Installed tableOne prefix-aware table stores filter name, serialised parameters and staff owner.
Version1.0.4.
CRM requirementThe source header declares compatibility with CRM 1.0.* or later in that series.

Code-backed validations and workflow rules

  • Activation executes install.php and creates the saved-filter table when it does not already exist.
  • Migrations 101–104 are present but their upgrade methods contain no schema operations.

Expected result and verification

  • Activation 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.
  • Use a database user that can create the module table during activation.