Test Drive Booking Flow

Six stages run in order; the first two can end the request early without ever reaching the database.

Every action on QuickController — including bookdriveAction — runs behind the class constructor (lines 20–58) first. It prepares context that the action reads without re-fetching it:

• $this->brand is read from setting site_settings.autoline_api_brand.
• $_POST['subsite_id'] and $_POST['website_id'] are copied in from the SUBSITEID / WEBSITEID HTTP headers.
• $_POST['store_name'] is looked up from StoresModel using the subsite.
• If productID is present (falling back to ecomProductId), VehiclemodelsModel::getProductModelByID() fills in model, variant, and variantSKU on $_POST.
• crmCustomerID is resolved via UserModel::getCrmIDByUserID().
• If showroomID is set, ShowroomModel::getLocationCode() fills locationCode.
• For the Chery / Omoda5 combination specifically, crm_api_domain and crm_api_token are swapped for the omoda_* variants of those settings.

Parameters arrive as $_POST fields plus three request headers. "Server-derived" fields are never sent by the client — they're computed during the constructor or the action and then read as if they were part of the request.

A single combined condition (line 164) decides pass/fail — the request fails if any of these are true:

Any failure short-circuits to the generic errParameterMissing response — the specific missing field is not named back to the caller.

The success branch, in execution order.

1. Captcha gate (brand-conditional) If brand is chery or exeed, verifyCaptchaAction() runs first. It only enforces anything if security_settings.enable_captcha is Yes — otherwise it's a no-op. When enforced, a missing or Google-rejected token ends the request immediately with an HTTP 400 JSON body; bookdriveAction never resumes.
2. Session context is stamped onto the request userID and subsiteID are overwritten from ObjCommon (the logged-in session), defaulting to 0 when there's no session.
3. Required-field validation See Validation rules. Failing here skips every remaining step and returns the failure JSON directly.
4. Booking is persisted BookTestDriveModel::saveBooking($_POST, $languageIDs['Current']) inserts one row into book_a_test_drive. See Database write.
5. CRM push, conditional on a site setting site_settings.post_lead_to_crm is checked. When Yes, scheduledTime is copied into requestDate and Crm::postLead($_POST, 3, $this->pdtSettings) is called. When not Yes, $crmresponse is simply set to an empty string and no HTTP call happens.
6. Local status is fixed to success status, responseCode (200), and message are set unconditionally at this point — they do not depend on what the CRM call returned.
7. Notification email sendMailLeadNotification(3) sends the "Test Drive Request" lead email — unless the brand is omoda or jac, in which case it returns immediately without sending anything.
8. Response is emitted The meta object is assembled and echoed as pretty-printed JSON, then the request exits.

BookTestDriveModel::saveBooking() runs a single raw INSERT into {DB_PREFIX}book_a_test_drive:

The method returns whatever the database wrapper's setQuery() call returns; bookdriveAction does not inspect or forward that value.

Crm::postLead($_POST, 3, $this->pdtSettings) extracts everything out of $_POST and assembles a JSON payload sent as:

Authorization: Bearer <pdtSettings.crm_api_token>
Content-Type: application/json

{
  "leadType": "Test Drive Request",        // numeric 3 mapped to this string
  "businessSource": "Alghanim website",
  "leadIntent": "Sales",
  "model": "<uppercased model name>",
  "firstName": "<firstName>",
  "lastName": "<lastName>",
  "phone": "<phoneNumber>",
  "prefix": "<title>",
  "email": "<email>",
  "initialTouchPoint": "Online",
  "civilId": "",
  "customerId": "<crmCustomerID>",
  "showroom": "<locationCode>",
  "requestedDate": "<scheduledTime, ISO-8601>",
  "variant": "<variant>",
  "note": "<comments>"
  // plus any of: campaignTag, promoterName, exteriorColor, interiorColor,
  //   purchaseHorizon, purchaseMethod, drivingLicence, addressStreet —
  //   included only when present on the request
}

sendMailLeadNotification(3) is called once the booking is saved, independent of whether the CRM push happened or succeeded.

• Brand short-circuit: if brand is omoda or jac (or byd with lead type 7), the method returns immediately — no mail is sent.
• Lead type 3 maps to the string "Test Drive Request", used to fill the {$extra} token in the email template.
• The template lead-request is loaded, merged with firstName, lastName, email, phoneNumber, model, variant, variantSKU, showroom name, comments, and the request date.
• Recipients come from the site_settings.lead-notification-email setting — a comma-separated list, each address regex-validated before sending.

All three outcomes are pretty-printed JSON (JSON_PRETTY_PRINT | JSON_NUMERIC_CHECK), followed by exit.

Success — 200

{
  "meta": {
    "status": "Success",
    "responsecode": 200,
    "message": "<msgTestDriveBookedSuccessfully>",
    "crmresponse": "<raw CRM response, or "" if post_lead_to_crm ≠ Yes>"
  }
}

Validation failure — required field missing

{
  "meta": {
    "status": "Failure",
    "responsecode": 500,
    "message": "<errParameterMissing>"
  }
}

Note: this branch never sets crmresponse, so the key is entirely absent from the JSON — unlike the success path, which always includes it.

Captcha failure — chery / exeed only, ends before validation

{
  "meta": {
    "status": "Failure",
    "responsecode": 400,
    "message": "<errParameterMissing or errCaptcha>"
  }
}