Understand compiled feature switches

This guide explains that Brand/Model/Series settings are disabled, Proposal integration is active, and the legacy old-customer proposal branch is disabled. 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.

What you’ll accomplish

Recognise that Brand/Model/Series settings are disabled, Proposal integration is active, and the legacy old-customer proposal branch is disabled. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

1. Go to Admin Area → Inventory → Settings.
2. Select the record or action required for understand compiled feature switches.
3. Complete the displayed fields and choices described in this guide.
4. Save, submit, approve or confirm the action as shown on screen.
5. Refresh the relevant list, record or report and verify the expected result.

Fields and options to review

Rules the system enforces

• Only controls rendered by the supplied module are documented; hidden AJAX helpers are mapped to their visible parent workflow.
• Core CRM record permissions and module permissions are both enforced where the code checks them.

How to confirm it worked

• The understand compiled feature switches action completes without a validation or permission error.
• The affected record, stock balance, response, session or style reflects the saved state.
• Audit, notification, report or portal evidence appears only where the module code creates it.

Security, privacy and operational checks

• Use a controlled test record before applying changes to live inventory, recipients, visitor tracking or global styling.
• Grant only the minimum module and core CRM capabilities needed for the task.

Continue with related guidance