Britixo CRMBritixo CRM Enterprise Help Centre
Help centreInventory & Warehousing Management SystemUnderstand the disabled legacy proposal-customer branch
CRM integrations and automation

Understand the disabled legacy proposal-customer branch

Do not expect the old-customer proposal conversion controls because ACTIVE_PROPOSAL_OLD_CUSTOMER is false.

Audience: Inventory staff, warehouse managers, finance teams and administratorsPermission: Relevant inventory capabilityModule v1.5.2
Exact navigationAdmin Area → Sales → Proposals
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

Do not expect the old-customer proposal conversion controls because ACTIVE_PROPOSAL_OLD_CUSTOMER is false. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Admin Area → Sales → Proposals.
  2. Select the record or action required for understand the disabled legacy proposal-customer branch.
  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, choices and supported possibilities

WorkspaceAdmin Area → Sales → Proposals
ActionDo not expect the old-customer proposal conversion controls because ACTIVE_PROPOSAL_OLD_CUSTOMER is false.

Code-backed validations and workflow rules

  • 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.

Expected result and verification

  • The understand the disabled legacy proposal-customer branch 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.
Use the active proposal integrationUnderstand disabled Brand, Model and Series settingsCRM integrations and automationBrowse all Inventory & Warehousing Management System guidesCreate an invoiceCreate a taskPurchase ManagementProjects and tasksClient portalReports and goals