Hi Somesh
Some background on the Catalog entity.
Having a Catalog entity in the catalog APIs (Product, Service, Resource, Entity) allows implementations to maintain multiple catalogs, which can be used for various purposes (e.g. different sub-markets). But catalogs are
not necessarily containers of catalog items (paradoxical as this sounds). The model allows you to implement a scheme where the same offering is exposed in multiple catalogs, although you could also to choose strict partitioning. Entirely up to you (or, since you are a vendor, your telco customer).
The association of offerings to catalogs is via categories. You can build category trees separately for each catalog, or have shared categories across multiple catalogs. And offerings are associated with categories, via the category (not via the offering).
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.
------------------------------
Original Message:
Sent: Jun 14, 2021 20:00
From: Somesh Batra
Subject: Catalog Id is missing in Post Product Offering
Hi,
We are implementing ProductOffering API and while adding post method, we found that catalog id is not a field while creating product offering. If no catalog id is passed, how does product catalog know which offer does this catalog belong to? @Jonathan Goldberg, can you check please?
Regards,
Somesh
------------------------------
Somesh Batra
Pegasystems, Inc.
------------------------------