Hi
@Ludovic Robert @Jonathan GoldbergWhile reviewing the new TMF641 specs version 4.0.0, I cant make out the process expected to be followed for cancellation of service orders. What i understood vaguely was that a new resource entity called cancelServiceOrder would need to be created, and it will reference the serviceOrder resource. Is the expectation that the system exposing this API is expected to create a cancelServiceOrder resource , and should control the state of this resource while making changes on the serviceOrder resource internally (like updating state to cancelled)?
After getting a cancelServiceOrder POST request, I can have my orch engine to initiate a patch on serviceOrder resource to update the state to "Cancelled", and once that is done, cancelServiceOrder resource can be pushed to "Done" state. Is that the ideal way to achieve cancellation, or is there a recommended pattern by API team?
Also, the example for cancelServiceOrder POST published in the document, shows that the state of the resource is set to "Done" in the HTTP 201 response, which is probably incorrect as you might have a few business rules to validate before we mark it "Done", and should ideally be responded back via notifications rather then a 201 response?
Appreciate your guidance on this.
------------------------------
Vishal Thakur
BT Group plc
------------------------------