Security, limitations and troubleshooting

Troubleshoot a task template that does not load

The filter ID must be numeric, owned by the current staff member and loaded without a competing POST request.

Audience: CRM staff and administratorsPermission: Administrator / authorised CRM staffModule 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

The filter ID must be numeric, owned by the current staff member and loaded without a competing POST request. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Reproduce the behaviour with a controlled staff account and known task records.
  2. Open it from Task Filter Templates, confirm ownership and avoid modifying the URL.
  3. Refresh the page and compare the result with the core Tasks workspace.
  4. Record the outcome before changing permissions or module code.

Fields, choices and supported possibilities

Verified behaviourThe filter ID must be numeric, owned by the current staff member and loaded without a competing POST request.

Code-backed validations and workflow rules

  • The filter ID must be numeric, owned by the current staff member and loaded without a competing POST request.

Expected result and verification

  • Troubleshoot a task template that does not load 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.