Open APIs

 View Only
  • 1.  TMF641 requires name for RelatedParty resource but it is not mandatory for 622

    TM Forum Member
    Posted Jun 03, 2019 08:47
    I've been considering some possibility to build end to end solution between Product Ordering and Service Ordering
    In my opinion, there is a misalignment, particularly  for rules are addressed to the parameters of RelatedParty.
    Since the resource is just a reference, so I think such parameters as 'id', 'href' should be mandatory for POST request to the TMF641 interface. However, I see that only name and role are mandatory for TMF641 on condition the RelatedParty is part of request. Even though it could be considered that href and id of RelatedParty are useless for Service level,  IMHO name can't be mandatory since it is not mandatory for Product Ordering, unless it means that Product Order level should enrich the name of RelatedParty before sending it to service level, Don't you think that is more complex than just send a href which is already there? I would prefer to get thinking that RelatedParty should be referred to the same object across Product and service levels, or made the name mandatory for Product level as well.

    ------------------------------
    Andrii Teslenko
    Netcracker Technology
    ------------------------------


  • 2.  RE: TMF641 requires name for RelatedParty resource but it is not mandatory for 622

    TM Forum Member
    Posted Jun 04, 2019 04:16
    See the replies on the similar forum discussion https://engage.tmforum.org/communities/community-home/digestviewer/viewthread?GroupId=31&MessageKey=f006ed38-f0ef-4dda-8a87-70a42627f31a&CommunityKey=d543b8ba-9d3a-4121-85ce-5b68e6c31ce5&tab=digestviewer&ReturnUrl=%2fcommunities%2fcommunity-home%2fdigestviewer%3fcommunitykey%3dd543b8ba-9d3a-4121-85ce-5b68e6c31ce5%26tab%3ddigestviewer

    Hope it helps

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    ------------------------------