Adobe Commerce - Global Management

DQE Core Module Overview

Multistore Configuration

• The DQE module supports multistore configurations.
• It can be enabled or disabled at both website and store levels using the enable/disable field in Stores > Configuration > DQE > DQE Core.
• Configuration for DQE services such as Address, Email, Gender, B2B, and Phone can also be managed by scope.

Controller

• The DQE Core module includes controllers that handle requests to the DQE API and return formatted responses.
• Controllers are located in the controller folder and include:
  1. Index Controller: used for customer account login, create, and edit forms.
  2. Checkout Controller: used for checkout shipping and billing forms.

Model

• The DQE Core module uses the DqeDataModel, which maps to the dqe_core_data table in the database.
• Controller responses are stored in this table. Each response contains a type and a mapping_entity_id, for example the customer ID in the customer_entity table.
• Response types:
  • TEMP: temporary data until the form is submitted.
  • ADDRESS: address-related responses.
  • ADDRESS_COMPL: address completion responses.
  • PHONE: phone-related responses.
  • EMAIL: email-related responses.

JavaScript Integration

• When a response is sent by the controller, JavaScript files retrieve the parameters and insert a hidden input field with a random ID into the Magento form.
• This random ID is temporarily stored in the database.

Observer

• Observers ensure that responses are definitively saved in the database when the form is submitted.
• They retrieve the proper entity_id and mapping_entity_id, which are inserted into the DOM by JavaScript.
• Important note: once submitted, the TEMP type transitions to its final type, such as ADDRESS or EMAIL.

Cron Jobs

• If a form is not submitted, responses marked as TEMP are automatically removed later by a scheduled cron job.

DQE Core Features

• The DQE Core module contains the primary operations organized into the Model and Controller folders.
• It also manages the license parameter, which is critical for all other DQE modules.