TM Forum Community

 View Only

Engagement not having right to CRUD

  • 1.  Engagement not having right to CRUD

    Posted Sep 03, 2019 07:58
    Edited by Rabinder Devnani Sep 03, 2019 08:00
    Hi @Dave Milham,

    I was going through  ODA functional architecture document (IG1167_ODA_Functional_Architecture_R19.0.0​​) and found below statement in section "4.2.4. Open API's Requirement"

    "In ODA, Engagement management doesn't have the right to Create, Delete, Update data. So, it cannot use the current TMF Open APIs, which are CRUD operations on data. Therefore, to allow interactions and decoupling between Engagement Management and Party Management, Core Commerce Management, Production, new APIs which prohibit Create, Update and Delete operations on data have to be defined. The TM Forum Open API group is currently working on the definition of these APIs."

    I want to understand if the above statement is the base assumption for decoupling of SoE with SoR then :

    1. How for e.g. are we going to capture the online orders ?
    2. How are we going capture customer/user details and send it to Customer Registry in case of online on-boarding journeys ?
    3. How will it enable Quote to order journey which involves a long sales team process ?


    #OpenDigitalArchitecture

    ------------------------------
    Rabinder Devnani
    Sterlite Technologies Limited
    ------------------------------