This page documents the Non-EB Opportunities workflow from the Opportunities list (/leads/list). A user creates a Non-EB opportunity, then progresses through RFQ → QCR → mail actions → placement — all from the list row action menu.

Non-EB rows are identified by leads.lead_form_type = 2 (EB = 1). RFQ and QCR are managed in Google Sheets; sheet IDs are stored in leads.misc JSON.

End-to-end flow

Typical sequence from the list:

1. Create opportunity (form submit) → queued
2. RFQ — create/open Google Sheet → rfq_created
3. QCR — copy RFQ sheet → qcr_created
4. Send Internal Mail — team mail with RFQ or QCR attachment (by current status)
5. Send Insurer Mail — RFQ sheet attached → rfq_sent
6. Send Client Mail — QCR sheet attached → qcr_sent
7. Placement — placement sheet + policy/payment fields → won

Edit is available at any stage from the same action menu and reuses the add form with pre-filled data (getLeadNonEB + POST /leads/create with lead id).

Key files

Google Sheet config

Non-EB RFQ, QCR, and Placement sheets are Google Drive files created at runtime by GoogleSheetLib using a service account. Only RFQ needs a pre-configured template per product; QCR and Placement are copies of the lead’s RFQ/QCR sheets.

App ↔ Google Drive flow

Library: app/Libraries/GoogleSheetLib.php — auth via service account JSON at {project-root}/nhance-ee8d1-e3c5269b1ec7.json, scopes DRIVE + SPREADSHEETS.

What must be done before RFQ / QCR

Where to configure sheet ID per product

Template sheet IDs are stored per product on the policy_type table — one row per product (Fire, Marine, Burglary, etc.). The lead’s selected policy_type_id determines which template is copied when RFQ is clicked.

Database column: policy_type.misc (JSON text)

{
  "rfq_template_sheet_id": "1GXNDNXoWriClb5HCqPYd2GAY1T8aie_Hos0yAOoTaC0"
}

Example — set or update for policy type id 12:

UPDATE policy_type
SET misc = JSON_SET(COALESCE(misc, '{}'), '$.rfq_template_sheet_id', 'YOUR_GOOGLE_DRIVE_FILE_ID')
WHERE id = 12;

How to find a template file ID:

• From the Google Sheet URL: https://docs.google.com/spreadsheets/d/{FILE_ID}/edit
• CLI — list all sheets in the RFQ parent folder: php public/index.php cli/list-sheet-folder-files {RFQ_PARENT_FOLDER_ID} → writes sheetid.json with name + sheetId pairs (GoogleSheetController::listFolderSheetFilesCli)

QCR and Placement: no separate template ID per product. They always copy from the lead’s existing sheets:

App-level config files

Placeholder tokens to embed in each product’s RFQ master template:

After RFQ copy, editors are granted from the lead’s rfq_qcr_viewers JSON email list (selected on the create/edit form). The same list is applied to QCR and Placement copies.

Step 1 — Create opportunity

From the list

1. Open /leads/list → click Add.
2. Modal Select Opportunity Type → choose Non-EB (lead_form_type=2).
3. Redirect: GET /util/getLeadNonEB/2/0.

Form (leads_non_eb.php)

• Sections: Opportunity Details, Client Information, Branch Information, Policy Details, Sales & Assignment.
• Policy types limited to allocg = Non-EB or Marine.
• Policy type change → GET /util/getPolicyTypeFields → dynamic fields in #appendArea.
• Renewal types may show claim history rows → stored as fin_years_claims JSON.
• rfq_qcr_viewers (emails) become Google Sheet editors later.
• Submit → AJAX POST /leads/create with lead_form_type=2.

Controller: createLead()

• prepareLeadData() → prepareSingleLeadData() (one lead row; EB uses multi-row).
• Non-EB validation: policy type, DOC/DOE, claim-history rows when claim_history=1.
• insertNewLead() — no demography background job (EB-only).
• Initial status: queued (In-Queued).

Edit flow

From the list action menu → Edit (available for both EB and Non-EB):

1. JS: getLeadsDataForEdit(lead_id, lead_form_type, actual_lead_id)
2. Redirect: GET /util/getLeadNonEB/{lead_form_type}/{actual_lead_id}/{lead_id}
3. Controller: getLeadNonEB($type, $actual_lead_id, $id) (~line 4818)
   • Loads master data (issuer, policy types, sales team, etc.)
   • When $id present: fetches lead_edit_data, files, custom fields, date formatting
   • Builds dynamic policy HTML via generateViewPageHtml()
   • Renewal Non-EB: renders rfq/claims_details_non_eb into claims_details_html
   • Returns layout with leads_form_handler → includes leads_non_eb.php when selected_lead_type != 1
