Understand option persistence after deactivation
The supplied source registers activation but no deactivation/uninstall cleanup hook. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Menu Setup
Before you start
- Verify 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 you’ll accomplish
The supplied source registers activation but no deactivation/uninstall cleanup hook. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Reproduce the behaviour with a controlled administrator account.
- Reset menus before deactivation when the default menu must be restored; verify saved options after lifecycle changes.
- Test the resulting navigation with an administrator and a restricted staff account.
- Reset or restore the intended menu configuration after the test.
Fields and options to review
Verified behaviourThe supplied source registers activation but no deactivation/uninstall cleanup hook.
Rules the system enforces
- The supplied source registers activation but no deactivation/uninstall cleanup hook.
How to confirm it worked
- Understand option persistence after deactivation 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.