Hi,
In most cases, we need to manage the changes in the Catalog (Product, Service or Resource) as a whole in some kind of transaction that goes through its own lifecycle. Eg: As part of Christmas Campaign, some new Product Offers are being introduced. There could be a Project to roll out Fiber Services that require changes in Service Catalog. In the Catalog APIs, I don't see anything that can encapsulate multiple Catalog Entities belonging to a changeset that could be managed on its own. This Changeset could go through its own lifecycle through Dev-Test-Production and there are cases where we would like to expose the changeset to external systems so that those systems could retrieve the contents of the changeset for synchronization to external catalogs.
My question is how to manage this changeset in the Catalog? Does it require a new Resource that we don't have in the Catalog APIs Resource Models? Or should we manage it using something like a Business Interaction and use TMF681 Communications Management API for this purpose?
------------------------------
Kinshuk Kulshreshtha
Oracle Corporation
My views posted on this forum are personal, and do not reflect the position of my employer or TM Forum.
------------------------------