Hi Uma
I don't think that we have reached this level of granularity in the Open API semantics for orders (such as service order).
At least according to my understanding of current semantics, a POST and a PATCH on a service order are synchronous, in other words the result is immediate (201 for POST and 200 for PATCH).
And PATCH can be invoked any number of times (until the PoNR).
To achieve your use case would require keeping multiple versions (perhaps) of the service order, and canceling a patch request would somehow cause reversion to the previous version, assuming that this was still possible (depending on what work was already done).
Deferring to
@Ludovic Robert, the lead and SME for TMF641.
------------------------------
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: Jul 06, 2020 20:50
From: uma lakshman
Subject: Cancellation Of Inflight Patch on TMF 641 - ServiceOrderManagement API
Hi there,
Need your assistance in supporting cancellation of an inflight patch which is applied on an inflight 641 ServiceOrder Creation.
High level sequence as below.
Sequence of Event :
- Consumer Request to create serviceOrder
- Service Provider Initiates ServiceOrder creation
- Service Provider responds with id and href in HTTP Response 202 and move the order state to inProgress
- Consumer Updates Service Characteristics of serviceOrder which is inProgress
- Service Provider acknowledges the update request
- Service Provider responds with with id and href in HTTP Response 202
- Consumer wants to cancel PATCH request (step 4) )which is not completed or not reached PONR
The flow is detailed in the attachment as well .
Looking forward to get some guidance on supporting the 7th step in the sequence , which is a cancellation request on an inflight PATCH. The diagram and steps shows only one PATCH on an inflight serviceOrder. There are usecases where there can be multiple patches on an inflight order. We are looking for a generic solution which can be selectively applied on a specific patch.
Regards,
Uma Lakshman
Telstra Corporation
------------------------------
Uma Lakshman
Telstra Corporation
------------------------------