Open APIs

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Hi @Ludovic Robert,

Can you please provide some guidance around the query in the post above.

Thanks,
Rati​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Original Message:
Sent: Sep 08, 2020 03:55
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Hi Rati,

We need to clarify terminatedWithError and Done states. Seems to me that the definition provided in the user guide confuse people.
There is mixing between the state of the request to cancel vs the cancel itself.
I understood your proposal that make sense for me (I will probably move the SO to inProgress in scenario 1) but we need to probably re-discuss this cancelOrder state within the team.

Hope it helps

Ludovic


------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Original Message:
Sent: Sep 16, 2020 02:56
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,

Can you please provide some guidance around the query in the post above.

Thanks,
Rati​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 08, 2020 03:55
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Hi @Ludovic Robert,  Thanks for your guidance.  Is there any Jira where this is tracked which i can start watching?​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Original Message:
Sent: Sep 16, 2020 05:09
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati,

We need to clarify terminatedWithError and Done states. Seems to me that the definition provided in the user guide confuse people.
There is mixing between the state of the request to cancel vs the cancel itself.
I understood your proposal that make sense for me (I will probably move the SO to inProgress in scenario 1) but we need to probably re-discuss this cancelOrder state within the team.

Hope it helps

Ludovic


------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 02:56
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,

Can you please provide some guidance around the query in the post above.

Thanks,
Rati​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 08, 2020 03:55
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Hi Rati

It was discussed during JIRA 2343 --> you can check the comment (the jira itself is not exactly on this topic). We need probably to sync with @Kamal Maghsoudlou who are working on the v4.1.

Ludovic
​​

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Original Message:
Sent: Sep 16, 2020 22:53
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,  Thanks for your guidance.  Is there any Jira where this is tracked which i can start watching?​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 16, 2020 05:09
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati,

We need to clarify terminatedWithError and Done states. Seems to me that the definition provided in the user guide confuse people.
There is mixing between the state of the request to cancel vs the cancel itself.
I understood your proposal that make sense for me (I will probably move the SO to inProgress in scenario 1) but we need to probably re-discuss this cancelOrder state within the team.

Hope it helps

Ludovic


------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 02:56
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,

Can you please provide some guidance around the query in the post above.

Thanks,
Rati​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 08, 2020 03:55
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Ludovic,

I assume this addition for "Error reason" would be applicable to Task Resources generally. So I can expect  to be able to add the same for cancelProductOrder?

thanks,
Lynn

------------------------------
Lynn Dueck
Oracle Corporation
------------------------------

Original Message:
Sent: Sep 17, 2020 07:50
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati

It was discussed during JIRA 2343 --> you can check the comment (the jira itself is not exactly on this topic). We need probably to sync with @Kamal Maghsoudlou who are working on the v4.1.

Ludovic
​​

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 22:53
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,  Thanks for your guidance.  Is there any Jira where this is tracked which i can start watching?​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 16, 2020 05:09
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati,

We need to clarify terminatedWithError and Done states. Seems to me that the definition provided in the user guide confuse people.
There is mixing between the state of the request to cancel vs the cancel itself.
I understood your proposal that make sense for me (I will probably move the SO to inProgress in scenario 1) but we need to probably re-discuss this cancelOrder state within the team.

Hope it helps

Ludovic


------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 02:56
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,

Can you please provide some guidance around the query in the post above.

Thanks,
Rati​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 08, 2020 03:55
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Hello Lynn,
Yes generally we try to consistently use same pattern for one API to another. Next release for ProductOrder should be aligned with the pattern of serviceOrder for cancelOrder behaviour (in this cas aligned with service order 4.1 version).

Thanks
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Original Message:
Sent: Nov 19, 2020 11:08
From: Lynn Dueck
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Ludovic,

I assume this addition for "Error reason" would be applicable to Task Resources generally. So I can expect  to be able to add the same for cancelProductOrder?

thanks,
Lynn

------------------------------
Lynn Dueck
Oracle Corporation

Original Message:
Sent: Sep 17, 2020 07:50
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati

It was discussed during JIRA 2343 --> you can check the comment (the jira itself is not exactly on this topic). We need probably to sync with @Kamal Maghsoudlou who are working on the v4.1.

Ludovic
​​

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 22:53
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,  Thanks for your guidance.  Is there any Jira where this is tracked which i can start watching?​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 16, 2020 05:09
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati,

