Open APIs

 View Only
  • 1.  TMF 620 Product Catalogue ConstraintRef

    TM Forum Member
    Posted Mar 06, 2024 09:36

    In TMF 620 we have constraint defined at productOfferingPrice. As per my understanding it is a condition which make this price valid/deemed for productOrdering.

    We have a use-case where we need to define productOfferingPrice at zipcode level. In a developing country like India we have 19000 zipcodes.

    So we can define a constraint called name=PriceAvailabilityConstraint id=2503 . 

    Now question is there is no data model for Constraint defined yet. If we define our own entity can we create task resource over it,  example evaluate defined below



    "name": "zipcode",
    "description": "ZIPCODE where this price is available ",
    "valueType": "number",
    "constraintsCharacteristicValue": [
    "valueType": "number",
    "value": 121001
    Result of above task resource will give true or false, true means constraint evaluation is true false means provided zipcode not satisfying the constraints.
    Is this a valid pattern to use constraint, or there is best practice available for constraints.

    subhanshu shukla
    Bharti Airtel Ltd

  • 2.  RE: TMF 620 Product Catalogue ConstraintRef

    TM Forum Member
    Posted May 26, 2024 03:38


    Sorry about the delay in answering this one. In v5, TMF620 was updated to point to Policy instead of Constraint. There is a Policy Management API in progress, that allows you to represent authoring of business rules by policy expressions.

    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.