Open APIs

Hello,

I have a couple of questions regarding this API:
-> since this API is supposed to be used for evaluating the technical and commercial eligibility is there any intention to also return the cardinality (min, max) of the eligible product offerings? currently the only indication is the qualified/unqualified status at ProductOfferingQualificationItem level (qualificationItemResult)
-> is this API also supposed to return the prices for the product offerings in the given context? according to the Resource Model diagram prices should be returned only for existing products (which I assume are products from inventory or that were already added to the cart)

Have a great day,

Iulia

------------------------------
Iulia Pasca
IBM Corporation
------------------------------

Hello Iulia

1) for my perspective TMF679 is mainly designed for commercial eligibility because it works at product level. I will more recommend service qualification API for technical eligibility. From an implementation perspective this could trigger some challenge because need to mix 2 calls but usually these API supplier components are not the same (Commercial catalog vs feasability check component).
Adding max/min could be an interesting idea to improve the API - it is true that sometimes a given customer could not buy more than X occurences of same offer. A Change request should be trigger for this.
2) For me the price are not supposed to be retrieved by POQ. For consistence we use same ProductRefOrValue class for all product API so that why you have this productPrice.

Hope it helps

Ludovic

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

Hello Ludovic,

Thank you for the reply. I would be really interested in how the API calls will be orchestrated on a purchase flow. Are there by any chance some examples with Product Offering and Product Offering Qualification for such a Use Case?

Many thanks,
Iulia

------------------------------
Iulia Pasca
IBM Corporation
------------------------------

Original Message:
Sent: Apr 02, 2020 11:39
From: Ludovic Robert
Subject: TMF679 ProductOfferingQualification API

Hello Iulia

1) for my perspective TMF679 is mainly designed for commercial eligibility because it works at product level. I will more recommend service qualification API for technical eligibility. From an implementation perspective this could trigger some challenge because need to mix 2 calls but usually these API supplier components are not the same (Commercial catalog vs feasability check component).
Adding max/min could be an interesting idea to improve the API - it is true that sometimes a given customer could not buy more than X occurences of same offer. A Change request should be trigger for this.
2) For me the price are not supposed to be retrieved by POQ. For consistence we use same ProductRefOrValue class for all product API so that why you have this productPrice.

Hope it helps

Ludovic

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

Hi all,

I know my reply is way too late, I only recently started on TMF APIs.

I had the same question and other members could find my reply useful in the future.

TMF has created some use cases to illustrate how the APIs can be used.
for this exact question,  IG1228
has the use cases you're looking for.

My 2 cents

------------------------------
Matthieu Hattab
Altibox AS
------------------------------

Original Message:
Sent: Apr 10, 2020 03:31
From: Iulia Pasca
Subject: TMF679 ProductOfferingQualification API

Hello Ludovic,

Thank you for the reply. I would be really interested in how the API calls will be orchestrated on a purchase flow. Are there by any chance some examples with Product Offering and Product Offering Qualification for such a Use Case?

Many thanks,
Iulia

------------------------------
Iulia Pasca
IBM Corporation
------------------------------


Original Message:
Sent: Apr 02, 2020 11:39
From: Ludovic Robert
Subject: TMF679 ProductOfferingQualification API

Hello Iulia

1) for my perspective TMF679 is mainly designed for commercial eligibility because it works at product level. I will more recommend service qualification API for technical eligibility. From an implementation perspective this could trigger some challenge because need to mix 2 calls but usually these API supplier components are not the same (Commercial catalog vs feasability check component).
Adding max/min could be an interesting idea to improve the API - it is true that sometimes a given customer could not buy more than X occurences of same offer. A Change request should be trigger for this.
2) For me the price are not supposed to be retrieved by POQ. For consistence we use same ProductRefOrValue class for all product API so that why you have this productPrice.

Hope it helps

Ludovic

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

Original Message:
Sent: 9/14/2021 1:17:00 PM
From: Matthieu Hattab
Subject: RE: TMF679 ProductOfferingQualification API

Hi all,

I know my reply is way too late, I only recently started on TMF APIs.

I had the same question and other members could find my reply useful in the future.

TMF has created some use cases to illustrate how the APIs can be used.
for this exact question,  IG1228
has the use cases you're looking for.

My 2 cents

------------------------------
Matthieu Hattab
Altibox AS
------------------------------


Original Message:
Sent: Apr 10, 2020 03:31
From: Iulia Pasca
Subject: TMF679 ProductOfferingQualification API

Hello Ludovic,

Thank you for the reply. I would be really interested in how the API calls will be orchestrated on a purchase flow. Are there by any chance some examples with Product Offering and Product Offering Qualification for such a Use Case?

Many thanks,
Iulia

------------------------------
Iulia Pasca
IBM Corporation
------------------------------