Dear TM Forum,
Our solution for a Product Catalogue is based in Product Catalogue Management API and we've detected a performance issue when we return all the product offering prices for one product offering.
The model used to satisfy the business requirement has several levels (at maximum 3) of product offering price and this means that each POP is connected to the other POP using the popRelationship sub-resource (a list of pop relationship PopRelationship[*]). This model obliges several calls to the backend system decreasing the performance.
Following the Product Catalogue Management API, the operation that we advocate to return all the prices for one product offering is GET /productOffering/<productOfferingId>/productOfferingPrice/, but in this <g class="gr_ gr_15 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation only-ins replaceWithoutSep" id="15" data-gr-id="15">case</g> the Product Catalogue Management API doesn't return the entire POP structure.
So, our suggestion goes through <g class="gr_ gr_13 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace" id="13" data-gr-id="13">modify</g> the operation posted above to return the entire productOfferingPrice structure, this change will improve the performance because this suggestion needs only one call to our backend system.
We would like to know from TMForum's point of view if there is any inconvenience in implementing this solution and if it doesn't exist, what is the possibility of TMForum to adopt this solution.
------------------------------
Best Regards,
António Ribeiro
Celfocus
------------------------------