Hello Members!Is it possible to migrate our existing inhouse APIs to TMF648 Specs without considering other TMF specs like catalog, productOfferingQualification, serviceOfferingQualification, agreementManagement, etc,.
Basically we are looking at migrating our Quote systems alone to TMF specs and not to disturb the other systems for time being (Atleast now!)PS: I referred the TMF648 specs and found other systems like catalog, product & service offering, agreement, billing management APIs are interconnected with the Quote requests & so I came up with this question.
Hi JonathanYes I agree with your points. It certainly helps. In our case, we do follow a completely different business process than what needs to be there for TMF standards. For example, agreement, billingAccount & productOfferingQualification entity needs to be created (before quote) and the corresponding entity id should be specified in the Quote request. But we do have a different approach where those entities are created as an internal part of quoting process rather than as a separate entity.
Further, on exploring TMF648 API, quoteItem is the only mandatory attribute of the request, so can I extend the request with attributes (not available in TMF) which is required for our inhouse API? so, this would help us to follow our internal business process as well as the TMF standard.Is my assumptions correct?