Cross-Application Sync

Step 1 — Launch PolySniffer for Dolibarr

In the Django admin, each PassThrough endpoint has a PolySniffer Analysis button. Click it on the Dolibarr ERP row to start the traffic capture proxy.

Step 2 — PolySniffer Captures All Traffic

The PolySniffer dashboard shows every HTTP request in real time. As we navigate Dolibarr, every GET and POST is captured with full headers, cookies, and body content.

Step 3 — Login to Dolibarr Through the Proxy

Dolibarr 19.0.2 loads through the PolySniffer proxy. The login request is captured, giving us the CSRF token pattern and authentication flow.

Step 4 — Navigate to Third-parties

After login, the Dolibarr dashboard shows the full menu: Home, Members, Third-parties, Products, Projects, Commerce, Billing, and more. We navigate to Third-parties.

Step 5 — Select New Customer

The Third-parties sidebar shows the entity list. Statistics: 0 Prospects, 0 Customers, 0 Vendors. We click New Customer to begin.

Step 6 — Fill the New Third Party Form

The form captures comprehensive customer data. We fill in the fields that will be extracted by the Mapping Engine:

Step 7 — Submit: Create Third Party

The bottom of the form shows Professional IDs, Sales tax (checked), Third-party type, and the sales representative assignment. Click CREATE THIRD PARTY.

When submitted, PolySniffer captures the full POST body with all 43 form fields, including the hidden CSRF token, action type, and all visible form values.

Step 8 — Customer Created in Dolibarr

Dolibarr confirms the record with auto-generated Customer Code CU2603-00001. All entered data is displayed on the card view.

Step 9 — Mike Oliver Appears in Odoo Contacts

The sync chain completes: Dolibarr → Mapping Engine → RabbitMQ → Mapping Engine → Odoo XML-RPC. The customer record now appears in Odoo Contacts.

Step 10 — Full Record Detail in Odoo

Opening the contact record confirms every field was correctly mapped from the Dolibarr form through both Mapping Engine transformations:

Sync Complete — Zero code changes. Entirely driven by database-configured Mappings and Instructions.

Instructions in the Tenant Admin

Instructions are the routing rules that connect incoming requests to atomic services. In the Oliver Enterprises tenant, two new Instructions were created for the cross-app sync flow:

Instruction Detail: Dolibarr POST Capture

Each Instruction defines a requestpath (substring match), method, direction, and an eventKey for tracking. The Instruction Mappings tab links it to one or more Mapping records that define the field extraction logic.

When any POST request passes through the proxy and its URL contains /societe/card.php, this Instruction fires the EndpointDataExtractorService, which uses the attached Mapping to extract and normalize the form fields.