4. Form pre-fills client, branch, policy, files, viewers, status, lost reason, etc.
5. Submit same endpoint: POST /leads/create with hidden id → updateOldLead()

Steps 2–7 — List table actions (Non-EB)

When lead_form_type === 2, the row action menu in app/Views/leads_list.php (lines ~297–343) uses modal/AJAX flows instead of navigating to /rfq/list/{id}/1|2 (EB behaviour).

Action → view handler → controller endpoint

EB contrast (same menu, lead_form_type === 1): RFQ/QCR are links to /rfq/list/{id}/1 and /rfq/list/{id}/2; internal/insurer/client/placement mail items are not shown.

Shared mail modal helpers (all in leads_list.php):

• POST /leads/uploadLeadAttachment — optional extra files (lead_id, docs_name, file)
• constructURL_ForInternalMailSend(), insurer/client via constructURL_ForInsurerOrClientMailSend(), placement via constructURL_ForPlacementMailSend()
• External CC disclaimer modal (#external_cc_disclaimer_modal) before client/placement send to non-user emails

Step 2 — RFQ (createRfqSheet())

1. Load lead + policy_type.misc.rfq_template_sheet_id.
2. If misc.rfq_sheet_id exists → return existing Google Sheet URL.
3. Copy template via GoogleSheetLib::copyTemplate() into RfqConfig::rfqParentFolderId.
4. Fill placeholders (buildRfqPlaceholderData()): client, GST, PAN, policy period, claims table.
5. Grant editors from leads.rfq_qcr_viewers email JSON.
6. Save misc.rfq_sheet_id; set status = rfq_created.
7. UI opens sheet in a new browser tab.

Step 3 — QCR (createQcrSheet())

1. Requires misc.rfq_sheet_id — returns 400 if RFQ not created yet.
2. If misc.qcr_sheet_id exists → return existing URL.
3. Copy the RFQ sheet (not the policy template) with a QCR filename.
4. Same editor permissions from rfq_qcr_viewers.
5. Save misc.qcr_sheet_id; set status = qcr_created.

Steps 4–6 — Mail actions

Load template — getLeadMailTemplate()

Called before each mail modal opens. Query params: lead_id + template_type (rfq | qcr | placement). Returns subject, HTML body, and attachment checkbox HTML from lead_files.

Send — sendMailWithAttachement()

For Non-EB (lead_form_type == 2), the Excel attachment comes from Google Sheets:

Implementation detail: downloadFileFromGoogleSheet() exports the chosen sheet to a temp .xlsx under writable/tmp/ before MailHelper::send_email().

Step 7 — Placement

Opened from list action → openPlacementFromList(leadId):

1. GET /rfq/placementData/{id} — pre-fills policy dates, premium, CD, installments, contacts.
2. GET /leads/mailTemplate?template_type=placement — subject/body/attachments.
3. User fills placement modal: dates, premium/CD/total, installment rows, To/CC, optional external CC.
4. POST /leads/sendMail with recipient_type=placement.
5. Backend copies QCR → placement Google Sheet, attaches Excel, updates lead to won, persists placement_date, premium_amount, cd_amount, installments, etc.

Status lifecycle

leads.misc JSON

{
  "rfq_sheet_id": "…",
  "qcr_sheet_id": "…",
  "placement_sheet_id": "…"
}

Controller reference (list flow)

Methods in LeadsController.php used by the list Non-EB flow:

Developer checklist

1. Complete Google Sheet config for each Non-EB/Marine policy_type before first RFQ.
2. Set policy_type.misc.rfq_template_sheet_id per product (see sheet ID per product).
3. Configure RFQ_PARENT_FOLDER_ID in .env and share folder/templates with the service account.
4. Ensure placeholders in master templates match Config\RfqConfig::$rfqPlaceholders.
5. Gate new list actions with $isNonEb in leads_list.php.
6. Respect sheet order: RFQ → QCR → mails → placement.
7. QCR button: roles [1, 5, 2, 3] or BUSINESS_SUPPORT_TEAM_ID in user team.

Common pitfalls

• QCR before RFQ: createQcrSheet fails if rfq_sheet_id is missing.
• Queued status: Mail and placement actions are hidden until status moves past queued.
• Insurer mail needs RFQ sheet; client mail needs QCR sheet — create sheets before sending.
• Internal mail attachment picks RFQ or QCR based on current lead status.
• Edit vs create: same POST /leads/create; presence of hidden id triggers update.