We need to clarify terminatedWithError and Done states. Seems to me that the definition provided in the user guide confuse people.
There is mixing between the state of the request to cancel vs the cancel itself.
I understood your proposal that make sense for me (I will probably move the SO to inProgress in scenario 1) but we need to probably re-discuss this cancelOrder state within the team.

Hope it helps

Ludovic


------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 02:56
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,

Can you please provide some guidance around the query in the post above.

Thanks,
Rati​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 08, 2020 03:55
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Hi Ludovic,

Need help with below points around Cancel Order.
InProgress
Acknowledgement - Acknowledgement of Cancel Order means that the provider is able to Cancel the Order. So the Cancel Order request will either have a Acknowledgement or Reject.
Reject - Order cannot be cancelled mainly due to Order reaching PoNR. In which case the consumer will need to send a new Order to Disconnect the Service. Cancel Order Request might be rejected for other reasons like not all the details required to cancel the Ordre may not be present.
Complete - On successful Cancellation of the Order.

Prior to Acknowledgement/Rejection the Order state would be AssessingCancellation
On Acknowledgement the Order state would be CancellationInProgress. It becomes the Providers responsibility to successfully Cancel the Order.
Any failures during cancellation typically if the responsibility of Provider to get it resolved and cancel the Order. terminatedWithError cannot be a terminal status.

Once the Cancel Order is submitted by the consumer, believe it is not possible to perform any more in-flight operation on the Order unless the Cancel Order Request was Rejected.

Appreciate your feedback on this.


------------------------------
Srinivasa Vellanki
Amdocs Management Limited
------------------------------

Original Message:
Sent: Nov 20, 2020 10:09
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hello Lynn,
Yes generally we try to consistently use same pattern for one API to another. Next release for ProductOrder should be aligned with the pattern of serviceOrder for cancelOrder behaviour (in this cas aligned with service order 4.1 version).

Thanks
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Nov 19, 2020 11:08
From: Lynn Dueck
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Ludovic,

I assume this addition for "Error reason" would be applicable to Task Resources generally. So I can expect  to be able to add the same for cancelProductOrder?

thanks,
Lynn

------------------------------
Lynn Dueck
Oracle Corporation

Original Message:
Sent: Sep 17, 2020 07:50
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati

It was discussed during JIRA 2343 --> you can check the comment (the jira itself is not exactly on this topic). We need probably to sync with @Kamal Maghsoudlou who are working on the v4.1.

Ludovic
​​

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 22:53
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,  Thanks for your guidance.  Is there any Jira where this is tracked which i can start watching?​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 16, 2020 05:09
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati,

We need to clarify terminatedWithError and Done states. Seems to me that the definition provided in the user guide confuse people.
There is mixing between the state of the request to cancel vs the cancel itself.
I understood your proposal that make sense for me (I will probably move the SO to inProgress in scenario 1) but we need to probably re-discuss this cancelOrder state within the team.

Hope it helps

Ludovic


------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 02:56
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,

Can you please provide some guidance around the query in the post above.

Thanks,
Rati​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 08, 2020 03:55
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------

Hello Srinivasa;

We had a lot of discussion on this lifecycle lately - To sum-up my understanding of the team direction for the cancel service order flow:

1. We have a service order 'in fly' in the SOM system. I asume in state acknowledged, inProgress, pending or hold.
2. A system externally to the SOM requests a SO cancelation
3. SOM received this request - check surgace data for it (the service order exist for example) and acknowledge it (if ok). The SOM store the cancelServiceOrder in acknowledged state
4. SOM assess if cancelation is possible. The service order switch to assessingCancelation state and the cancelServiceOrder to inProgress state
5. here 2 cases: (1)cancel is possible... the cancelServiceOrder is in state done. The serviceOrder is in PendingCancellation (during the time of performin cancel action) and then cancelled. (2)cancel not possible - the cancelServiceOrder is in state TerminationWitherror and the service order is back in previous state (acknowledged, inProgress, pending or hold).

I invite people involved in the discussion to jump it and comment if my understanding is wrong .

Hope it helps
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Original Message:
Sent: Nov 22, 2020 06:52
From: Srinivasa Vellanki
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Ludovic,

