X
NMS Prime
Stay informed. No spam. Just content. This is our promise.
I agree to the privacy terms. I can unsubscribe at any time.
X
Thank You!
X
NMS PRIME - Konferenz
Anzahl der Teilnehmer:
Datenschutz gelesen und akzeptiert
X
Vielen Dank!
X Sign up to comment and create new topics

Page tree

NOTE

this module is in development and is not in production!

Database

WorkFlow

Adding a customer

DB synchronization

  1. forward update: nmsprime –> nmsprime_ccc, via a ISP service user
  2. reverse update: nmsprime_ccc –> nmsprime, from customer via CCC

Solution Ideas:

  • Patrick Reichel: Reverse update: only by ticket system (TODO) See Authentication API

  • forward update: DB update in nmsprime auto updates nmsprime_ccc, e.g. via Observer, just simply copy Model from Admin in CCC context and save, this could also be done scheduled (without Observers for heavy/mass assignments)

  • reverse update: defined merge rules (table), auto- and/or manual update mode
    manual mode: means a service admin performs updates based on nmsprime assumptions to update

  • migration synchronization with ProvBase or Billing Module:
    Solution: https://github.com/mrjgreen/db-sync – See Example 8:


availability/product checking

address / product mapping

required fields address table:

  • zip
  • city
  • street
  • house_number

Structure




DB namenmsprime_ccc
DB usernmsprime_ccc



required tablescontract

sepamandate

item







KDG OTC Example

  • No labels