Open APIs

Expand all | Collapse all

TMF622 - cardinality of RelatedParty seems to be wrong on resource diagram

  • 1.  TMF622 - cardinality of RelatedParty seems to be wrong on resource diagram

    TM Forum Member
    Posted 11 days ago
    Hi all
    Please advise how to read TMF622 Open API resource model. Particularly for RelatedPartyRef, it's located under Product Order and Product and for both has cardinality like 0..*, however Create Product Order API demands RelatedParty as mandatory -- at least one RelatedParty to be created.
    My question is -- Do we need it mandatory for both either Product or Product Order? I think so, thus imho cardinality should be fixed as 1..* for RelatedParty

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


  • 2.  RE: TMF622 - cardinality of RelatedParty seems to be wrong on resource diagram

    TM Forum Member
    Posted 10 days ago
    Hi Andrii

    From a business perspective, I have trouble to imagine an order without any party related (but perhaps there are some UC that did not require it) - that why " Create Product Order API demands RelatedParty as mandatory".

    But because, as you noted, relatedParty could be described at product order level or product level, I will be unconfortable with a cardinality 1..* at any level. It will limit flexibility to describe party at product order level only or at product level only in API implementations.

    Best regards

    ------------------------------
    Ludovic Robert
    Orange
    ------------------------------



  • 3.  RE: TMF622 - cardinality of RelatedParty seems to be wrong on resource diagram

    TM Forum Member
    Posted 7 days ago
    I think it would be better to set it as 1..* at least for Product Order in that case it will not contradict with API demand. But, I agree, since Product can come as pure Reference in some integrations then yes for Product it can be as 0..*. Anyway thanks for your answer, will think about UCs where it could be optional for Product Order, but can't imagine it now.

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



  • 4.  RE: TMF622 - cardinality of RelatedParty seems to be wrong on resource diagram

    TM Forum Member
    Posted 7 days ago
    Hi,

    Please note that the relation to the customer is already covered via the BillingAccountRef.
    More relatedParties are also available via the relatedParties of the productOffering and productSpecification.
    In case of fully automated processes this is probably sufficient. Additional relatedParties are probably only required in case of manual processes.

    Regards

    ------------------------------
    Koen Peeters
    Ciminko Luxembourg
    ------------------------------



  • 5.  RE: TMF622 - cardinality of RelatedParty seems to be wrong on resource diagram

    This message was posted by a user wishing to remain anonymous
    Posted 10 days ago
    This post was removed