Hello,
little warning to TMF members who use TMF620 APIs:
- the last version is not : TMF620-Product_Catalog_Management-v5.0.0.oas
- the last version is : TMF620-Product_Catalog_Management-v5.0.0.oas
I hope that's clear 😉.
I realised this at my expense as I was modelling eligibility and advanced pricing rules in 620 and realised my JSON response were wrong and could not be used by Product configurator (TMF760). After a time-consuming analysis, I realised I was working with the wrong OAS file.
It seems the OAS file was "silently" updated in January but the uploader did not change the version number (maybe it should have been v5.0.1) and did not announce or publish the change log.
@Heidi Lobecker, @Lorna Mitchell
I see you publish all API announcements. Is there anything that can be done so we can avoid this issue in the future?
@Lutz Bettge, so far, I noticed these differences: policyRef added, priceAlteration removed, bundledGroupProductOfferingOption removed, bundledGroupProductOffering added. Do you have a list of all changes?
the 2 conflicting files are here (it will be deleted in 6 days)
------------------------------
Kind regards,
Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS
------------------------------