Need help with below points around Cancel Order.
InProgress
Acknowledgement - Acknowledgement of Cancel Order means that the provider is able to Cancel the Order. So the Cancel Order request will either have a Acknowledgement or Reject.
Reject - Order cannot be cancelled mainly due to Order reaching PoNR. In which case the consumer will need to send a new Order to Disconnect the Service. Cancel Order Request might be rejected for other reasons like not all the details required to cancel the Ordre may not be present.
Complete - On successful Cancellation of the Order.

Prior to Acknowledgement/Rejection the Order state would be AssessingCancellation
On Acknowledgement the Order state would be CancellationInProgress. It becomes the Providers responsibility to successfully Cancel the Order.
Any failures during cancellation typically if the responsibility of Provider to get it resolved and cancel the Order. terminatedWithError cannot be a terminal status.

Once the Cancel Order is submitted by the consumer, believe it is not possible to perform any more in-flight operation on the Order unless the Cancel Order Request was Rejected.

Appreciate your feedback on this.


------------------------------
Srinivasa Vellanki
Amdocs Management Limited

Original Message:
Sent: Nov 20, 2020 10:09
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hello Lynn,
Yes generally we try to consistently use same pattern for one API to another. Next release for ProductOrder should be aligned with the pattern of serviceOrder for cancelOrder behaviour (in this cas aligned with service order 4.1 version).

Thanks
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Nov 19, 2020 11:08
From: Lynn Dueck
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Ludovic,

I assume this addition for "Error reason" would be applicable to Task Resources generally. So I can expect  to be able to add the same for cancelProductOrder?

thanks,
Lynn

------------------------------
Lynn Dueck
Oracle Corporation

Original Message:
Sent: Sep 17, 2020 07:50
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati

It was discussed during JIRA 2343 --> you can check the comment (the jira itself is not exactly on this topic). We need probably to sync with @Kamal Maghsoudlou who are working on the v4.1.

Ludovic
​​

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 22:53
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,  Thanks for your guidance.  Is there any Jira where this is tracked which i can start watching?​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 16, 2020 05:09
From: Ludovic Robert
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi Rati,

We need to clarify terminatedWithError and Done states. Seems to me that the definition provided in the user guide confuse people.
There is mixing between the state of the request to cancel vs the cancel itself.
I understood your proposal that make sense for me (I will probably move the SO to inProgress in scenario 1) but we need to probably re-discuss this cancelOrder state within the team.

Hope it helps

Ludovic


------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Sep 16, 2020 02:56
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi @Ludovic Robert,

Can you please provide some guidance around the query in the post above.

Thanks,
Rati​

------------------------------
Rati Mehrotra
Telstra Corporation

Original Message:
Sent: Sep 08, 2020 03:55
From: Rati Mehrotra
Subject: TMF 641 : Cancel Service order lifecycle mapping with service order

Hi ,

Need some guidance on the cancelServiceOrder state transition mapping to serviceOrder state transition.

The state transition in cancelServiceOrder are Acknowledged, inProgress , terminatedWithError and Done. The definition provided below  and both terminatedWithError and Done are final states.

terminatedWithError  : The CancelOrder could not be correctly completed by Service Order component. It did not mean that the cancel request is denied – it means that the assessment was not be done
Done :CancelOrder assessment has been done. The Order has been cancelled or keep is as it if cancel request denied.

My queries are on below two scenarios :

Scenario 1:

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment could not be completed due to some reason , the cancelServiceOrder state would be "terminatedWithError". In this case, what should be the expected state transition of service order. Should it move back to "inProgress" or should it move to "pending" and request consumers to cancel the order again?

Scenario 2 :

• Considering a scenario when an order is in "inProgress" and the consumer decide to cancel the order. 
• When cancelServiceOrder has reached "inProgress" , the service Order state can be transitioned to "AssessingCancellation".
• Now if  the cancelServiceOrder assessment is completed , the cancelServiceOrder state would be "done". But since the done state is only indication of assessment being completed, if the assessment concludes that  order cannot be cancelled , should the service order state be moved back to "inProgress" .

Basically we are trying to come up with a table like below for better understanding:

CancelServiceOrder	Service Order
	inProgress
Acknowledged	AssessingCancellation
InProgress	AssessingCancellation
TerminatedWithError	pending( should the consumer send another request for cancelling) or should order move back to "inProgress"
Done	PendingCancellation ->Cancelled for success cancellation inProgress for denied cancellation

Thanks,
Rati
@Uma Lakshman

​

------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------