Open APIs

Expand all | Collapse all

TMF637 "status" in POST /product

  • 1.  TMF637 "status" in POST /product

    TM Forum Member
    Posted Nov 03, 2020 12:09
    We are implementing TMF637 and while going through resource model in conformance doc TMF637B, it is mentioned that "status" is only optional for making POST /product call and mandatory only in response message which seems to be a logical expectation of this API.

    But when you read through TMF637 API specification or use sample postman requests(they do not have status but wont work until you specify one) or in swagger specification, you will notice that "status" is mandatory field even for create(POST /product) product api. Is this a mistake in documentation? If not, can you please explain why is this required to sent "status" while creating a product?

    In short, can someone confirm if "status" is a required request parameter while creating a product subscription?

    Ravi Sharma

  • 2.  RE: TMF637 "status" in POST /product

    TM Forum Member
    Posted Nov 04, 2020 03:30
    Hello Ravi

    For me yes this is mandatory in the POST request and we need to fix accordingly the conformance profile.
    I'm not sure it makes sense to have product without a status so the alternative should have been to have a by default status but this is not the way it is designed.

    For my perspetive TMF637 for creation/update is only used internally by the Product Order management component (and the order fullfillment process is responsible to update - accordingly to delivery milestone - the product status) or in very restricted UC to correct wrong inventory representation (done by admin).

    Hope it helps

    Ludovic Robert
    My answer are my own & don't represent necessarily my company or the TMF