Understand migrations 101–104
The four migration classes exist but their up methods contain no schema changes.
Exact navigationAdmin Area → Setup → Modules → Advanced 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 four migration classes exist but their up methods contain no schema changes. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Reproduce the behaviour with a controlled staff account and known task records.
- Use activation/install.php as the source of the saved-filter table and verify the installed version through Setup → Modules.
- Refresh the page and compare the result with the core Tasks workspace.
- Record the outcome before changing permissions or module code.
Fields, choices and supported possibilities
Verified behaviourThe four migration classes exist but their up methods contain no schema changes.
Code-backed validations and workflow rules
- The four migration classes exist but their up methods contain no schema changes.
Expected result and verification
- Understand migrations 101–104 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.