Open APIs

 View Only
  • 1.  TM Forum Conformance Tests Release Version V19.0.0

    TM Forum Member
    Posted Feb 20, 2020 12:16

    Hi Fellow TM FOrum members, 

    I have a question over some field like validFor which they have mentioned in the response payload for POST operation.
    I work in Verizon and we have decided to make this field as our response payload for Patch operation( which refer as UpdateTicketService) and so I would like to have a brief definition of the usage specifically of the field validFor. I have read that it mentions some validity of the attachment but I am not cleared by validity of the attachment. My question is when you create a resource , your conformance mentions validFor as a must in response  but we are deciding to make this field as required in different API operation i.e. PATCH response payload . Hence , before using this field (validFor), could anyone give us a brief clarity of this field ?

    Regards,

    Harkaran Sidhu

    Software Engineer,

    Verizon

    E: Harkaran.Sidhu@verizon.com



    ------------------------------
    Harkaran Sidhu
    Verizon Communications
    ------------------------------


  • 2.  RE: TM Forum Conformance Tests Release Version V19.0.0

    TM Forum Member
    Posted Feb 25, 2020 10:46
    Hi Harkaran

    Can you clarify which API you are referring to - we thought it might be Trouble Ticket but not sure.
    Attachment is a general entity used across the entire Open API model. The validity period of an attachment would presumably mean that the contents should be considered valid only for that time period. For Trouble Ticket it is not clear that this limitation would be relevant, for other business areas it is possible to come up with use cases that limit the validity.

    If you have more queries about the Trouble Ticket API, you could reach out to @Jacob Avraham , who leads this API design.

    Hope it helps​

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------