Security, limitations and troubleshooting

Advanced Task Filters

Understand the Create-capability limitation

The module registers a Create capability, but the current save-template branch does not perform a separate Create check after View access is granted.

Understand the template-update ID limitation

The model update method applies by template ID after the normal controller load; the model method itself does not add a staff-owner condition to the update query.

Troubleshoot an empty task report

One or more criteria may conflict, the selected date field may be blank, or core task permissions may exclude rows.

Troubleshoot a missing Staff Member filter

The member selector is intentionally shown only to users with global core Tasks View permission.

Troubleshoot a missing Customer Group filter

The customer-group control depends on Related Type being Customer.

Troubleshoot custom task date results

The report filters only the selected date basis and uses equality when From and To match.

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.

Troubleshoot the missing template-name message

The browser script requires a non-empty name when Save Filter Template is selected.

Understand the absence of shared task templates

The supplied model lists templates by current staff ID and provides no sharing or transfer screen.

Understand unsupported task-filter automation and APIs

The supplied module registers no cron process, API endpoint, webhook, scheduled report, email delivery or PDF generator.

Understand migrations 101–104

The four migration classes exist but their up methods contain no schema changes.

Verify Advanced Task Filters after deployment

Run a controlled end-to-end access, report, template and export test.