TM Forum Community

 View Only

TMF629: Customer Management API to manage multiple name fields

  • 1.  TMF629: Customer Management API to manage multiple name fields

    Posted Jun 16, 2023 11:38
    Edited by Chetan Hirpara Jun 17, 2023 04:29

    Hi Team,

    Query 1:

    Here we need to store & retrieve name inputs in multiple language<e.g English & French > as well as it's not a single full name entity. It has been divided in four part like,  FirstName, SecondName, MiddleName and LastName while customer management post/get operation have only single place holder as "name". Here I am expecting your guidance to manage all four part of name through this API<TMF629: Customer Management API>.

    Query 2:

    Here we need to manage 5-6 inputs/attributes for customer status like statusvalue, substatus and demographics field while in TMF629 , there is only two placeholder so please can someone suggest extension object or other way around to incorporate my required fields?

    Query 3:

    We need to manage customer Identity information like idno, idtype, shortcode , validity duration in date, demographics information while there is no such place holder in TMF629 so please can someone suggest extension object or other way around to incorporate my required fields?

    Query 4:

    There is a contactMedium place holder but it has limited attributes while we may need to more attributes like validity duration in extension, hasextention, marketing permission flag, demographics attributes etc. so please can someone suggest extension object or other way around to incorporate my required fields?

    Query 5:

    Here we need to manage address as a separate entity with lots of attribute while TMF629 have few attributes under contact medium place holder. Here we need you guidance to manage address schema object with additional inputs like demographics attributes, block, landmark, locality name, city-state-country id as well as name, multiple boolean values like is Primary , isactive so please can someone suggest extension object or other way around to incorporate my required fields?

    Query 6:

    TMF629 have agreement placeholder where we need to manage additional inputs/attributes like documentContent, CreationTime, upload channel as well as multiple demographics attributes, so please can someone suggest extension object or other way around to incorporate my required fields?
    #General

    Query 7:

    How can we mange account production information in TMF629? Here we need to manage productid, productname, billingaccount, barringReason object and demographics attributes.

    @Jonathan Goldberg   
    ------------------------------
    Chetan Patel
    Tech Mahindra Limited
    ------------------------------