Our TMF648 compliant Quote Management platform has POST-Quote and PATCH-Quote APIs.
- POST-Quote is used for creation of TMF648 compliant Quote,
- PATCH-Quote is used for configuration of TMF648 compliant Quote.
TMF622 compliant Order Management platform has POST-ProductOrder endpoint that accepts TMF622 compliant Order.
But we are trying to understand what is the TMF648 endpoint that accepts the id/payload of a TMF648 compliant Quote object, converts it into a TMF622 compliant Order object and finally calls the POST-ProductOrder endpoint.
Currently we have a POST-SubmitQuote API. It is not TMF compliant. But this API accepts the id of a Quote object, converts it to an OSSJ Order object and finally submit to Order Management via a TMF non-compliant API.
We can spawn a TMF compliant variant of existing POST-SubmitQuote API. This API will only accepts the id of a TMF compliant Quote, converts it to a TMF622 compliant Order object and finally submit to TMF622 compliant POST-ProductOrder API. Is this the standard industry practice?
Thanks, Mujtaba.
------------------------------
Mujtaba Nowshad
Hansen Technologies
------------------------------