Open APIs

Hi,

I have question about TMFC027: Product Configurator component.

In document TMFC027 Product Configurator v2.1.1 there is diagram TMFC027 Product Configurator (page 5)

In this diagram, we see which APIs are consumed by the Product Configurator.

I see that this component consumes, for example, TMF637 Product Inventory Management, TMF666 Account Management, and TMF669 Party Role Management. This suggests that prices returned by TMF760 may be influenced by existing products-for instance, all products beyond the fifth one being 50% cheaper.

In our implementation, agreements can also impact the price of a particular product offer. TMF651 Agreement Management enables linking agreement items with specific offers.

However, the diagram does not show the consumption of TMF651 Agreement Management or TMF629 Customer Management.

Shouldn't it be a general assumption that the Product Configurator consumes TMF651 Agreement Management, at least for TMF679 Product Offering Qualification?

APIs listed in TMFC0027 are just illustrative suggestions and don't always have align with dependent APIs defined in the API documentation.

i.e. one can argue that TMFC0027 also omits the very important TMF645 (Service Qualification) or TMF723 (Policy) APIs.

Each CSP/ISV should add the APIs that make sense for their implementation.

Original Message:
Sent: Feb 21, 2025 03:48
From: Tomasz Ruchała
Subject: TMFC027: Product Configurator consuming API

Hi,

I have question about TMFC027: Product Configurator component.

In document TMFC027 Product Configurator v2.1.1 there is diagram TMFC027 Product Configurator (page 5)

In this diagram, we see which APIs are consumed by the Product Configurator.

I see that this component consumes, for example, TMF637 Product Inventory Management, TMF666 Account Management, and TMF669 Party Role Management. This suggests that prices returned by TMF760 may be influenced by existing products-for instance, all products beyond the fifth one being 50% cheaper.

In our implementation, agreements can also impact the price of a particular product offer. TMF651 Agreement Management enables linking agreement items with specific offers.

However, the diagram does not show the consumption of TMF651 Agreement Management or TMF629 Customer Management.

Shouldn't it be a general assumption that the Product Configurator consumes TMF651 Agreement Management, at least for TMF679 Product Offering Qualification?

------------------------------
Tomasz Ruchała
Comarch S.A.
------------------------------