Open APIs

 View Only
  • 1.  TMF678 duplicate @type and type attribute for AppliedCustomerBillingRate

    Posted Jul 21, 2020 05:04
    Hello,

    I've come across duplicate definition of @type and type attribute definition for ​​AppliedCustomerBillingRate within TMF678.
    It seems to me a similar issue as discussed in this thread in context of TMF657_ServiceQualityManagement.

    The type attributes duplicate in the latest 2019 swagger TMF7678 definition in GitHub. 

    I'm thinking about altering the swagger locally so that type attribute would be named, e.g.: "chargeType":
    "type": {
    "chargeType": {
          "type": "string",
           "description": "Type of the applied billing rate : appliedBillingCharge (any kind of charge except taxation charges : recurringCharge, oneTimeCharge, usageCharge), appliedBillingCredit (any kind of credit : rebate or productAlteration) or appliedPenaltyCharge (penalty charges such as late fees, payment rejection fees,...)"
    }, 

    Do you know if TMForum teams are working on this definition as well?

    Cheers,
    Bartosz



    ------------------------------
    Bartosz Kluzek
    Liberty Global Services B.V.
    ------------------------------


  • 2.  RE: TMF678 duplicate @type and type attribute for AppliedCustomerBillingRate

    TM Forum Member
    Posted Jul 21, 2020 08:11
    Hi Bartosz
    Be aware that TMF678 has not yet been published, it is still in beta. In general I advise not to go directly to GitHub, but rather via the Open API table, then you can choose if you are going to the published version (old for TMF678, from 17.5) or to the newer beta version (from 19).

    In any case this error has been corrected in our internal working area and the swagger fragment looks like this:

    "appliedBillingRateType": {
    "type": "string",
    "description": "Type of the applied billing rate : appliedBillingCharge (any kind of charge except taxation charges : recurringCharge, oneTimeCharge, usageCharge), appliedBillingCredit (any kind of credit : rebate or productAlteration) or appliedPenaltyCharge (penalty charges such as late fees, payment rejection fees,...)"
    },

    I don't know what the publication schedule is for this API, perhaps @Alan Pope can react, and/or update the beta swagger with the one from the working area.

    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.
    ------------------------------



  • 3.  RE: TMF678 duplicate @type and type attribute for AppliedCustomerBillingRate

    Posted Jul 22, 2020 03:05
    Thanks Jonathan for very quick answer. This is very helpful.

    I was looking at the Open API table, but when writing it I thought it is worth to look also to GitHub to see possible public updates.

    Cheers,
    Bartosz

    ------------------------------
    Bartosz Kluzek
    Liberty Global Services B.V.
    ------------------------------