Configuration · Third-party integrations & connectors

The per-centre connector settings: Connectif (marketing automation API URL and key), cinema listings (theatre API and id, app/web channels), blog URL, cashback (admin, client and store-transaction URLs), Tally and custom forms, PAC Virtual receipt capture with Neodoc or Neuro OCR, email validation, footfall, and the operator app for the play centre.

AreaConfiguration
Routesconfiguration.centers.new · configuration.centers.edit
Centre modulesapp_operator · blog · cashback · connectif · email_validation · form_commerces · forms · movies · tally
Staff levelsroot · admin · manager · scmanager
Modelsapp-module-custom-forms · app-module-email-validation · app-module-pacv · app-module-tally · module-app-operator · module-blog · module-cashback · module-connectif · module-footfall · module-movies
UI labelconfiguration.center.modules
Coverage4 use cases · 1 happy · 3 failure

How it works

Each connector is a module toggle plus parameters, validated with the pattern ‘enabled AND value missing/invalid’. PAC Virtual (‘PACV’) is the receipt-upload channel: it has an application key, an automatic-validation switch, a ticket-notification option, a read-name option and an OCR provider; enabling Neodoc OCR makes its token mandatory (configuration.center.neodoc-ocr.token). onChangeEnablePacv / onChangeEnableAppPacv keep the CRM and app sides consistent. The operator app has its own sub-modules (enums/modules-app-operator), currently the play centre. Search modules (store-search, staff-search, category-search) are also toggled here.

Use cases

Why someone opens this (4)

  • Sending customer events to Connectif for marketing automation.
  • Showing cinema listings in the app from the theatre’s API.
  • Letting customers upload receipts via PAC Virtual with OCR so moderators only check exceptions.
  • Enabling a cashback programme with separate admin and client portals.

Path map

flowchart LR
    F(["Third-party integrations and connectors"]):::feat
    F --> H1["PAC Virtual with OCR"]:::ok
    F -.-> X1["OCR enabled without token"]:::bad
    F -.-> X2["Integration URL malformed"]:::bad
    F -.-> X3["Wrong API key"]:::bad
    classDef feat fill:#566066,stroke:#566066,color:#ffffff,font-weight:bold
    classDef ok fill:#e3f1ea,stroke:#0d6b42,color:#0d4a2e
    classDef bad fill:#f7e6e2,stroke:#9a2d1c,color:#6e1f13

Happy paths

PAC Virtual with OCR

  1. Admin enables PACV on the CRM side, which reveals the app PACV section.
  2. Sets the application key, enables Neodoc OCR and pastes its token.
  3. Optionally enables automatic validation.
  4. Saves; uploaded receipts are read by OCR and land in the receipt queue already parsed.

Failure paths

QA checklist

Tick these off while regression-testing this feature. The boxes are plain Markdown, so progress is visible in git diffs.

  • ✅ PAC Virtual with OCR
  • ⛔ OCR enabled without token
  • ⛔ Integration URL malformed
  • ⛔ Wrong API key

Implementation


Generated from doc/feature-inventory.json · id config-integrations · commit 276788ca6